diff --git a/3.4-Apply-&-Update-&-Maintain.md b/3.4-Apply-&-Update-&-Maintain.md index dfd0e9c..606d23f 100644 --- a/3.4-Apply-&-Update-&-Maintain.md +++ b/3.4-Apply-&-Update-&-Maintain.md @@ -1,26 +1,23 @@ 🟩 Previous: [Overrides [To RFP or Not]](https://github.com/arkenfox/user.js/wiki/3.3-Overrides-[To-RFP-or-Not]) -🟥 Summary: **It's so simple, we do not need one, even for a peacock**. - --- #### 🟪 APPLY If you are not using a new profile, we recommend running our [cleanup script](https://github.com/arkenfox/user.js/blob/master/scratchpad-scripts/arkenfox-cleanup.js), the instructions are in the file. -🔹 Put all the relevant files into the root folder of your profile [1] +- 🔹 Put all the relevant files into the root folder of your profile [1] - `prefsCleaner` - `updater` - `user.js` - `user-overrides.js` (which you created) - -Continue with the UPDATE part below. +- 🔹 Continue with the UPDATE part below [1] To find your profile, open `about:support` and look for `Profile Folder` under `Application Basics`. #### 🟪 UPDATE -- 🔹 run the updater +- 🔹 Run the updater - so the contents of your `user-overrides.js` is appended to the `user.js` - 🔹 ALWAYS run prefsCleaner - make sure Firefox is closed @@ -29,9 +26,12 @@ Continue with the UPDATE part below. #### 🟪 MAINTAIN -Arkenfox changes to the live master happen once per release: all changes are done in a separate branch and only merged when finished. There is no guarantee when it is done - hopefully within a week of the Firefox release. Nothing of consequence changes these days that will affect you in that time delay. +Each release 1 +- 🔹 Check for the latest [changelog](https://github.com/arkenfox/user.js/issues?utf8=✓&q=is%3Aissue+label%3Achangelog) +- 🔹 Run the updater +- 🔹 Run prefsCleaner -So ... once a release ... check for the latest [changelog](https://github.com/arkenfox/user.js/issues?utf8=✓&q=is%3Aissue+label%3Achangelog), run the updater, and run prefsCleaner (with Firefox closed). +1 Arkenfox changes to the live master happen once per release: all changes are done in a separate branch and only merged when finished. There is no guarantee when it is done - hopefully within a week of the Firefox release. Nothing of consequence changes these days that will affect you in that time delay. ---