More footnote cleanup v3

4 files changed, 11 insertions, 11 deletions

diff --git a/posts/hamburger-menu-alternative.md b/posts/hamburger-menu-alternative.md
index 47af1a1..ded2065 100644
--- a/posts/hamburger-menu-alternative.md
+++ b/posts/hamburger-menu-alternative.md
@@ -116,4 +116,4 @@ That really depends on your project or overall mobile design (I know, such a hel
 
 That's it. I hope I've inspired you to try out sausage links in the near future or at least made you think more deeply about mobile navigation design!
 
-<small>...is anyone else really hungry now?</small>
+...is anyone else really hungry now?
diff --git a/posts/openring.md b/posts/openring.md
index f91138c..42ac0d8 100644
--- a/posts/openring.md
+++ b/posts/openring.md
@@ -24,7 +24,7 @@ You *could* setup a whole new directory specifically for your openring files, bu
 
 ### openring-in.html Contents
 
-```
+~~~html
 <!-- License-Id: CC0-1.0 -->
 <section class="webring">
   <h3>Articles from blogs I follow around the world wide web</h3>
@@ -75,7 +75,7 @@ You *could* setup a whole new directory specifically for your openring files, bu
   color: #555;
 }
 </style>
-```
+~~~
 
 > Sidenote: You will get minor Liquid Syntax warnings in the console when running your website via `serve` or `build`. I don't really mind those warnings but if you do, feel free to move these files out into their own sub-directory in your project folder.
 
@@ -89,7 +89,7 @@ To simplify things, we are going to place our main commands in a single build sc
 
 Place the following inside that file:
 
-```
+~~~sh
 openring \
   -s https://example.com/feed.xml \
   -s https://example.com/feed.xml \
@@ -97,25 +97,25 @@ openring \
   < _includes/openring-in.html \
   > _includes/openring-out.html
 bundle exec jekyll build
-```
+~~~
 
 ## Edit `_config.yml`
 
 Next we need to make sure we exclude our new `build-site` script file, since we really don't need that pushed up to the main server:
 
-```
+~~~sh
 # Includes / Excludes
 exclude:
   - build-site.sh
-```
+~~~
 
 ## Almost Done...
 
 Now you just need to decide where you want your `openring` feed outputs to render. For this example, we will place them at the bottom of every blog post inside the `_layouts/post.html` file, like so:
 
-```
+~~~ruby
 {% raw %}{% include openring-out.html %}{% endraw %}
-```
+~~~
 
 ## Build It & They Will Come
 
diff --git a/posts/still-using-jquery.md b/posts/still-using-jquery.md
index b30c25d..2c889ea 100644
--- a/posts/still-using-jquery.md
+++ b/posts/still-using-jquery.md
@@ -27,4 +27,4 @@ As long as all of these items are accomplished, I don't care if the project was
 
 So use whatever tools make you a happier developer, as long as your projects don't suffer because of them.
 
-[^1]: This would obviously be terrible for development, but its just an extreme example</small>
+[^1]: This would obviously be terrible for development, but its just an extreme example
diff --git a/posts/they-wont-wait.md b/posts/they-wont-wait.md
index 2291d69..a8f6a71 100644
--- a/posts/they-wont-wait.md
+++ b/posts/they-wont-wait.md
@@ -36,7 +36,7 @@ If my terrible analogy wasn't enough to convince you to implement better perform
 - [Mozilla](https://blog.mozilla.org/metrics/2010/04/05/firefox-page-load-speed-%E2%80%93-part-ii/): Shaving 2.2 seconds off page load time increased downloads by 15.4%
 - [Yahoo](https://www.slideshare.net/stubbornella/designing-fast-websites-presentation/23-1_Create_a_component_library): 400 ms resulted in a 5 to 9% drop in traffic
 
-<small>All data taken from [instant.page](https://instant.page) (which I am a huge fan of &hearts;)</small>
+All data taken from [instant.page](https://instant.page) which I am a huge fan of &hearts;
 
 The fact something as small as 100 ms can have such a profound impact on your bottom-line should be eye-opening. You're leaving money of the table by not tackling even the low-hanging, easy performance wins. You need to start valuing your users' time and stop serving them excessive garbage they never asked for.