treewide: use 1. numbering for all ordered lists

Following specifications at [0] the formatting for lists "have no
effect on the HTML output Markdown produces".

This means we can consolidate all ordered lists to `1.`, which makes it
easier for the end user to add and remove steps and retain the
numbering.

It should be noted some Markdown implementations may use the first
number as a starting number for ordered lists, so it's best to start
with `1.`.

[0]: https://daringfireball.net/projects/markdown/syntax#list

docs/extras/adding_udev.md

@@ -20,22 +20,22 @@ The following instructions are not for beginners. Only do this if you understand
 To start, we will create a new group and add ourselves to it. The group the Nintendo Switch device will be owned by on Linux will be set to this group.
 
 1. Open a terminal.
-2. Enter the following command: `sudo groupadd nintendo_switch`.
-3. Enter your password when prompted.
-4. Enter the following command: `sudo usermod -a -G nintendo_switch $USER`. Make sure that the `G` is capitalized!
-5. Close the terminal.
+1. Enter the following command: `sudo groupadd nintendo_switch`.
+1. Enter your password when prompted.
+1. Enter the following command: `sudo usermod -a -G nintendo_switch $USER`. Make sure that the `G` is capitalized!
+1. Close the terminal.
 
 #### **Adding a udev rule**
 
 Next we're gonna add a new `udev` rule. `udev` is a device manager for the linux kernel. The rule we're gonna specify is that if the Switch is connected in `RCM`, the group the Switch belongs to will be the group we made in the previous section.
 
 1. Open a terminal.
-2. Change to the root user with the following command: `sudo -i`. Enter your password when prompted.
-3. Enter the following command: `mkdir -p /etc/udev/rules.d`.
-4. Enter the following command: `echo 'SUBSYSTEMS=="usb", ATTRS{manufacturer}=="NVIDIA Corp.", ATTRS{product}=="APX", GROUP="nintendo_switch"' > /etc/udev/rules.d/10-switch.rules`.
-5. Enter the following command: `udevadm control --reload`.
-6. Enter the following command: `udevadm trigger`.
-7. Logout and log back in.
+1. Change to the root user with the following command: `sudo -i`. Enter your password when prompted.
+1. Enter the following command: `mkdir -p /etc/udev/rules.d`.
+1. Enter the following command: `echo 'SUBSYSTEMS=="usb", ATTRS{manufacturer}=="NVIDIA Corp.", ATTRS{product}=="APX", GROUP="nintendo_switch"' > /etc/udev/rules.d/10-switch.rules`.
+1. Enter the following command: `udevadm control --reload`.
+1. Enter the following command: `udevadm trigger`.
+1. Logout and log back in.
 
 You should now be able to run the payload sender without having to use `sudo`.
 
@@ -49,7 +49,7 @@ You may just follow the instructions at <a href="https://github.com/pheki/nx-ude
 
 1. Download <a href="https://github.com/pheki/nx-udev/releases/latest/download/nx-udev_latest_all.deb
 " target="_blank">nx-udev_latest_all.deb</a>.
-2. Open a terminal in the same directory as your download.
-3. Run `sudo dpkg -i nx-udev_latest_all.deb` to install the package
+1. Open a terminal in the same directory as your download.
+1. Run `sudo dpkg -i nx-udev_latest_all.deb` to install the package
 
 You should now be able to run the payload injector and homebrew with USB communication without having to use `sudo`.

docs/extras/alternate_bootsetups.md

@@ -16,11 +16,11 @@ If you need to troubleshoot something, or need to try a different boot setup, re
 #### **Instructions:**
 
 1. Insert your Switch's microSD card into your PC.
-2. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD card.
-3. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your microSD card.
-4. Copy `fusee.bin` to the `sd:/bootloader/payloads` folder on your microSD card.
-5. The setup is complete, you can inject the Hekate payload (Unpatched Switch users) or place the Hekate payload on the root of your microSD card and rename it to `payload.bin` (Modchipped Switch users).
-6. Navigate to and select `Payloads` > `fusee.bin`.
+1. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD card.
+1. Copy the `bootloader` folder from the Hekate `.zip` file to the root of your microSD card.
+1. Copy `fusee.bin` to the `sd:/bootloader/payloads` folder on your microSD card.
+1. The setup is complete, you can inject the Hekate payload (Unpatched Switch users) or place the Hekate payload on the root of your microSD card and rename it to `payload.bin` (Modchipped Switch users).
+1. Navigate to and select `Payloads` > `fusee.bin`.
     - Note: `fusee` uses a set boot order that is not as easily configurable as Hekate. Its boot order is `emuMMC` > `sysCFW` > `stock`.
     If an emuMMC isn't present, it will boot into sysCFW for example. Make sure you have a method of blocking Nintendo's servers set up (such as [DNS-MITM](../extras/blocking_nintendo.md/#instructions-ams-dns-redirection)) if you do use `fusee` and have an `emuMMC`.
 
@@ -37,7 +37,7 @@ This method will *not* work for Modchipped Switch users.
 #### **Instructions:**
 
 1. Insert your Switch's microSD card into your PC.
-2. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD card.
-3. The setup is complete, you can inject the `fusee.bin` payload.
+1. Copy *the contents of* the Atmosphere `.zip` file to the root of your microSD card.
+1. The setup is complete, you can inject the `fusee.bin` payload.
     - Note: `fusee` uses a set boot order that is not as easily configurable as Hekate. Its boot order is `emuMMC` > `sysCFW` > `stock`.
     If an emuMMC isn't present, it will boot into sysCFW for example. Make sure you have a method of blocking Nintendo's servers set up (such as [DNS-MITM](../extras/blocking_nintendo.md/#instructions-ams-dns-redirection)) if you do use `fusee` and have an `emuMMC`.

docs/extras/autorcm.md

@@ -38,7 +38,7 @@ AutoRCM can be used for good as well:
 If, despite all of the information above, you still wish to enable (or disable) AutoRCM, and understand the risks, do the following:
 
 1. Boot into Hekate
-2. Go to `Tools`
-3. At the bottom of the page, tap `Arch Bit • AutoRCM • Touch • Pkg1/2`
-4. Then tap `AutoRCM`. It will show a little `ON` next to the option once you have done this.
+1. Go to `Tools`
+1. At the bottom of the page, tap `Arch Bit • AutoRCM • Touch • Pkg1/2`
+1. Then tap `AutoRCM`. It will show a little `ON` next to the option once you have done this.
     - If you wish to disable it instead, follow these same steps and ensure the `AutoRCM` option is set to `OFF`.

docs/extras/blocking_nintendo.md

@@ -13,13 +13,13 @@ You can configure Atmosphère to automatically redirect any requests directed to
 
 1. Enter RCM and inject the Hekate payload.
     - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your SD.
-2. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
-3. Enter the `atmosphere` folder.
-4. If it doesn't exist already, create a folder named `hosts` in the `atmosphere` folder.
+1. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
+1. Enter the `atmosphere` folder.
+1. If it doesn't exist already, create a folder named `hosts` in the `atmosphere` folder.
     - You should end up with the `sd:/atmosphere/hosts` directory.
-5. Copy the `emummc.txt` file into the hosts folder.
+1. Copy the `emummc.txt` file into the hosts folder.
     - If you want to apply the DNS redirection to sysmmc instead of emummc, rename the file to `sysmmc.txt`
-6. Eject the `UMS` device safely from within your computer's operating system and boot into CFW.
+1. Eject the `UMS` device safely from within your computer's operating system and boot into CFW.
 
 !!! note "Verify functionality"
     You can verify the functionality of the DNS redirection by booting into emummc (or sysmmc if you applied the config to sys), and powering off after.
@@ -42,33 +42,33 @@ Enter the console's System Settings, and then proceed to the Internet tab. From
     Not all WiFi networks require a password to connect. If your network does not use one, you can use the `Manual Setup` option, located at the very bottom of the `Internet Settings` screen below all other WiFi networks.
 
 1. Select your WiFi network from the list of networks.
-2. Enter an **incorrect** password that is 8 characters long and press `OK`.
-3. After a few moments of attempting to connect, the console will display a connection error.
-4. Press `OK` to close the error message.
-5. Press `Close` when it offers to display more details about the error.
-6. When asked if you want to re-enter the password, pick `View Settings`.
-7. Change `DNS Settings` to `Manual`.
-8. Pick the server that is the closest to your location out of the below chart and enter its `Primary` and `Secondary` DNS into your connection settings.
-9. Enter the correct password for your WiFi connection.
-10. Save the settings and test the connection.
+1. Enter an **incorrect** password that is 8 characters long and press `OK`.
+1. After a few moments of attempting to connect, the console will display a connection error.
+1. Press `OK` to close the error message.
+1. Press `Close` when it offers to display more details about the error.
+1. When asked if you want to re-enter the password, pick `View Settings`.
+1. Change `DNS Settings` to `Manual`.
+1. Pick the server that is the closest to your location out of the below chart and enter its `Primary` and `Secondary` DNS into your connection settings.
+1. Enter the correct password for your WiFi connection.
+1. Save the settings and test the connection.
 
     -----
 
 #### **Editing an existing WiFi connection**
 1. Select your existing WiFi network from the list of networks.
-2. Select `Change Settings`.
-3. Pick the server that is the closest to your location out of the below chart and enter its Primary and Secondary DNS into your connection settings.
-4. Save the settings and test the connection.
+1. Select `Change Settings`.
+1. Pick the server that is the closest to your location out of the below chart and enter its Primary and Secondary DNS into your connection settings.
+1. Save the settings and test the connection.
 
     -----
 
 #### **Using homebrew to set 90DNS on all existing WiFi networks**
 1. Download [switch-90dns-setter](https://github.com/suchmememanyskill/switch-90dns-setter/releases) and put it in the `/switch` folder.
-2. Launch CFW and open the homebrew menu.
-3. Launch `90DNS Setter`.
-4. Press X to apply 90DNS to all WiFi networks.
-5. Press Y to reboot the Switch.
-6. Check in system settings if networks have a custom DNS applied.
+1. Launch CFW and open the homebrew menu.
+1. Launch `90DNS Setter`.
+1. Press X to apply 90DNS to all WiFi networks.
+1. Press Y to reboot the Switch.
+1. Check in system settings if networks have a custom DNS applied.
 
 
 | Location                              | Primary DNS         | Secondary DNS       |
@@ -88,13 +88,13 @@ Enter the console's System Settings, and then proceed to the Internet tab. From
 
 #### **Testing via the eShop (Stock)**
 1. Open the eShop. Wait until it either opens or displays an error.
-2. If it displays "Unable to display page.", you seem to have blocked Nintendo's servers.
+1. If it displays "Unable to display page.", you seem to have blocked Nintendo's servers.
 
 #### **Testing via a homebrew app (CFW)**
 1. Download the latest release of the [90DNS Tester](https://github.com/meganukebmp/Switch_90DNS_tester/releases)
-2. Place the `Switch_90DNS_tester.nro` in the `switch` folder on your SD.
-3. Enter the homebrew menu and run the 90DNS Tester.
-4. After the test finished it should look similar to the below picture, with every `nintendo` domain being blocked.
+1. Place the `Switch_90DNS_tester.nro` in the `switch` folder on your SD.
+1. Enter the homebrew menu and run the 90DNS Tester.
+1. After the test finished it should look similar to the below picture, with every `nintendo` domain being blocked.
 
 !!! tip ""
     ![tester example](../extras/img/90dns_tester_switch.jpg)

docs/extras/nandrestore.md

@@ -25,11 +25,11 @@ Before we start, check if you have a tree of folders called `backup/[8 Character
 
 1. Enter RCM and inject the Hekate payload.
     - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your SD.
-2. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
-3. Copy your `rawnand.bin` (combined or in 15 or 30 parts), `BOOT0`, and `BOOT1` to the `backup/[8 Character NAND id]/restore` folder on the microSD card.
-4. Eject the `UMS` device safely from within your computer's operating system.
-5. Navigate to `Tools` > `Restore eMMC`. Select `Restore eMMC BOOT0 & BOOT1`. Wait for this process to complete.
-6. In that same menu, select `eMMC RAW GPP` and wait for the process to complete.
+1. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
+1. Copy your `rawnand.bin` (combined or in 15 or 30 parts), `BOOT0`, and `BOOT1` to the `backup/[8 Character NAND id]/restore` folder on the microSD card.
+1. Eject the `UMS` device safely from within your computer's operating system.
+1. Navigate to `Tools` > `Restore eMMC`. Select `Restore eMMC BOOT0 & BOOT1`. Wait for this process to complete.
+1. In that same menu, select `eMMC RAW GPP` and wait for the process to complete.
     - This will generally take a long time to complete, the time it takes depends on your microSD card's specifications. (10-15 minutes is expected.)
 
 !!! danger "If you're downgrading using your NAND backup"

docs/extras/showing_file_extensions.md

@@ -5,14 +5,14 @@ By default, Microsoft Windows 10 and 11 do not show file extensions for known fi
 ### **Instructions for Windows 10:**
 
 1. Open a new File Explorer window.
-2. Switch to the View tab/ribbon.
-3. On this tab, if the `File name extensions` checkbox is not ticked, put a check/tick mark in it by clicking it.
+1. Switch to the View tab/ribbon.
+1. On this tab, if the `File name extensions` checkbox is not ticked, put a check/tick mark in it by clicking it.
 
 ### **Instructions for Windows 11:**
 
 1. Open a new File Explorer window.
-2. Click the `View` hamburger menu/dropdown menu.
-3. Go to `Show` at the bottom and ensure that `File name extensions` is ticked.
+1. Click the `View` hamburger menu/dropdown menu.
+1. Go to `Show` at the bottom and ensure that `File name extensions` is ticked.
 
 !!! tip ""
     ![Visual for the above instructions](img/file_extensions.png)

docs/extras/transfer_sd.md

@@ -10,22 +10,22 @@ You should first check whether you have a file or partition based emuMMC:
 
 1. Enter RCM and inject the Hekate payload.
     - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your microSD card.
-2.  Tap on the `emuMMC` button.
-3.  Under `emuMMC Info & Selection`, check the text next to `Type`.
+1.  Tap on the `emuMMC` button.
+1.  Under `emuMMC Info & Selection`, check the text next to `Type`.
     - If you have one it should be either `SD Raw Partition` or `SD File`.
 
 -----
 ### **If you are using a file based emuMMC or are using no emuMMC at all:**
 
 1. Enter RCM and inject the Hekate payload.
     - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your microSD card.
-2. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
-2. Copy the contents of your microSD card somewhere to your PC.
-4. Access your new microSD card via a microSD card reader or similar.
-5. Format your new microSD card to FAT32 if it isn’t already.
+1. Navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
+1. Copy the contents of your microSD card somewhere to your PC.
+1. Access your new microSD card via a microSD card reader or similar.
+1. Format your new microSD card to FAT32 if it isn’t already.
     - To do this, use [this guide](https://wiki.hacks.guide/wiki/Formatting_an_SD_card).
-6. Copy the files from your PC or directly from your old microSD card to your new microSD card.
-7. Eject the `UMS` device safely from within your computer's operating system.
+1. Copy the files from your PC or directly from your old microSD card to your new microSD card.
+1. Eject the `UMS` device safely from within your computer's operating system.
 
 -----
 ### **If you are using a partition based emuMMC:**
@@ -35,20 +35,20 @@ You should first check whether you have a file or partition based emuMMC:
 
 1. Enter RCM and inject the Hekate payload.
     - If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to `payload.bin` on the root of your SD.
-2.  In the main menu, tap on `Tools`, then `Backup eMMC` and set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
-3.  Backup both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
-4.  Once both are done, go back to the main menu, navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
-5.  If Windows asks you to format a drive, discard it and open the accessible drive containing the contents of your microSD card.
-6.  Copy the contents of your old microSD card somewhere to your PC.
-7.  Follow the `Preparing Hekate` section at the bottom of [this page](../user_guide/rcm/sending_payload.md) (Unpatched Switch users only) to prepare your new SD card with Hekate's files.
+1.  In the main menu, tap on `Tools`, then `Backup eMMC` and set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
+1.  Backup both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
+1.  Once both are done, go back to the main menu, navigate to `Tools` > `USB Tools` > `SD Card` and plug your Switch into your PC via USB.
+1.  If Windows asks you to format a drive, discard it and open the accessible drive containing the contents of your microSD card.
+1.  Copy the contents of your old microSD card somewhere to your PC.
+1.  Follow the `Preparing Hekate` section at the bottom of [this page](../user_guide/rcm/sending_payload.md) (Unpatched Switch users only) to prepare your new SD card with Hekate's files.
     - If you have a modchipped Switch, follow [this page](../user_guide/modchip/preparing_hekate.md) instead.
-8.  Follow only steps 1-3 on [this page](../user_guide/all/partitioning_sd.md) to partition the new microSD card for an emuMMC setup.
-8.  After it’s done, boot into Hekate and navigate to `Tools` > `USB Tools` > `SD Card`, then plug your Switch into your PC via USB.
-9.  Copy the backup you made of your old microSD card on your PC to your new microSD card.
-10. Navigate to `/backup/<some characters>/emummc` on your microSD card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to `/backup/<some characters>/restore/emummc`.
-11. Eject the `UMS` device safely from within your computer's operating system.
-12. Tap on `Tools`, `Restore eMMC`, set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
-13. Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
+1.  Follow only steps 1-3 on [this page](../user_guide/all/partitioning_sd.md) to partition the new microSD card for an emuMMC setup.
+1.  After it’s done, boot into Hekate and navigate to `Tools` > `USB Tools` > `SD Card`, then plug your Switch into your PC via USB.
+1.  Copy the backup you made of your old microSD card on your PC to your new microSD card.
+1. Navigate to `/backup/<some characters>/emummc` on your microSD card and move `BOOT0`, `BOOT1` and the `rawnand.bin.xx` files to `/backup/<some characters>/restore/emummc`.
+1. Eject the `UMS` device safely from within your computer's operating system.
+1. Tap on `Tools`, `Restore eMMC`, set `SD emuMMC Raw Partition` at the bottom of your screen to `ON`.
+1. Restore the backup by tapping on both `SD emuMMC BOOT0 & BOOT1` and `SD emuMMC RAW GPP` (Note: `SD emuMMC RAW GPP` may take a while).
     - It is very important that for both of these the `SD emuMMC Raw Partition` option is enabled, otherwise you will be altering your sysMMC
       which is not what you want.
-14. Your emuMMC is now restored on the new microSD card and you should be able to launch it from `Launch` -> `Atmosphere FSS0 emuMMC` in Hekate.
+1. Your emuMMC is now restored on the new microSD card and you should be able to launch it from `Launch` -> `Atmosphere FSS0 emuMMC` in Hekate.