Require standard ASCII quote characters (#392)

Author: emmercm

index.js

@@ -542,9 +542,11 @@ tracer(Metalsmith(path.resolve()))
         directoryIndex: 'index.md'
     }))
 
-    // Validate markdown file naming
     .use((files, metalsmith, done) => {
-        const pathMismatches = metalsmith.match('**/*.md', Object.keys(files))
+        const markdownFilenames = metalsmith.match('**/*.md', Object.keys(files));
+
+        // Validate markdown file naming
+        const pathMismatches = markdownFilenames
             .map((filename) => {
                 const file = files[filename];
                 const permanentPath = `${file.paths.dir || 'index'}${file.paths.ext}`
@@ -555,7 +557,24 @@ tracer(Metalsmith(path.resolve()))
             .filter((err) => err);
         if (pathMismatches.length) {
             done(`Some blog articles are named incorrectly:\n${pathMismatches.map((err) => `  ${err}`).join('\n')}`);
+            return;
         }
+
+        // Validate markdown content
+        const illegalContents = markdownFilenames
+            .map((filename) => {
+                const file = files[filename];
+                const illegalMatches = /([ʹʺʻʼʽˈ˝ˮ‘’‛“”„‟′″‵‶])/.exec(file.contents.toString());
+                if (illegalMatches !== null) {
+                    return `${filename}: ${illegalMatches.slice(1).join(', ')}`;
+                }
+            })
+            .filter((err) => err);
+        if (illegalContents.length) {
+            done(`Some blog articles have illegal content:\n${illegalContents.map((err) => `  ${err} `).join('\n')}`);
+            return;
+        }
+
         done();
     })
 

src/blog/amortize-your-learning-by-writing-how-to-guides.md

@@ -52,13 +52,13 @@ Here are some example how-to guides you could write today:
 - Local development & testing instructions for your services, especially if they differ from your organization's norms
 - Deployment steps for your services, in case multiple manual steps need coordination
 - A list of custom metrics emitted by your services and what they mean
-- How to use one of your team's admin tools (and no, strict RPC schemas aren’t self-descriptive)
+- How to use one of your team's admin tools (and no, strict RPC schemas aren't self-descriptive)
 
 ## Audience three: the public
 
 You should be motivated by both helping yourself and your colleagues, but if not, try writing how-to guides for clout.
 
-If in the course of your daily tasks you’ve learned something generalizable or publicly applicable, blog about it! You would be surprised how helpful it can be to someone else. If the [Reddit blackout of 2023](https://en.wikipedia.org/wiki/2023_Reddit_API_controversy) taught us anything, it's that a lot of valuable knowledge exists on the internet, and sometimes it only exists in one or two Google-crawled places. You have valuable knowledge, and others should feel honored for you to share it.
+If in the course of your daily tasks you've learned something generalizable or publicly applicable, blog about it! You would be surprised how helpful it can be to someone else. If the [Reddit blackout of 2023](https://en.wikipedia.org/wiki/2023_Reddit_API_controversy) taught us anything, it's that a lot of valuable knowledge exists on the internet, and sometimes it only exists in one or two Google-crawled places. You have valuable knowledge, and others should feel honored for you to share it.
 
 I wrote "[Bash Environment Variable Defaults](/blog/bash-environment-variable-defaults)" because I wanted a "snack" article that was easy to write, and even though the topic is relatively niche, the article is in my top five articles by hits. On the other hand, I wrote "[Docker Shell vs. Exec Form](/blog/docker-shell-vs.-exec-form)" mostly as an article to support "[You Don't Need an Init System for Node.js in Docker](/blog/you-don-t-need-an-init-system-for-node.js-in-docker)," but the former gets nearly 10x the hits. There is so much more information about Docker and related technologies that I thought it would get lost in the noise. But you never know what people will find valuable!
 
@@ -72,6 +72,6 @@ It can be difficult (and overwhelming!) to start writing something from nothing.
 
 There's a Ralph Waldo Emerson quote from his essay titled "[Compensation](https://en.wikipedia.org/wiki/Compensation_(essay))" that is often referenced when talking about the "pay it forward" movement:
 
-> In the order of nature we can’t render benefits to those from whom we receive them, or only seldom. But the benefit we receive must be rendered again, line for line, deed for deed, cent for cent, to somebody. Beware of too much good staying in your hand. It will fast corrupt and worm worms. Pay it away quickly in some sort.
+> In the order of nature we can't render benefits to those from whom we receive them, or only seldom. But the benefit we receive must be rendered again, line for line, deed for deed, cent for cent, to somebody. Beware of too much good staying in your hand. It will fast corrupt and worm worms. Pay it away quickly in some sort.
 
 In that paragraph, Emerson is talking about paying debts, and the rest of the essay is about keeping one's life in balance. It's not quite the same as writing how-to guides, but I appreciate his opinion that it's one's responsibility to pass benefits on to others.

src/blog/an-effective-incident-runbook-template.md

@@ -125,7 +125,7 @@ Steps to take, in order:
 > 1. Help the incident responder take steps to stop the situation from getting worse.
 > 2. Help the incident responder take steps to recover from the situation.
 >
-> Incident mitigation is all about fixing the immediate problem. You can think of mitigation as: if I’m paged at 3 a.m., what do I need to do to get the system healthy such that I can confidently & safely go back to sleep?
+> Incident mitigation is all about fixing the immediate problem. You can think of mitigation as: if I'm paged at 3 a.m., what do I need to do to get the system healthy such that I can confidently & safely go back to sleep?
 >
 > Complicated, nuanced, or unclear steps may benefit from the inclusion of screenshots that have been marked up with arrows and/or numbers to indicate action order.
 >
@@ -155,13 +155,13 @@ Indicators that health has been restored:
 >
 > - Help the incident responder take any final, necessary steps before the incident can be resolved.
 >
-> Incident remediation covers the steps that need to be taken after mitigation, generally during normal working hours. Steps may include but aren’t limited to:
+> Incident remediation covers the steps that need to be taken after mitigation, generally during normal working hours. Steps may include but aren't limited to:
 >
 > - Reverting any temporary hotfixes made during mitigation
 > - Dealing with any corrupted data or statistics
 > - Auditing other services, jobs, etc. for similar risks
 >
-> This doesn’t encompass incident follow-ups, which should be created & prioritized as part of the written incident postmortem & debrief meeting.
+> This doesn't encompass incident follow-ups, which should be created & prioritized as part of the written incident postmortem & debrief meeting.
 
 Steps to take, in order:
 

src/blog/defensive-shell-scripting-with-shell-options.md

@@ -251,7 +251,7 @@ VAR=$(false; echo "this will NOT print")
 
 However, there is a whole list of scenarios where `set -e` isn't inherited. From the [`set` docs](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html):
 
-> The shell does not exit if the command that fails is part of the command list immediately following a `while` or `until` reserved word, part of the test in an `if` statement, part of any command executed in a `&&` or `||` list except the command following the final `&&` or `||`, any command in a pipeline but the last (subject to the state of the `pipefail` shell option), or if the command’s return status is being inverted with `!`.
+> The shell does not exit if the command that fails is part of the command list immediately following a `while` or `until` reserved word, part of the test in an `if` statement, part of any command executed in a `&&` or `||` list except the command following the final `&&` or `||`, any command in a pipeline but the last (subject to the state of the `pipefail` shell option), or if the command's return status is being inverted with `!`.
 
 ```bash
 #!/usr/bin/env bash
@@ -280,7 +280,7 @@ fi
 # "any command in a pipeline but the last"
 false | echo "this will print" && echo "and so will this"
 
-# "or if the command’s return status is being inverted with '!'"
+# "or if the command's return status is being inverted with '!'"
 ! false && echo "this will print"
 ```
 

src/blog/discussion-guide-more-than-a-glitch.md

@@ -72,7 +72,7 @@ Ground rules:
 ## Chapter 8
 
 - The author shared a story of encountering an electronic medical/health record (EMR/EHR) system with restrictive options to describe her race. As machine learning's understanding of unstructured data progresses, do you think we could allow for more freeform answers on medical and legal forms?
-- The author gives a call to action to "‘call bullshit' on claims about future technology and a rosy tech-enabled future," as a response to a [2017 interview](https://www.newyorker.com/magazine/2017/04/03/ai-versus-md) with [Geoffrey Hinton](https://en.wikipedia.org/wiki/Geoffrey_Hinton). What technology is currently over-valued, either monetarily or in terms of hype from the media?
+- The author gives a call to action to "'call bullshit' on claims about future technology and a rosy tech-enabled future," as a response to a [2017 interview](https://www.newyorker.com/magazine/2017/04/03/ai-versus-md) with [Geoffrey Hinton](https://en.wikipedia.org/wiki/Geoffrey_Hinton). What technology is currently over-valued, either monetarily or in terms of hype from the media?
 - The author asserts that one perpetrator of bias is overvaluing experts' opinions in an area that isn't their expertise, such as technologists making statements about social science. What similar harm do you see technologists making today?
 
 ## Chapter 9

src/blog/slis-slos-and-slas-what-are-they.md

@@ -72,5 +72,5 @@ SLAs don't make sense for all companies or services, sometimes the consequence o
 ## More reading
 
 - Google: [SRE fundamentals: SLIs, SLAs and SLOs](https://cloud.google.com/blog/products/gcp/sre-fundamentals-slis-slas-and-slos)
-- Atlassian: [SLA vs. SLO vs. SLI: What’s the difference?](https://www.atlassian.com/incident-management/kpis/sla-vs-slo-vs-sli)
+- Atlassian: [SLA vs. SLO vs. SLI: What's the difference?](https://www.atlassian.com/incident-management/kpis/sla-vs-slo-vs-sli)
 - New Relic: [Best Practices for Setting SLOs and SLIs For Modern, Complex Systems](https://blog.newrelic.com/engineering/best-practices-for-setting-slos-and-slis-for-modern-complex-systems/)