From d70cd70f60d4018b685d228182ade4ad02a81c96 Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Sun, 26 Mar 2017 03:20:32 +1300 Subject: [PATCH] Updated 1.1 Overview (markdown) --- 1.1-Overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1.1-Overview.md b/1.1-Overview.md index b515f2c..80ab013 100644 --- a/1.1-Overview.md +++ b/1.1-Overview.md @@ -38,7 +38,7 @@ And why would you want a `user.js`? * It is used to reset settings on a restart, making certain preferences more or less "permanent". You can still change preferences via about:config for testing * It can be used to migrate a lot of settings to a new profile, and can be easily modified and deployed for multiple profiles * There are a lot of preferences in `about:config`. There are over 3000 firefox ones alone. A `user.js` is a great repository for information. For example, it can be used as a basis for `mozilla.cfg` files and `lockprefs`. -* It will teach you how to protect your privacy, enhance your security, and reduce fingerprinting +* It can help you to better understand how to protect your privacy, enhance your security, and reduce fingerprinting ## Working with a user.js