Use single quotes

6 files changed, 15 insertions, 15 deletions

diff --git a/src/index.gsp b/src/index.gsp
index 9f2808c..78d6239 100644
--- a/src/index.gsp
+++ b/src/index.gsp
@@ -19,8 +19,8 @@ html lang="en" {
 			p {-
 				Welcome to my plot of the internet.  This site is mostly oriented
 				towards topics related to software development, but you might eventually
-				find some things that are completely unrelated as well.  The “source
-				code” for the site (if you can call m4_abbr(HTML) @x-ref{-1} and a basic
+				find some things that are completely unrelated as well.  The ‘source
+				code’ for the site (if you can call m4_abbr(HTML) @x-ref{-1} and a basic
 				build system source code)
 				@a
 					href="https://git.thomasvoss.com/www.thomasvoss.com"
diff --git a/src/prj/mmv/index.gsp b/src/prj/mmv/index.gsp
index 3207611..185d93e 100644
--- a/src/prj/mmv/index.gsp
+++ b/src/prj/mmv/index.gsp
@@ -238,8 +238,8 @@ html lang="en" {
 			p {-
 				People are retarded, and as a result we have filenames with newlines in
 				them.  All it would have taken to solve this issue for everyone was for
-				literally @strong{-anybody} during the early UNIX days to go “@em{-hey,
-				this is a bad idea!}”, but alas, we must deal with this.  Newlines are
+				literally @strong{-anybody} during the early UNIX days to go ‘@em{-hey,
+				this is a bad idea!}’, but alas, we must deal with this.  Newlines are
 				of course not the only special characters filenames can contain, but
 				they are the single most infuriating to deal with; the UNIX utilities
 				all being line-oriented really doesn’t work well with these files.
@@ -284,7 +284,7 @@ html lang="en" {
 				though another example.  We have 2 files — one with and one without an
 				embedded newline — and our goal is to simply reverse these filenames.
 				In this example I am going to be displaying newlines in filenames with
-				the “@code{-$'\\n'}” syntax as this is how my shell displays embedded
+				the ‘@code{-$'\\n'}’ syntax as this is how my shell displays embedded
 				newlines.
 			}
 
@@ -312,9 +312,9 @@ html lang="en" {
 
 			aside {
 				p data-ref="1" {-
-					The reason you get a cryptic “file not found” error message is because
+					The reason you get a cryptic ‘file not found’ error message is because
 					@code{-mmv} tries to assert that all the input files actually exist
-					before doing anything.  Since “foo” isn’t a real file, we error out.
+					before doing anything.  Since ‘foo’ isn’t a real file, we error out.
 				}
 			}
 			
@@ -359,7 +359,7 @@ html lang="en" {
 				}
 				li {-
 					The @code{-l} command in @code{-sed} prints the current input in a
-					“visually unambiguous form”.
+					‘visually unambiguous form’.
 				}
 			}
 
diff --git a/src/srp/fw-ec/index.gsp b/src/srp/fw-ec/index.gsp
index 3b8a94a..acd39b9 100644
--- a/src/srp/fw-ec/index.gsp
+++ b/src/srp/fw-ec/index.gsp
@@ -178,9 +178,9 @@ html lang="en" {
 
 			aside {
 				p data-ref="1" {-
-					If you’re confused by what I mean by a “key-chord”, I am simply
+					If you’re confused by what I mean by a ‘key-chord’, I am simply
 					referring to pressing multiple keys in conjunction, such as when you
-					press “@kbd{-Ctrl + C}” to copy text.
+					press ‘@kbd{-Ctrl + C}’ to copy text.
 				}
 			}
 
diff --git a/src/srp/fw-ec/kbd-sc-cb.c.gsp b/src/srp/fw-ec/kbd-sc-cb.c.gsp
index fa03466..31524de 100644
--- a/src/srp/fw-ec/kbd-sc-cb.c.gsp
+++ b/src/srp/fw-ec/kbd-sc-cb.c.gsp
@@ -1,4 +1,4 @@
-@span .c-cmt {-/* “make_code” is the scancode.  “pressed” is a boolean that is true if this is a}
+@span .c-cmt {-/* ‘make_code’ is the scancode.  ‘pressed’ is a boolean that is true if this is a}
    @span .c-cmt {-keydown event, and false if it’s a keyup. */}
 
 r = @span .c-fn {-my_handler_function}(make_code, pressed);
diff --git a/src/srp/gsp/index.gsp b/src/srp/gsp/index.gsp
index b417165..8c56883 100644
--- a/src/srp/gsp/index.gsp
+++ b/src/srp/gsp/index.gsp
@@ -86,8 +86,8 @@ html lang="en" {
 			p {- Oh no.}
 
 			p {-
-				Now most readers probably had the initial reaction of “@em{-What’s wrong
-				with Markdown?}”.  To answer your question: everything.  The issue I
+				Now most readers probably had the initial reaction of ‘@em{-What’s wrong
+				with Markdown?}’.  To answer your question: everything.  The issue I
 				have with these highly-prevalent Markdown-based replacements for
 				m4_abbr(HTML) is that they ignore the fundamental fact that
 				m4_abbr(HTML) and Markdown are @em{-not} compatible languages with each
diff --git a/src/style.css b/src/style.css
index 753de28..1ea926b 100644
--- a/src/style.css
+++ b/src/style.css
@@ -77,8 +77,8 @@ h2                 { font-size: 1.2rem; }
 a       { color: var(--accent);  }
 a:hover { text-decoration: none; }
 
-blockquote > p:first-child::before  { content: '“';  }
-blockquote > p:last-child::after    { content: '”';  }
+blockquote > p:first-child::before  { content: '‘';  }
+blockquote > p:last-child::after    { content: '’';  }
 blockquote + figcaption::before     { content: '— '; }
 
 blockquote, blockquote + figcaption { font-style: italic; }