Fix typos in tests/

Reviewed-by: Ryan Moeller <ryan@ixsystems.com>
Reviewed-by: Richard Laager <rlaager@wiktel.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
Closes #9243

tests/zfs-tests/tests/functional/rsend/rsend_008_pos.ksh

@@ -38,7 +38,7 @@
 # STRATEGY:
 #	1. Separately promote pool clone, filesystem clone and volume clone.
 #	2. Recursively backup all the POOL and restore in POOL2
-#	3. Verify all the datesets and property be properly received.
+#	3. Verify all the datasets and properties were properly received.
 #
 
 verify_runnable "both"

tests/zfs-tests/tests/functional/rsend/rsend_011_pos.ksh

@@ -63,7 +63,7 @@ for prop in $(fs_inherit_prop); do
 done
 
 #
-# Inherit propertes in sub-datasets
+# Inherit properties in sub-datasets
 #
 for ds in "$POOL/$FS/fs1" "$POOL/$FS/fs1/fs2" "$POOL/$FS/fs1/fclone" ; do
 	for prop in $(fs_inherit_prop) ; do

tests/zfs-tests/tests/functional/rsend/rsend_012_pos.ksh

@@ -39,7 +39,7 @@
 #	1. Setting properties for all the filesystem and volumes randomly
 #	2. Backup all the data from POOL by send -R
 #	3. Restore all the data in POOL2
-#	4. Verify all the perperties in two pools are same
+#	4. Verify all the properties in the two pools are the same
 #
 
 verify_runnable "global"

tests/zfs-tests/tests/functional/rsend/rsend_022_pos.ksh

@@ -25,7 +25,7 @@
 #
 # Strategy:
 # 1. Bookmark a ZFS snapshot
-# 2. Destroy the ZFS sanpshot
+# 2. Destroy the ZFS snapshot
 # 3. Destroy the filesystem for the receive
 # 4. Verify receive of the full send stream
 # 5. Start an incremental ZFS send of the ZFS bookmark, redirect output to a

tests/zfs-tests/tests/functional/rsend/rsend_024_pos.ksh

@@ -25,7 +25,7 @@
 #
 # Strategy:
 # 1. Destroy the filesystem for the receive
-# 2. Unmount the source filsesystem
+# 2. Unmount the source filesystem
 # 3. Start a full ZFS send, redirect output to a file
 # 4. Mess up the contents of the stream state file on disk
 # 5. Try ZFS receive, which should fail with a checksum mismatch error

tests/zfs-tests/tests/functional/rsend/send-cD.ksh

@@ -45,7 +45,7 @@ typeset inc=$BACKDIR/stream.inc
 log_must zfs create -o compress=lz4 $sendfs
 log_must zfs create -o compress=lz4 $recvfs
 typeset dir=$(get_prop mountpoint $sendfs)
-# Don't use write_compressible: we want compressible but undedupable data here.
+# Don't use write_compressible: we want compressible but undeduplicable data.
 log_must eval "dd if=/dev/urandom bs=1024k count=4 | base64 >$dir/file"
 log_must zfs snapshot $sendfs@snap0
 log_must eval "zfs send -D -c $sendfs@snap0 >$stream0"

tests/zfs-tests/tests/functional/rsend/send-c_resume.ksh

@@ -28,7 +28,7 @@
 # 2. Mess up the contents of the stream state file on disk
 # 3. Try ZFS receive, which should fail with a checksum mismatch error
 # 4. ZFS send to the stream state file again using the receive_resume_token
-# 5. ZFS receieve and verify the receive completes successfully
+# 5. ZFS receive and verify the receive completes successfully
 # 6. Repeat steps on an incremental ZFS send
 #
 

tests/zfs-tests/tests/functional/rsend/send-c_stream_size_estimate.ksh

@@ -89,4 +89,4 @@ for compress in $compress_types; do
 	    "$vol_csize and $vol_refer differed by too much"
 done
 
-log_pass "The the stream size given by -P accounts for compressed send."
+log_pass "The stream size given by -P accounts for compressed send."

tests/zfs-tests/tests/functional/rsend/send_realloc_encrypted_files.ksh

@@ -25,7 +25,7 @@
 # Strategy:
 # 1. Create a pool containing an encrypted filesystem.
 # 2. Use 'zfs send -wp' to perform a raw send of the initial filesystem.
-# 3. Repeat the followings steps N times to verify raw incremental receives.
+# 3. Repeat the following steps N times to verify raw incremental receives.
 #   a) Randomly change several key dataset properties.
 #   b) Modify the contents of the filesystem such that dnode reallocation
 #      is likely during the 'zfs receive', and receive_object() exercises

tests/zfs-tests/tests/functional/rsend/send_realloc_files.ksh

@@ -25,7 +25,7 @@
 # Strategy:
 # 1. Create a pool containing an encrypted filesystem.
 # 2. Use 'zfs send -wp' to perform a raw send of the initial filesystem.
-# 3. Repeat the followings steps N times to verify raw incremental receives.
+# 3. Repeat the following steps N times to verify raw incremental receives.
 #   a) Randomly change several key dataset properties.
 #   b) Modify the contents of the filesystem such that dnode reallocation
 #      is likely during the 'zfs receive', and receive_object() exercises