From 8aab42140de686de4a254e52aae368980482e658 Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Sun, 26 Mar 2017 16:36:02 +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 80ab013..07ddc03 100644 --- a/1.1-Overview.md +++ b/1.1-Overview.md @@ -28,7 +28,7 @@ Here is how it basically works: * If you reset a value to `default`, it is removed from `prefs.js` * If you reset a `hidden preference` to default, the value will be blank, and assuming it is not applied again from a `user.js`, it will then vanish on the next restart -tl;dr: firefox starts :arrow_right: user.js active preferences :arrow_right: prefs.js :arrow_right: `about:config` .. with caveats +tl;dr: firefox starts :arrow_right: user.js active preferences :arrow_right: prefs.js :left_right_arrow: `about:config` .. with caveats That's a bit to digest, so here is a pretty picture showing a preference with the same value as status `user set` and `default`. In `about:config's` search box, you can use wildcards (e.g `network*policy`) to save time typing, and it is case insensitive.