diff --git a/content/post/emacs_clang_libopencm3.md b/content/post/emacs_clang_libopencm3.md
index 81c4605..e0df48c 100644
--- a/content/post/emacs_clang_libopencm3.md
+++ b/content/post/emacs_clang_libopencm3.md
@@ -95,20 +95,15 @@ For an STM32F0 project, the context of the `.clang_complete` file would be:
 <sub>The above assumes that `libopencm3` is also places within the project
 directory</sub>
 
-
-## Example
-
 {{% admonition warning Note %}}
 There is a strange issue that is encountered with non-working completion for new
-header include statements.
-<br/>
-<br/>
-The workaround for this includes running <code>M-x irony-server-kill</code>
-after new header additions to your current working file. Irony's server is
-clever enough to restart itself after a completion request is triggered via
-<code>TAB</code> so this is a fairly uninvolved workaround.
+header include statements. The workaround for this includes running `M-x irony-server-kill`after new header
+additions to your current working file. Irony's server is clever enough to
+restart itself after a completion request is triggered via `TAB` so this is a
+fairly uninvolved workaround.
 {{% /admonition %}}
 
+## Example
 {{< img src="/static/img/emacs-clang-libopencm3/completion.png"
     sub="Completion" >}}
 
diff --git a/content/post/gpg_best_practices_and_git.md b/content/post/gpg_best_practices_and_git.md
index 4ece434..b3c4e80 100644
--- a/content/post/gpg_best_practices_and_git.md
+++ b/content/post/gpg_best_practices_and_git.md
@@ -80,8 +80,8 @@ Once the signature has been verified, the CA can be moved over to
 `/usr/share/ca-certificates` to update the list of trusted CA certificates. Do
 this via:
 
-+ `sudo update-ca-trust` (_Arch_)
-+ `sudo update-ca-certificates` (_Debian/Ubuntu, RHEL_)
++ **ArchLinux:** `sudo update-ca-trust`
++ **Debian/Ubuntu, RHEL:** `sudo update-ca-certificates`
 
 
 {{% admonition tip "CA Path" %}}
@@ -93,21 +93,24 @@ On my system the full path to the CA certs is:
 Two following parameters should be added to your `~/.gnupg` configuration files:
 
 ### GnuPG Versions >2.1
+
+
 {{% admonition note "gpg.conf" %}}
-```apacheconf
+```
 keyserver hkps://hkps.pool.sks-keyservers.net
 ```
 {{% /admonition %}}
 
+
 {{% admonition note "dirmngr.conf" %}}
-```apacheconf
+```
 hkp-cacert /etc/ca-certificates/path/to/CA.pem
 ```
 {{% /admonition %}}
 
 ### GnuPG Versions <2.1
 {{% admonition note "gpg.conf" %}}
-```apacheconf
+```
 keyserver hkps://hkps.pool.sks-keyservers.net
 keyserver-options ca-cert-file=/path/to/CA/sks-keyservers.netCA.pem
 ```
diff --git a/content/post/stm32-part0.md b/content/post/stm32-part0.md
index 17035c9..6d87cb9 100644
--- a/content/post/stm32-part0.md
+++ b/content/post/stm32-part0.md
@@ -14,11 +14,11 @@ series: turn on the lights!
 
 <!--more-->
 
-{{% admonition info "Note to Windows Users" %}}
+{{% admonition warning "Windows Users" %}}
 This series of write-ups assumes the reader is on a Linux operating
-system. Windows users <i>can</i> utilize the <a
-href="https://docs.microsoft.com/en-us/windows/wsl/install-win10"><b>Windows
-Subsystems for Linux</b></a> though your mileage may vary!
+system. Windows users _can_ utilize the [**Windows Subsystems for
+Linux**](https://docs.microsoft.com/en-us/windows/wsl/install-win10) though your
+mileage may vary!
 {{% /admonition %}}
 
 # Straight to the Chase
@@ -113,7 +113,7 @@ Makefile's variables of things you may want to change:
 
 {{% admonition info "Naming Convention" %}}
 As a note to the reader: below I will not refer to the GPIO port or pins using
-the <code>#define</code> friendly names from above. This is purely for the sake
+the `#define` friendly names from above. This is purely for the sake
 of clarity in hopes of avoiding confusion.
 {{% /admonition %}}