Updated 1.1 To Arkenfox or Not (markdown)

1.1-To-Arkenfox-or-Not.md

@@ -1,12 +1,12 @@
-🟩 FOREWORD
+🟩 **FOREWORD**
 
 Arkenfox is a resource, feel free to use any, all or none of it - just **HEED** the warnings, notes and documentation.
 
-🟪 TOR BROWSER
+🟪 **TOR BROWSER**
 
 If your threat model calls for anonymity and advanced fingerprinting protection, **[USE TOR BROWSER](https://www.torproject.org/)**. You can also use Tor Browser for [everyday browsing](https://2019.www.torproject.org/about/torusers.html) as another secondary browser. However, you're going to want a non-Tor Browser browser too, which is Firefox, so carry on reading :).
 
-🟪 A FEW SETTINGS & EXTENSIONS
+🟪 **A FEW SETTINGS & EXTENSIONS**
 
 **For most people, this is all you really need.**
 
@@ -28,7 +28,7 @@ After that, the benefits get incrementally smaller, but they do add up: your mil
 
 <sup>1</sup> Sanitizing refers to clearing site and other data such as caches and histories.
 
-🟪 FINGERPRINTING
+🟪 **FINGERPRINTING**
 
 Most of the above deals with [state](https://developer.mozilla.org/en-US/docs/Web/Privacy/State_Partitioning) <sup>1</sup> and other cross-origin linkability mechanisms such as navigational tracking.
 
@@ -36,7 +36,7 @@ Stateless tracking, or fingerprinting, is a little more complex. If your threat
 
 <sup>1</sup> State refers to stored (disk/memory) client-side data such as those listed [here](https://privacycg.github.io/storage-partitioning/).
 
-🟪 EXPECTATIONS
+🟪 **EXPECTATIONS**
 
 If you're going to use arkenfox's user.js, then don't expect to just start using it as is. You **WILL NEED TO CREATE OVERRIDES**, and **FULLY** read this wiki.