Run ‘make check’ and fix various typos

1 files changed, 12 insertions, 12 deletions

diff --git a/src/prj/mmv/index.gsp b/src/prj/mmv/index.gsp
index 3c2fd97..f049426 100644
--- a/src/prj/mmv/index.gsp
+++ b/src/prj/mmv/index.gsp
@@ -270,8 +270,8 @@ html lang="en" {
 					}
 					p {-
 						If combined with the @code{--0} flag, then while input will be read
-						assuming a NUL-byte input-seperator, the encoded input files will be
-						written to the spawned process newline-seperated.
+						assuming a NUL-byte input-separator, the encoded input files will be
+						written to the spawned process newline-separated.
 					}
 				}
 			}
@@ -332,7 +332,7 @@ html lang="en" {
 
 			p {-
 				So we’re getting places, but we aren’t quite there yet.  The issue we’re
-				getting now is that @code{-mmv} recieved 2 input files from the standard
+				getting now is that @code{-mmv} received 2 input files from the standard
 				input, but @code{-rev} produced 3 output files.  Why is that?  Well
 				let’s try our hand at a little bit of command-line debugging with
 				@code{-sed}:
@@ -365,7 +365,7 @@ html lang="en" {
 			p {-
 				In the @code{-sed} output, we can see that @samp{-$} represents the end
 				of a line, and @samp{-\\000} represents the NUL-byte.  All looks good
-				here, we have two inputs seperated by NUL-bytes.  Now let’s try to throw
+				here, we have two inputs separated by NUL-bytes.  Now let’s try to throw
 				in @code{-rev}:
 			}
 
@@ -375,7 +375,7 @@ html lang="en" {
 
 			p {-
 				Well wouldn’t you know it?  Since @code{-rev} @em{-also} works with
-				newline-seperated input, it reversed out NUL-byte seperators and now
+				newline-separated input, it reversed out NUL-byte separators and now
 				gives us 3 outputs.  Luckily the folks over at @em{-util-linux} provided
 				us with the @code{--0} flag here too, so that we can properly handle
 				NUL-delimited input. Combining all of this together we get a final
@@ -393,7 +393,7 @@ html lang="en" {
 				use doesn’t support NUL-bytes as nicely as we would like.  In these
 				cases, you may want to consider encoding your newline characters into
 				the literal string ‘@code{-\\n}’ and then passing your input
-				newline-seperated to your given command with the @code{--e} flag.
+				newline-separated to your given command with the @code{--e} flag.
 			}
 
 			p {-
@@ -415,7 +415,7 @@ html lang="en" {
 			aside {
 				p {-
 					Notice how you still need to pass the @code{--0} flag to @code{-mmv}
-					know that our inputfiles may have embedded newlines.
+					know that our input files may have embedded newlines.
 				}
 			}
 
@@ -429,8 +429,8 @@ html lang="en" {
 			}
 
 			p {-
-				After you exit your editor, @code{-mmv} will decode all occurances of
-				‘@code{-\\n}’ back into a newline, and all occurances of ‘@code{-\\\\}’
+				After you exit your editor, @code{-mmv} will decode all occurrences of
+				‘@code{-\\n}’ back into a newline, and all occurrences of ‘@code{-\\\\}’
 				back into a backslash:
 			}
 
@@ -441,11 +441,11 @@ html lang="en" {
 			h2 #i-flag {-Individual Execution}
 			p {-
 				The previous examples are great and all, but what do you do if your
-				mapping command doesn’t have the concept of an input seperator at all?
+				mapping command doesn’t have the concept of an input separator at all?
 				This is where the @code{--i} flag comes into play.  With the @code{--i}
 				flag we can get @code{-mmv} to execute our mapping command for every
 				input filename.  This means that as long as we can work with a complete
-				buffer, we don’t need to worry about seperators.
+				buffer, we don’t need to worry about separators.
 			}
 
 			p {-
@@ -524,7 +524,7 @@ html lang="en" {
 				}
 				li {-
 					In the case that something goes wrong during execution (perhaps you
-					tried to move a file to a non-existant directory, or a syscall
+					tried to move a file to a non-existent directory, or a syscall
 					failed), a backup of your input files is saved automatically by
 					@code{-mmv} for recovery.
 				}