From: MinxAa <99985274+MinxAa@users.noreply.github.com>
Date: Fri, 18 Feb 2022 17:10:46 +0000 (+0100)
Subject: Update README.md - Preferences, fix grammar
X-Git-Tag: v3.7~4^2
X-Git-Url: https://git.p6c8.net/policy-templates.git/commitdiff_plain/70e04efd7ebe7ae63bbcc4c71bb9b677a37ff518

Update README.md - Preferences, fix grammar

Hope I fixed the grammar here.
---

diff --git a/README.md b/README.md
index 21ea6c7..8735384 100644
--- a/README.md
+++ b/README.md
@@ -4334,10 +4334,10 @@ Using the preference as the key, set the `Value` to the corresponding preference
 
 `Status` can be "default", "locked", "user" or "clear"
 
-* `"default"`: Read/Write: Setting appear as default even if factory default differs.
-* `"locked"`: Read-Only: Setting appear as default even if factory default differs.
-* `"user"`: Read/Write: Setting appear as changed if it differ from factory default.
-* `"clear"`: Read/Write: `Value` has no effect. Resets to factory default on each startup.
+* `"default"`: Read/Write: Settings appear as default even if factory default differs.
+* `"locked"`: Read-Only: Settings appear as default even if factory default differs.
+* `"user"`: Read/Write: Settings appear as changed if it differs from factory default.
+* `"clear"`: Read/Write: `Value` has no effect. Resets to factory defaults on each startup.
 
 `"user"` preferences persist across invocations of Firefox. It is the equivalent of a user setting the preference. They are most useful when a preference is needed very early in startup so it can't be set as default by policy. An example of this is ```toolkit.legacyUserProfileCustomizations.stylesheets```.