Fix spelling

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Reviewed-by: Haakan T Johansson <f96hajo@chalmers.se>
Closes #5547 
Closes #5543

tests/zfs-tests/tests/functional/inheritance/README.config

@@ -29,7 +29,7 @@
 # or set locally.
 #
 # Format for this file is as follows:
-#	<dataset name>	<dataset type> 	<inital property setting>
+#	<dataset name>	<dataset type> 	<initial property setting>
 #
 # <dataset name> - must be the full dataset name
 #

tests/zfs-tests/tests/functional/inheritance/inherit_001_pos.ksh

@@ -157,10 +157,10 @@ function update_recordsize { #dataset init_code
 # The mountpoint property is slightly different from other properties and
 # so is handled here. For all other properties if they are set to a specific
 # value at a higher level in the data hierarchy (i.e. checksum=on) then that
-# value propogates down the hierarchy unchanged, with the source field being
+# value propagates down the hierarchy unchanged, with the source field being
 # set to 'inherited from <higher dataset>'.
 #
-# The mountpoint property is different in that while the value propogates
+# The mountpoint property is different in that while the value propagates
 # down the hierarchy, the value at each level is determined by a combination
 # of the top-level value and the current level in the hierarchy.
 #
@@ -327,7 +327,7 @@ function scan_state { #state-file
 				# set up correctly as specified in the
 				# configX.cfg file (which includes 'set'ting
 				# properties at a higher level and checking
-				# that they propogate down to the lower levels.
+				# that they propagate down to the lower levels.
 				#
 				# Note in a few places here, we use
 				# check_failure, rather than log_must - this

tests/zfs-tests/tests/functional/inheritance/state001.cfg

@@ -33,7 +33,7 @@
 # No command is actually run (hence '-:-') but rather this state file is
 # used to verify that the property that was set on the top level pool
 # via the 'local' keyword (in the config1.cfg file) has correctly
-# propogated down the hierarchy.
+# propagated down the hierarchy.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state002.cfg

@@ -33,7 +33,7 @@
 # No command is actually run (hence '-:-') but rather this state file is
 # used to verify that the property that was set on the middle level
 # dataset via the 'local' keyword (in the configX.cfg file) has
-# correctly propogated down the hierarchy to the filesystem underneath,
+# correctly propagated down the hierarchy to the filesystem underneath,
 # while leaving the top level pools properties unchanged.
 #
 # *** ASSERTION DESCRIPTION ***

tests/zfs-tests/tests/functional/inheritance/state012.cfg

@@ -32,12 +32,12 @@
 #
 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
 # when the bottom filesystem level properties have been set locally results
-# in the top level property values being propogated down the data
+# in the top level property values being propagated down the data
 # hierarchy.
 #
 # Executing inherit -r at the middle level and bottom levels after
 # running it at the top level is somewhat redundant as the top level value
-# should propogate down the entire data hierarchy. Done for completeness
+# should propagate down the entire data hierarchy. Done for completeness
 # sake.
 #
 # *** ASSERTION DESCRIPTION ***

tests/zfs-tests/tests/functional/inheritance/state014.cfg

@@ -32,12 +32,12 @@
 #
 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
 # when the bottom and middle level properties have been set locally results
-# in the top level property values being propogated down the data
+# in the top level property values being propagated down the data
 # hierarchy.
 #
 # Note : executing inherit -r at the middle level and bottom levels after
 # running it at the top level is somewhat redundant as the top level value
-# should propogate down the entire data hierarchy. Done for completeness
+# should propagate down the entire data hierarchy. Done for completeness
 # sake.
 #
 # *** ASSERTION DESCRIPTION ***

tests/zfs-tests/tests/functional/inheritance/state015.cfg

@@ -40,7 +40,7 @@
 # the bottom level.
 #
 # Executing 'zfs inherit' at the bottom level is somewhat redundant but
-# is done for completness sake.
+# is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state016.cfg

@@ -37,7 +37,7 @@
 # to the top level (default) values.
 #
 # Executing 'zfs inherit -r' at the bottom and middle levels after executing
-# at the top level is somewhat redundant but ss done for completness sake.
+# at the top level is somewhat redundant but ss done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state017.cfg

@@ -41,7 +41,7 @@
 # the values down to the bottom level.
 #
 # Executing 'zfs inherit' at the bottom level is somewhat redundant but
-# is done for completness sake.
+# is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state018.cfg

@@ -34,11 +34,11 @@
 # when the top level and middle level datasets properties are set locally,
 # and the bottom level has inherited its properties from the middle
 # level, results in the top level properties reverting back to their
-# default values and being propogated down to the other datasets in the
+# default values and being propagated down to the other datasets in the
 # hierarchy.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels after executing
-# it at the top level is somewhat redundant but is done for completness sake.
+# it at the top level is somewhat redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state019.cfg

@@ -37,7 +37,7 @@
 # levels inheriting the changed values.
 #
 # Executing 'zfs inherit' at the middle and bottom levels is somewhat
-# redundant but is done for completness sake.
+# redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state020.cfg

@@ -37,7 +37,7 @@
 # levels inheriting the changed values.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels is somewhat
-# redundant but is done for completness sake.
+# redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state022.cfg

@@ -37,7 +37,7 @@
 # levels inheriting the changed values.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels is somewhat
-# redundant but is done for completness sake.
+# redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #

tests/zfs-tests/tests/functional/inheritance/state024.cfg

@@ -33,7 +33,7 @@
 # Verify that executing 'zfs inherit -r' at the top level in the hierarchy
 # when each levels properties are set locally, results in the top level
 # properties reverting back to their default values, and the changed
-# values being propogated down the hierarchy.
+# values being propagated down the hierarchy.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels after doing so
 # at the top level is somewhat redundant but is done for completeness.