docs: address review commentary

docs/components/modules/ams_mitm.md

@@ -5,28 +5,30 @@ This module provides methods to intercept services provided by other system modu
 bpc_mitm enables intercepting requests to power control services. It currently intercepts:
 + `am` system module (to intercept the Reboot/Power buttons in the overlay menu)
 + `fatal` system module (to simplify payload reboot logic significantly)
-+ Homebrew Loader (to allow homebrew to take advantage of the feature)
++ [nx-hbloader](https://github.com/switchbrew/nx-hbloader) (to allow homebrew to take advantage of the feature)
 
 ## fs_mitm
 fs_mitm enables intercepting file system operations. It can deny, delay, replace, or redirect any request made to the file system. It enables LayeredFS to function, which allows for replacement of game assets.
 
 ## hid_mitm
 hid_mitm enables intercepting requests to controller device services. It is currently disabled by default. If enabled, it intercepts:
-+ Homebrew Loader (to help homebrew not need to be recompiled due to a breaking change introduced in the past)
++ [nx-hbloader](https://github.com/switchbrew/nx-hbloader) (to help homebrew not need to be recompiled due to a breaking change introduced in the past)
+
+Note that hid_mitm is currently deprecated and might be removed entirely in the future.
 
 ## ns_mitm
 ns_mitm enables intercepting requests to application control services. It currently intercepts:
-+ Web Applets (to facilitate hbl web browser launching)
++ Web Applets (to facilitate nx-hbloader web browser launching)
 
 ## set_mitm
 set_mitm enables intercepting requests to the system settings service. It currently intercepts:
 + `ns` system module and games (to allow for overriding game locales)
-+ All settings requests
++ All firmware debug settings requests (to allow modification of system settings not directly exposed to the user)
 
 ### Firmware Version
 set_mitm intercepts the `GetFirmwareVersion` command, if the requester is `qlaunch` or `maintenance`.
 It modifies the `display_version` field of the returned system version, causing the version to display
-in settings as `#.#.# (AMS #.#.#)`. This allows users to easily verify what version of Atmosphère they are running.
+in settings as `#.#.#|AMS #.#.#|?` with `? = S` when running under system eMMC or `? = E` when running under emulated eMMC. This allows users to easily verify what version of Atmosphère and what eMMC environment they are running.
 
 ### System Settings
 set_mitm intercepts the `GetSettingsItemValueSize` and `GetSettingsItemValue` commands for all requesters.

docs/components/modules/loader.md

@@ -5,6 +5,15 @@ This module is a reimplementation of the Horizon OS's `ldr` system module, which
 Atmosphère extends this module to allow executables to be replaced or patched by files stored on the SD card. Note that a few services are required for SD card access and therefore cannot be replaced or patched in this manner.
 
 ### Exefs Replacement
+Atmosphère's reimplementation allows replacing executable files in the file system.
+
+#### Partition Replacement
+It is possible to replace the full exefs partition at once with a PFS0 file. In that case, Atmosphère will load the following file:
+```
+/atmosphere/contents/<program id>/exefs.nsp
+```
+
+#### File Replacement
 When a process is created, loader will search for several NSO filenames in the program's exefs directory.
 These filenames are, in this order:
   - rtld
@@ -26,19 +35,16 @@ Atmosphère extends this functionality by also searching for these files on the
 
 This allows the replacement of applets, system modules, or even games with homebrew versions.
 
+##### File Stubbing
 In order to prevent an NSO from being loaded even if it exists in the exefs, loader will also check if a stub file exists. If such a file exists, the NSO will not be loaded. The files should be named like `rtld.stub`, `main.stub`, etc. and may be empty.
 
-It is also possible to replace the full exefs partition at once with a PFS0 file. In that case, Atmosphère will load the following file:
-```
-/atmosphere/contents/<program id>/exefs.nsp
-```
-
 ### NSO Patching
 When an NSO is loaded, Atmosphère's reimplementation will search for IPS patch files on the SD card in the following locations.
 ```
 /atmosphere/exefs_patches/<patchset name>/<nso build id>.ips
 ```
-This organization allows patch sets affecting multiple NSOs to be distributed as a single directory. Patches will be searched for in each patch set directory. The name of each patch file should match the hexadecimal build ID of the NSO to affect, except that trailing zero bytes may be left off. Because the NSO build ID is unique for every NSO, this means patches will only apply to the files they are meant to apply to.
+
+This organization allows patch sets affecting multiple NSOs to be distributed as a single directory and also allows patches from multiple patch sets to be stacked. Patches will be searched for in each patch set directory. The name of each patch file should match the hexadecimal build ID of the NSO to affect, except that trailing zero bytes may be left off. Because the NSO build ID is unique for every NSO, this means patches will only apply to the files they are meant to apply to.
 
 Patch files are accepted in either IPS format or IPS32 format.
 
@@ -46,8 +52,10 @@ Because NSO files are compressed, patch files are not made between the original
 
 When authoring patches, [hactool](https://github.com/SciresM/hactool) can be used to find an NSO's build ID and to uncompress NSOs. Recent versions of the [ReSwitched IDA loaders](https://github.com/reswitched/loaders) can be used to load uncompressed NSOs into IDA in such a way that you can [apply patches to the input file](https://www.hex-rays.com/products/ida/support/idadoc/1618.shtml). From there, any IPS tool can be used to create the patch between the original NSO and the patched NSO. Note that if the NSO you are patching is larger than 16 MiB, you will have to use a tool that supports IPS32.
 
-### HBL Support
-Atmosphère provides first class support for [hbmenu](https://github.com/switchbrew/nx-hbmenu/releases) and [hbloader](https://github.com/switchbrew/nx-hbloader/releases).
+### Homebrew Support
+Atmosphère provides first class support for  [nx-hbloader](https://github.com/switchbrew/nx-hbloader/releases) and [nx-hbmenu](https://github.com/switchbrew/nx-hbmenu/releases).
+
+Launching of the nx-hbloader process is controlled by configurable button inputs. See [here](../../features/configurations.md) for more detailed information.
 
 In addition, loader has extensions to enable homebrew to launch web applets. This normally requires the application launching the applet to have HTML Manual content inside an installed NCA. Atmosphère's reimplementation will automatically ensure that the commands used to check this succeed, and will redirect the relevant file system to the `/atmosphere/hbl_html/` subdirectory.
 

docs/components/modules/ncm.md

@@ -1,4 +1,4 @@
 # ncm
-This module is a reimplementation of the Horizon OS's `ncm` system module, which is responsible content management.
+This module is a reimplementation of the Horizon OS's `ncm` system module, which is responsible for content management.
 
 Atmosphère's reimplementation is currently opt-in only. See [here](../../features/configurations.md) for more information.

docs/components/modules/pgl.md

@@ -1,2 +1,4 @@
 # pgl
-This module is a reimplementation of the Horizon OS's `pgl` system module, which is responsible for launching programs.
+This module is a reimplementation of the Horizon OS's `pgl` system module, which is responsible for launching programs and was introduced by firmware version `10.0.0`.
+
+Currently, Atmosphère's reimplementation doesn't backport this module's functionalities to firmware versions lower than `10.0.0`.

docs/components/modules/ro.md

@@ -1,5 +1,7 @@
 # ro
-This module is a reimplementation of the Horizon OS's `ro` system module, which is responsible for loading dynamic libraries.
+This module is a reimplementation of the Horizon OS's `ro` system module, which is responsible for loading dynamic libraries and was introduced by firmware version `3.0.0`.
+
+Atmosphère's reimplementation backports this module's functionalities to firmware versions lower than `3.0.0` where said functionalities were provided by the `ldr` system module instead.
 
 ## Extensions
 Atmosphère extends this module to allow libraries to be patched by files stored on the SD card.