Fix wording, grammar, and otherwise bad use of the English language

_pages/en_US/badrecovery.txt

@@ -5,71 +5,55 @@ title: "BadRecovery/OlyBmmer"
 {% include toc title="Table of Contents" %}
 
 ## Prerequisites
-- A USB drive, preferably 8gb or larger, for the modded recovery image.
+- A USB drive, preferably 8gb or larger, for the patched recovery image.
 
-## Section I - Downloading a Recovery image
+## Section I - Downloading a Recovery Image
 
-First things first, you need to grab a recovery image lower than v125 for your board.
+First, you need a recovery image lower than v125 for your board.
 
 - https://chrome100.dev
 
-## Section II - Mod the Recovery image
+## Section II - Patch the Recovery image
 
-Vist the [BadRecovery Web Bulider](https://binbashbanana.github.io/badrecovery) and upload the RAW recovery image. choose auto and wait a couple of minute and it should download automatically.
+Vist the [BadRecovery Web Bulider](https://binbashbanana.github.io/badrecovery) and upload the unpatched (colloquially: "raw") recovery image. Select `Auto` and wait for the process to complete. The patched image should download automatically.
 
-## Section III - Flashing the image
+## Section III - Flashing the Image
 
-Did it download automatically? Amazing! Please follow the next instructions for
-flashing.
+Now, we need to flash the recovery image to a USB drive. Follow the below steps for your platform:
 
-### Across all platforms (ChromeOS, Mac, Windows, Linux, etc.)
+### On *nix
 
-If you are using a Chromium browser, Download the Chromebook Recovery Utility and click on "Use Local Image" on the dropdown menu.
+On a ChromeOS device in developer mode, you can also use the following instructions to flash the drive. Otherwise, you can download the [Chromebook Recovery Utility]() from the Chrome Webstore and use that to flash the drive. Just click on the top right button in the window and select "Use Local File", then select your .bin file. This probably won't work on an enrolled device, but if the extension is unblocked, you can do it entirely on that Chromebook.
+{: .notice--info}
 
-Select your modded recovery image you made earlier and click Continue.
+Good choice of operating system, by the way. Most distros will come with the `dd` utility built-in. If yours doesn't, then choose a different distro or find a way to flash the recovery image. Run the following command, making sure that you have the correct /dev path to your USB drive and the correct path to your recovery image:
 
-WARNING: All data on this USB will be lost. Consider making a backup of the USB
-if this is the only one laying around you.
-{: .notice--danger}
-
-Once done, you should plug the USB into your chromebook and hit ESC+REFRESH+POWER.
-Recovery should now start. Sit back and relax until the BadRecovery screen pops up.
-
-### Linux
+```sh
+dd if=/path/to/recovery-image.bin of=/dev/sdX status=progress
+```
 
-Run
-```dd if=/path/to/yourmoddedrecoimage.bin of=/dev/sdWHATEVERYOURUSBIS```
+In a few minutes, you should be done, and the command should exit with a 0 exit code.
 
-MAKE SURE YOU ARE NOT FLASHING TO YOUR INTERNAL DISK! DOING SO WILL
-RESULT IN LOSS OF DATA!
-{: .notice--danger}
+### On Windows
 
-If all goes well, the command will finish with no errors.
-A 0 exit code is not a error, please ignore that.
+Download [Rufus](https://rufus.ie/) and run the executable. Select the .bin file you just downloaded and select your USB drive. Click on flash and follow the prompts. If asked, select "Flash in DD mode".
 
-### Windows
-Download [Rufus](https://rufus.ie), run the exe and select the raw image. Choose DD mode if prompted. Click START to Continue.
+### On MacOS
 
-### MacOS
-Download [Etcher](https://www.balena.io/etcher) and run the executable/appimage. Click allow for everything. Select the modded reco image and your USB drive.
+Download [Etcher](https://www.balena.io/etcher) and run the excutable. Select the .bin file and your USB drive. Click on flash and follow the prompts.
 
 ## Section IV - Booting BadRecovery
 
-Unlike SH1MMER, DO NOT enter devmode unless you have a ancient board (pre-CR50).
-
-Instead simply press ESC+REFRESH+POWER and plug in your USB.
-
-The recovery process should start.
+Unlike SH1mmer, do not enter devmode unless you have a ancient board (pre-CR50).
 
-After a while you should get kicked to a BadRecovery screen. Let it remove
-FWMP and enable dev mode. If it shows a error of tpmc failing to remove FWMP, your chromebook is incompatible to the exploit. (This issue is not really common anymore since the latest version patched this.)
+Instead simply enter recovery normally (`Esc+Refresh+Power`) and plug in your drive. The recovery process should start, and after a while you should get kicked to a BadRecovery screen. Let it remove FWMP and enable dev mode. If it shows a error about tpmc failing to remove FWMP, your Chromebook is incompatible with the exploit. (This issue is not neccesarily common anymore since the latest version patched this.)
 
-Now press Refresh and Power.
+Now, perform an EC reset (`Refresh+Power`).
 
 Please note that your admin can see that your device is offline. If you are not allowed to do this, set your kernver to 0 and reenroll using KVS.
 {: .notice--danger}
 
-## Section VI- Postmodem
+## Section VI - Postmodem
 
 If you want to reenroll but want to unenroll at anytime, continue to [kvs](kvs)
 {: .notice--success}

_pages/en_US/choose-halcyon.txt

@@ -32,7 +32,7 @@ Your device is compatible with two exploit chains - E-Halcyon and traditional WP
 
 Chosen an exploit chain? Great! Select a next step below.
 
-If you want to boot E-Halcyon or install it in semi-tethered mode, continue to [SH1MMER Unenrollment](sh1mmer)
+If you want to boot E-Halcyon or install it in semi-tethered mode, continue to [SH1mmer Unenrollment](sh1mmer)
 {: .notice--success}
 
 Or, if you want to disable WP and unenroll normally, continue to [Identifying Firmware WP](identify-wp)

_pages/en_US/faq.txt

@@ -13,13 +13,13 @@ Yes, your administrator can see that you've unenrolled. More specifically - your
 {% capture compat %}
 <summary><u>Are there any risks of permanently damaging my Chromebook?</u></summary>
 
-Short answer: No. Slightly longer answer: Not unless you fuck up really, *really* badly. (if you do, consider yourself to be a honorary skid) Basically, just follow the instructions and you'll be fine.
+Short answer: No. Slightly longer answer: Not unless you fuck up really, *really* badly. Basically, just follow the instructions and you'll be fine.
 {% endcapture %}
 <details>{{ compat | markdownify }}</details>
 
 {% capture compat %}
 <summary><u>Help! I got a "ChromeOS is Missing or Damaged" screen and don't know what to do!</u></summary>
 
-Use a recovery drive. If ChromeOS refuses to load it, check that you got the right board on [Chrome100](https://chrome100.dev/). If that doesn't work, make sure that this screen isn't intentional, as it is in fakemurk. If none of that works, consult (here)[https://www.youtube.com/watch?v=GU4Hw-xbBNo] for instructions on how to fix it.
+Use a recovery drive. If ChromeOS refuses to load it, check that you got the right board on [Chrome100](https://chrome100.dev/). If that doesn't work, make sure that this screen isn't intentional, as it is in fakemurk.
 {% endcapture %}
 <details>{{ compat | markdownify }}</details>

_pages/en_US/finalizing-setup.txt

@@ -4,72 +4,9 @@ title: "Finalizing Setup"
 
 {% include toc title="Table of Contents" %}
 
-## Section I - Disable Extensions (if neccecary)
+## Section I - Finished!
 
-You can skip this step if you already installed murkmod.
-
-Try to open crosh (`Ctrl+Alt+T`). If you can't open crosh due to an extension block, then create a new folder in your Downloads named `disable-extensions`. Fakemurk will automagically disable extensions so you can use crosh.
-
-## Section II - Install Reccomended Murkmod Plugins
-
-This section is only appliccable if you installed murkmod.
-{: .notice--info}
-
-Open crosh (`Ctrl+Alt+T`) and select "Install Plugins". Type the following lines at the prompt, one at a time:
-
-```
-mrchromebox-fwscript.sh
-neofetch.sh
-wallpaper.sh
-wssocks.sh
-mac-randomizer.sh
-fakeapk.sh
-q
-```
-
-FakeAPK is an incredibly useful tool when it comes to fakemurked Chromebooks. If you chose not to install murkmod, then you can install it with:
-`sudo curl -LOk https://raw.githubusercontent.com/clockworkindustries/FakeAPK/main/fakeapk.sh && sudo bash fakeapk.sh
-` from a root shell.
-{: .notice--info}
-
-## Section III - Disable Admin-Installed Extensions
-
-Hard-disabling and hard-enabling extensions is a time-consuming process. If you're under surveilance unpredictably, you might want to be able to quickly toggle on and off certain extensions. Leave these extensions hard-enabled, then see the [LtBEEF Guide](ltbeef)
-{: .notice--info}
-
-Select "Hard Disable Extensions" and, at the prompt, enter the extension ID corresponding to the extension you want to disable (only applies for murkmod, fakemurk alone will allow you to disable only a few of these extensions):
-
-- GoGuardian - `haldlgldplgnggkjaafhelgiaglafanh`
-- Securly - `iheobagjkfklnlikgihanlhcddjoihkg` (webstore extension) or `joflmkccibkooplaeoinecjbmdebglab` (non-webstore extension)
-- OrbitNote - `feepmdlmhplaojabeoecaobfmibooaid`
-- Screenshot reader - `enfolipbjmnmleonhhebhalojdpcpdoo`
-- Read and Write for Google Chrome - `inoeonmfapjbbkmdafoankkfajkcphgd`
-- Gopher Buddy - `cgbbbjmgdpnifijconhamggjehlamcif`
-- Clever Plus - `dikiaagfielfbnbbopidjjagldjopbpa`
-- LightSpeed - `adkcpkpghahmbopkjchobieckeoaoeem`
-- Cisco Umbrella - `jcdhmojfecjfmbdpchihbeilohgnbdci`
-- ContentKeeper Authenticator - `jdogphakondfdmcanpapfahkdomaicfa`
-- Hapara - `aceopacgaepdcelohobicpffbbejnfac`
-- iboss - `kmffehbidlalibfeklaefnckpidbodff`
-- LightSpeed Classroom - `jaoebcikabjppaclpgbodmmnfjihdngk`
-- Blocksi - `ghlpmldmjjhmdgmneoaibbegkjjbonbk`
-- Linewize - `ddfbkhpmcdbciejenfcolaaiebnjcbfc`
-- Securly Classroom - `jfbecfmiegcjddenjhlbhlikcbfmnafd`
-- Impero - `jjpmjccpemllnmgiaojaocgnakpmfgjg`
-
-## Section IV - Install RW_LEGACY firmware
-
-Select Plugins (option 4 in murkmodded mush) and select "Run MrChromebox's firmware utility script". After a short bit of loading, it will present you with a menu that looks like this:
-
-![]({{ "./images/mrchromeboxfw.png" | absolute_url }})
-
-Select option 1, and the firmware will be installed. Then, press `Q` to quit.
-
-## Section V - Setup APK installation and AuroraStore
-
-Select Plugins and select "Install/Uninstall FakeAPK". At the menu, select `1` (Enable FakeAPK). When prompted, press enter to reboot. Upon rebooting, sign back in and download the [Aurora Store APK](https://gitlab.com/AuroraOSS/AuroraStore/uploads/bbc1bd5a77ab2b40bbf288ccbef8d1f0/AuroraStore_4.1.1.apk). Find it in your Downloads folder and double-click it. After a short wait, it will prompt you to confirm installing an "unsecure app". Click Continue, and installation will commence. Confirm installation if prompted, and then launch the Aurora Store app from your launcher (press the `Search` key). It will prompt you to perform initial configuration. Leave the default value for everything (except the color theme, feel free to mess with that). When prompted to log in, just select "Log in with Google" and sign in with your home account.
-
-## Section VI - Finished!
+This page was butchered because murkmod has been updated a lot since this guide was originally written - which is great for ease of use, but renders this page almost entirely obsolete. I'll get to it Eventually™.
 
 You're done with the guide! Congrats! At the end of the year, you'll need to [Re-Enroll your Device](re-enroll)
 {: .notice--success}

_pages/en_US/halcyon.txt

@@ -24,7 +24,7 @@ After a few minutes, the script should output a success message and you'll be go
 
 ## Section II - Flashing your Image and Booting
 
-By this point, you should have the steps down. Just flash the image that you just modified identically to how you flashed SH1MMER previously. From here, the steps differ significantly.
+By this point, you should have the steps down. Just flash the image that you just modified identically to how you flashed SH1mmer previously. From here, the steps differ significantly.
 
 Enter recovery mode (`Esc+Refresh+Power`) and enable developer mode (`Ctrl+D` and `Enter`). At the "developer mode blocked" screen, enter recovery mode again (`Esc+Refresh+Power`). At this point, you should plug in your RecoMod drive and begin to spam the `E` key on the keyboard. This is a critical step and cannot be skipped. RecoMod will begin a 5-minute wait sequence (you can watch it tick down if you like, it's in the top left hand corner of the screen), at which point you can stop spamming the `E` key. Once the timer nears the end, begin spamming the `E` key again. After a few seconds, a boot screen will show and you will be presented with a menu.
 

_pages/en_US/sh1mmer.txt

@@ -1,5 +1,5 @@
 ---
-title: "SH1MMER Unenrollment"
+title: "SH1mmer Unenrollment"
 ---
 
 {% include toc title="Table of Contents" %}
@@ -8,8 +8,8 @@ title: "SH1MMER Unenrollment"
 
 - A USB drive, 8gb or larger, for the modified shim
 
-Please note that SH1MMER has been patched for later devices with leaked shims.
-If the shim does not boot, you need to perform BadRecovery.
+Please note that SH1mmer has been patched for later devices, even if they have leaked shims.
+If the shim does not boot on your target device, you may need to use BadRecovery instead.
 {: .notice--danger}
 
 ## Section I - Download a Raw Shim
@@ -18,9 +18,9 @@ You need to download a raw RMA (Return Merchandise Authorization) shim for your
 
 - https://dl.darkn.bio/
 
-## Section II - Add the SH1MMER payload (BeautifulWorld)
+## Section II - Add the SH1mmer payload (BeautifulWorld)
 
-Visit the [SH1MMER Web Builder](https://sh1mmer.me/builder.html) and upload your raw shim. Wait a couple of minutes for it to build, then download the result.
+Visit the [SH1mmer Web Builder](https://sh1mmer.me/builder.html) and upload your raw shim. Wait a couple of minutes for it to build, then download the result.
 
 ## Section III - Flash the Shim
 
@@ -47,9 +47,9 @@ Download [Rufus](https://rufus.ie/) and run the executable. Select the .bin file
 
 Download [Etcher](https://www.balena.io/etcher) and run the excutable. Select the .bin file and your USB drive. Click on flash and follow the prompts.
 
-## Section IV - Boot SH1MMER
+## Section IV - Boot SH1mmer
 
-Boot your Chromebook and press and hold `Esc+Refresh+Power` for one second. Then, press `Ctrl+D`. At the next screen, press `Refresh+Power`. Now, plug in your USB drive and press `Esc+Refresh+Power` again. After a short loading screen, the SH1MMER menu should load.
+Boot your Chromebook and press and hold `Esc+Refresh+Power` for one second. Then, press `Ctrl+D`. At the next screen, press `Refresh+Power`. Now, plug in your USB drive and press `Esc+Refresh+Power` again. After a short loading screen, the SH1mmer menu should load.
 
 ## Section V - Unenroll
 

_pages/en_US/troubleshooting.txt

@@ -12,60 +12,57 @@ Seriously, how did you run into an issue *here*? Make an issue on the GitHub rep
 
 ### Help! I don't have a personal computer with admin permissions and the Chromebook Recovery Utility extension is blocked!
 
-Either get a friend to help you or else you're out of luck. Sorry, skid.
+Either get a friend to help you or else you're SOL.
 
 ### I don't have a USB drive, can you send one to me?
 
-Go out and buy one. While you're at it, touch some grass.
+No.
 
 ### My USB drive is less than 8gb. Will it still work?
 
-Yes. Use SH1MMER legacy instead.
+Yes. Use SH1mmer legacy instead.
 
 ### Recovery outputs something about the drive being outdated
 
-This means that, at some point, you've updated to v112 or higher. Use BadRecovery if under 125.
+This means that, at some point, you've updated to v112 or higher. Use BadRecovery if your version is under v125.
 
 ## Root Escalation (>v101)
 
-### No red prompt appears after running the root exploit
+### No red prompt appears after running the root exploit!
 
-Womp Womp. Recover again. Try again. Do better next time.
+You're SOL. Recover again and try again.
 
-### `set_cellular_ppp` outputs "No Cellular Service Exists"
+### `set_cellular_ppp` outputs "No Cellular Service Exists"!
 
 Either you're on a version where the `set_cellular_ppp` bug is patched (v101 or higher) or something else got messed up. Try downgrading again.
 
 ## Root Escalation (v81 - Kiosk)
 
-### I can't find my USB drive to load CHRWN from
+### I can't find my USB drive to load CHRWN from!
 
-Reboot. Try again.
+Reboot and try again. If it still doesn't work, you're (drumroll please...) SOL!
 
 ## Sh1mmer
 
-### "This USB drive does not contain ChromeOS" upon trying to boot the shim
+### "This USB drive does not contain ChromeOS" appears upon trying to boot the shim!
 
-Either you've upgraded past v112 (at which point sh1mmer is patched) or you downloaded the shim for the wrong board.
+Either you've upgraded past v112 (at which point SH1mmer is patched) or you downloaded the shim for the wrong board.
 
+### When I try to boot SH1mmer, it says I'm using a unoffical image!
 
-### When I do SH1MMER, it says im using a unoffical image.
-
-HOW. HOW DO YOU CONFUSE A RECOVERY IMAGE WITH A SHIM???? WHY..
-
-..speaking of which, you should've read the instructions for SH1MMER.
+You used a recovery image instead of a shim. Honestly, I'm not even going to tell you that you're SOL this time.
 
 ## LtBEEF
 
-### The script isn't running on any page.
+### The script isn't running on any page!
 
 Either the site that LtBEEF is being loaded from is blocked, in which case you're on a version where LtBEEF is patched, or you're on the wrong page. Keep in mind that LtBEEF needs to be run on:
 
 `https://chrome.google.com/webstorex`.
 
 ## Murkmod
 
-### Installing/Updating error: Read-only Filesystem
+### While Installing/Updating: Read-only Filesystem
 
 Try recovering, unenrolling, then fakemurking and murkmodding again.
 

_pages/en_US/what-now.txt

@@ -80,12 +80,15 @@ If you installed AuroraStore, you can search up "LibreTorrent". LibreTorrent is
 Using Crouton, you can swap over to a full Linux desktop running XFCE. Within it, you can install firefox (`sudo apt install firefox-esr`) and then set the proxy settings to point towards wssocks (`127.0.0.1` on port `1080`).
 
 ## Install Windows/MacOS/Linux with FULL UEFI firmware
+
 Disable WP using any of the methods for your board, then flash FULL ROM firmware using the MrChromebox script.
 
-Now, simply flash the iso of your OS on to your usb and plug it in. Simple right?
-Only issue is Windows needs drivers. LOTTTS of them. Go [here](https://coolstar.org/chromebook/windows-install.html) for more info. If you have money to spare,
-simply buy them from CoolStar.
+Now, simply flash the ISO of your OS on to your usb and plug it in.
+
+### For you Windows chumps:
+
+Windows needs drivers. Lots of them! Beware that this takes up a lot of space, too, so it might not be best for your 20gb EMMC Chromebook. If you still insist on running Windows for some horrible reason, go [here](https://coolstar.org/chromebook/windows-install.html) for more info. If you have money to spare, simply buy them from CoolStar.
 
-..or you can sail the high seas. good luck trying to find them lmao.
+...or you can sail the high seas. Good luck finding them.
 
-Please note that MacOS booting is only possible on 10th gen and below Intel Processors, which are not Celerons, Pentiums or Atoms. Consult the [OpenCore guide](https://dortania.github.io/OpenCore-Install-Guide/) for more.
+Please note that running MacOS is only possible on 10th gen and below Intel Processors, which are not Celerons, Pentiums or Atoms. Consult the [OpenCore guide](https://dortania.github.io/OpenCore-Install-Guide/) for more (but why would you even want to run MacOS? blink twice if you're doing this against your will).