Fix multiple typos

1 files changed, 10 insertions, 10 deletions

diff --git a/src/srp/gsp/index.gsp b/src/srp/gsp/index.gsp
index 1ff3686..38f8555 100644
--- a/src/srp/gsp/index.gsp
+++ b/src/srp/gsp/index.gsp
@@ -56,7 +56,7 @@ html lang="en" {
 				standard input and -output like all good UNIX utilities.  I should be
 				able to transpile my site by simply running ‘@code{-cmd in.xyz
 				out.html}’, where my input reflects the structure of my output will
-				nicer, less-poluting syntax such as in ‘@code{-div .cls { … \}}’.
+				nicer, less-polluting syntax such as in ‘@code{-div .cls { … \}}’.
 			}
 
 			p {-
@@ -67,8 +67,8 @@ html lang="en" {
 				m4_abbr(HTML), because that’s exactly what we’re trying to output.  It
 				makes little sense to create a fundamentally different language when
 				m4_abbr(HTML) not only does a good job at defining a websites structure,
-				but sticking close to the language we are targetting just makes
-				everyones life easier in every way.
+				but sticking close to the language we are targeting just makes
+				everyone's life easier in every way.
 			}
 
 			h2 #sucks {-Most Software Sucks}
@@ -92,7 +92,7 @@ html lang="en" {
 				m4_abbr(HTML) is that they ignore the fundamental fact that
 				m4_abbr(HTML) and Markdown are @em{-not} compatible languages with each
 				other.  m4_abbr(HTML) is designed around making websites (with the added
-				autism of m4_abbr(XML)).  It gives us things like sematic tags for
+				autism of m4_abbr(XML)).  It gives us things like semantic tags for
 				describing input forms, navigation bars, figures, and more.  With the
 				addition of classes and IDs, we can even style two paragraphs on the
 				same page in different ways.  This is fundamentally not possible in
@@ -163,7 +163,7 @@ html lang="en" {
 				Here you can see almost all of m4_abbr(GSP).  The document follows the
 				same structure as m4_abbr(HTML), but thanks to the use of braces instead
 				of opening- and closing tags, the syntax is far less verbose and easier
-				to read.  The language also provides shorthands for classses and IDs
+				to read.  The language also provides shorthands for classes and IDs
 				through m4_abbr(CSS)-selector syntax.
 			}
 
@@ -267,10 +267,10 @@ html lang="en" {
 
 			p {-
 				As you can see, this is all really simple stuff, which is what I love so
-				much about Tree Sitter — it’s just so easy!  With these basic annotions
-				your editor knows that attribute values should be highlighted like
-				strings, braces like tag delimiters, etc.  In a similar vein, writing a
-				query to describe code-folding is really easy:
+				much about Tree Sitter — it’s just so easy!  With these basic
+				annotations your editor knows that attribute values should be
+				highlighted like strings, braces like tag delimiters, etc.  In a similar
+				vein, writing a query to describe code-folding is really easy:
 			}
 
 			figure {
@@ -293,7 +293,7 @@ html lang="en" {
 				over-abstract — I’m looking at you, Java developers.  Abstraction often
 				leads to exponentially increased complications the moment we want to do
 				anything different or out of the ordinary, so unless you can find a
-				really nice abstraction that doesn’t really make anyones life harder,
+				really nice abstraction that doesn’t really make anyone's life harder,
 				try to avoid them when you can.
 			}