Sanitize markdown content

1 files changed, 26 insertions, 28 deletions

diff --git a/_posts/2019-06-02-stateless-os.md b/_posts/2019-06-02-stateless-os.md
index 486a0c2..2f15c17 100644
--- a/_posts/2019-06-02-stateless-os.md
+++ b/_posts/2019-06-02-stateless-os.md
@@ -17,20 +17,20 @@ install and configure my whole OS using apt-get. When I found a
 GNU/Linux distribution that was built on top of the idea of
 declaratively specifying the whole OS I was automatically convinced[^3].
 
-I was impressed. Even though I\'ve been experiencing the benefits of Nix
+I was impressed. Even though I've been experiencing the benefits of Nix
 isolation daily, I always felt skeptical that something would be
 missing, because the devil is always on the details. But the result was
 much better than expected!
 
 There were only 2 missing configurations:
 
-1.  tap-to-click on the touchpad wasn\'t enabled by default;
-2.  the default theme from the gnome-terminal is \"Black on white\"
-    instead of \"White on black\".
+1.  tap-to-click on the touchpad wasn't enabled by default;
+2.  the default theme from the gnome-terminal is "Black on white"
+    instead of "White on black".
 
-That\'s all.
+That's all.
 
-I haven\'t checked if I can configure those in NixOS GNOME module, but I
+I haven't checked if I can configure those in NixOS GNOME module, but I
 guess both are scriptable and could be set in a fictional `setup.sh`
 run.
 
@@ -59,7 +59,7 @@ investing on it is worth it (both time-wise and happiness-wise).
 
 ### Emacs
 
-Right now I\'m using the [Spacemacs](http://spacemacs.org/), which is a
+Right now I'm using the [Spacemacs](http://spacemacs.org/), which is a
 community package curation and configuration on top of
 [Emacs](https://www.gnu.org/software/emacs/).
 
@@ -67,11 +67,11 @@ Spacemacs does support the notion of
 [layers](http://spacemacs.org/doc/LAYERS.html), which you can
 declaratively specify and let Spacemacs do the rest.
 
-However this solution isn\'t nearly as robust as Nix: being purely
+However this solution isn't nearly as robust as Nix: being purely
 functional, Nix does describe everything required to build a derivation,
 and knows how to do so. Spacemacs it closer to more traditional package
 managers: even though the layers list is declarative, the installation
-is still very much imperative. I\'ve had trouble with Spacemacs not
+is still very much imperative. I've had trouble with Spacemacs not
 behaving the same on different computers, both with identical
 configurations, only brought to convergence back again after a
 `git clean -fdx` inside `~/.emacs.d/`.
@@ -80,20 +80,19 @@ The ideal solution would be managing Emacs packages with Nix itself.
 After a quick search I did found that [there is support for Emacs
 packages in
 Nix](https://nixos.org/nixos/manual/index.html#module-services-emacs-adding-packages).
-So far I was only aware of [Guix support for Emacs
-packages](https://www.gnu.org/software/guix/manual/en/html_node/Application-Setup.html#Emacs-Packages).
+So far I was only aware of [Guix support for Emacs packages](https://www.gnu.org/software/guix/manual/en/html_node/Application-Setup.html#Emacs-Packages).
 
-This isn\'t a trivial change because Spacemacs does include extra
-curation and configuration on top of Emacs packages. I\'m not sure the
+This isn't a trivial change because Spacemacs does include extra
+curation and configuration on top of Emacs packages. I'm not sure the
 best way to improve this right now.
 
 ### myrepos
 
-I\'m using [myrepos](https://myrepos.branchable.com/) to manage all my
+I'm using [myrepos](https://myrepos.branchable.com/) to manage all my
 git repositories, and the general rule I apply is to add any repository
-specific configuration in myrepos\' `checkout` phase:
+specific configuration in myrepos' `checkout` phase:
 
-``` {.shell}
+```shell
 # sample ~/.mrconfig file snippet
 [dev/guix/guix]
 checkout =
@@ -118,20 +117,19 @@ all](https://git.sr.ht/~euandreh/dotfiles/tree/316939aa215181b1d22b69e94241eef75
 I wonder if something like [GNU
 Stow](https://www.gnu.org/software/stow/) can help me simplify this.
 
-Conclusion
-----------
+## Conclusion
 
-I\'m really satisfied with NixOS, and I intend to keep using it. If what
-I\'ve said interests you, maybe try tinkering with the [Nix package
+I'm really satisfied with NixOS, and I intend to keep using it. If what
+I've said interests you, maybe try tinkering with the [Nix package
 manager](https://nixos.org/nix/) (not the whole NixOS) on your current
 distribution (it can live alongside any other package manager).
 
 If you have experience with declarative Emacs package managements, GNU
-Stow or any similar tool, etc., [I\'d like some
-tips](mailto:eu@euandre.org). If you don\'t have any experience at all,
-[I\'d still love to hear from you](mailto:eu@euandre.org).
+Stow or any similar tool, etc., [I'd like some
+tips](mailto:eu@euandre.org). If you don't have any experience at all,
+[I'd still love to hear from you](mailto:eu@euandre.org).
 
-[^1]: \"Last week\" as of the start of this writing, so around the end
+[^1]: "Last week" as of the start of this writing, so around the end
     of May 2019.
 
 [^2]: I was using a 32GB RAM, i7 and 250GB SSD Samsung laptop. The
@@ -141,7 +139,7 @@ tips](mailto:eu@euandre.org). If you don\'t have any experience at all,
     space.
 
 [^3]: The declarative configuration aspect is something that I now
-    completely take for granted, and wouldn\'t consider using something
-    which isn\'t declarative. A good metric to show this is me realising
-    that I can\'t pinpoint the moment when I decided to switch to NixOS.
-    It\'s like I had a distant past when this wasn\'t true.
+    completely take for granted, and wouldn't consider using something
+    which isn't declarative. A good metric to show this is me realising
+    that I can't pinpoint the moment when I decided to switch to NixOS.
+    It's like I had a distant past when this wasn't true.