fixup! Find and replace straight quotes with smart quotes

src/content/posts/2011-10-06-avoid-git-first-drafts.mdx

@@ -36,7 +36,7 @@ control can serve as an indicator as to not only when and how things were done,
 but also *why*[^1]. If you publish history exactly as it was, you lose this
 clarity.
 
-A book author never publishes first drafts. Book readers never see the book
+A book author never publishes first drafts. Book readers never see the book
 with rough around the edges. So readers puzzle less, altogether avoiding
 questions like, what does the author mean here? Or, did he really mean to
 include this sentence?
@@ -57,7 +57,7 @@ of code as hostile. You might as well make things easy as possible for future
 readers, yourself included.
 
 First, commit often in logical, functioning steps, to ease wrapping your head
-around the change and later reapplying or reverting it. Keep up to date but
+around the change and later reapplying or reverting it. Keep up to date but
 erase superfluous merge commits. Then clean up and reorder code and history
 before pushing. Make it as correct as possible and easy to follow.
 

src/content/posts/2014-01-28-good-ideas-from-mobile-design-that-are-good-everywhere.mdx

@@ -155,7 +155,7 @@ Then I’ll mix in what _I wish_ was in the report.
       </li>
       <li>
         <a href='#dont-restyle-form-inputs--scrollbars'>
-          {'Don’t Restyle Form & Inputs Scrollbars'}
+          {'Don’t Restyle Form Inputs & Scrollbars'}
         </a>
       </li>
       <li>