diff --git a/1.7-Extension-Exceptions.md b/1.7-Extension-Exceptions.md
index b31a005..f208c14 100644
--- a/1.7-Extension-Exceptions.md
+++ b/1.7-Extension-Exceptions.md
@@ -1,4 +1,4 @@
-:small_orange_diamond: The Issue
+### :small_orange_diamond: The Issue
 
 Cookies control access to **local storage** and **indexedDB**. The `ghacks user.js` denies cookies by default. This is the pref `network.cookie.cookieBehavior` (see `2701`). A value of `2` denies all cookies, a value of `1` allows first party only.
 
@@ -6,13 +6,13 @@ Extensions <sup>1</sup> that use local dom storage and/or indexedDB **will break
 
 <sup>1</sup> `Extensions` = Web Extensions API, `Legacy Extensions` = legacy APIs or the Add-on SDK.
 
-:small_orange_diamond: Strategy
+### :small_orange_diamond: Strategy
 
 You have two choices
  - Allow first party cookies and use an extension to clean up and/or block cookies and storage
  - Deny all cookies and use site exceptions, **including** exceptions for extensions that need it. And you can still use an extension to clean up and control those cookies and storage if you want.
 
-:small_orange_diamond: How To Set Extension Cookie Exceptions
+### :small_orange_diamond: How To Set Extension Cookie Exceptions
 
 - Open `about:debugging > Add-ons`
 - Click on the `Manifest URL` of the extension
@@ -23,7 +23,7 @@ You have two choices
 
 You can view cookie exceptions under Options > Privacy & Security > History > custom settings > Accept cookies from websites > Exceptions
 
-:small_orange_diamond: Notes
+### :small_orange_diamond: Notes
 - The exception uses the extension's `UUID`, which is a random unique value generated on each install of the extension.
 - If you are cleaning cookies via a third party appllication, such as CCleaner, make sure to keep these cookies