diff --git a/3.3-Updater-Scripts.md b/3.3-Updater-Scripts.md
index f872254..c32dbc3 100644
--- a/3.3-Updater-Scripts.md
+++ b/3.3-Updater-Scripts.md
@@ -131,7 +131,7 @@ a couple things to note here:
 * the netinfo line was merged but the pref has been moved to 4600 in the updated user.js (see info below)
 * the special comment-out command was also appended at the bottom as a reminder that you gave that command
 
-With `-merge` it's best to always add a comment behind your overrides to make them easily noticeable when you compare your new user.js with one of your backups. A good way is to use the number of the pref's section. That will also make it easier to spot when a pref you want to override gets moved to a commented-out section like `9999: DEPRECATED` or `4600: RFP ALTERNATIVES`, resulting in your override becoming inactive, which may or may not be what you want. (see `dom.netinfo.enabled` in the example) If that's not what you want, you can prepend the `dom.netinfo.enabled` line with a TAB or JS multi-line-comment (or in v4.0+ one or more spaces also works), like this:
+With `-merge` it's best to always add a comment behind your overrides to make them easily noticeable when you compare your new user.js with one of your backups. A good way is to use the number of the pref's section. That will also make it easier to spot when a pref you want to override gets moved to a commented-out section like `9999: DEPRECATED` or `7000: DON'T BOTHER`, resulting in your override becoming inactive, which may or may not be what you want. (see `dom.netinfo.enabled` in the example) If that's not what you want, you can prepend the `dom.netinfo.enabled` line with a TAB or JS multi-line-comment (or in v4.0+ one or more spaces also works), like this:
 ```js
     user_pref("dom.netinfo.enabled", false); // 25xx - enforcing false -- prepended with a TAB
 /* !!! */ user_pref("dom.netinfo.enabled", false); // 25xx - enforcing false -- or a JS-multi-line comment