Fix spelling errors in priority file comments

1 files changed, 4 insertions, 4 deletions

diff --git a/templates/priority b/templates/priority
index 64d2658..5c27a56 100644
--- a/templates/priority
+++ b/templates/priority
@@ -12,7 +12,7 @@
 # the config templates, and consist of code executed at the "update:",
 # "delete:", "create", "begin:", and "end:" tags.
 # 
-# The priority file provides a few imporant benefits.  First, it breaks
+# The priority file provides a few important benefits.  First, it breaks
 # the configuration statements to be committed into groups whose "commit
 # actions" are applied together in a "transaction".
 # Second, it defines the order in which these transactions are
@@ -50,9 +50,9 @@
 # The "commit" command reads this priority file and sorts the entries in
 # increasing order by their <priority> field.  We usually try to
 # maintain this file sorted in increasing <priority> order so that we
-# can redily see the order in which entries will be processed.  Next, it
+# can readily see the order in which entries will be processed.  Next, it
 # processes each entry, starting from the lowest priority entry, and
-# proceeding in increasing prioriy order.  For each entry, it checks to
+# proceeding in increasing priority order.  For each entry, it checks to
 # see if the <config-sub-tree> exists in the tree of parameters to be
 # committed.  If it does, it takes the config statements under that
 # sub-tree and removes any statements that match a deeper sub-tree that
@@ -82,7 +82,7 @@
 # be a multi-node parameter.  An example of this is if the routing
 # protocol parameters of an interface are applied before the interface
 # itself is applied.  In this case, the parent nodes are created in the
-# "active config" tree at the time the lower-level node is commited.
+# "active config" tree at the time the lower-level node is committed.
 # 
 
 200 firewall/group