diff --git a/3.3-Updater-Scripts.md b/3.3-Updater-Scripts.md
index 2cf25d9..4092452 100644
--- a/3.3-Updater-Scripts.md
+++ b/3.3-Updater-Scripts.md
@@ -19,6 +19,7 @@ Unless you want to use the `user.js` exactly as it is, you **must** follow our n
 Available command-line parameters (case-insensitive):
 - `-MultiOverrides`
 uses any and all .js files in a `user.js-overrides` sub-folder as overrides instead of the default `user-overrides.js` file. Files are appended in alphabetical order.
+- `-singleBackup` to use a single backup file and overwrite it on new updates, instead of cumulative backups. This was the default behaviour before v4.3.
 - `-unattended`
 runs the script without user-input
 - `-updatebatch`
@@ -64,7 +65,7 @@ user_pref("dom.netinfo.enabled", false); // 25xx - enforcing false
 user_pref("browser.startup.homepage", "https://www.foo.bar/"); // 01xx
 ```
 
-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 user.js.bak. 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 `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:
 ```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