Various changes (#28)

* Small adjustments and others

Small adjustments:
- Corrects capitalization of `Acekard` and `SD card`
- Corrects to American English
Also adds detail about nds-bootstrap screenshots, and redirects nds-bootstrap compatibility question to its FAQ, for consistency's sake.

* Compatibility and nds-bootstrap vs flashcard changes

Compatibility question changes:
- Merges troubleshooting and "Why do I get a white screen" because of redundancy
- Removes mention of changing sound quality, as far as I know this has never been an issue anywhere
- Adds mention of Async card read (using Async for the sake of consistency, unless that's to be changed as well)
- Links to GitHub issues page
-Small detail change on adding to the compatibility list
nds-bootstrap vs flashcard changes:
- Corrects `cartridges` to `Game Cards`
- Adds detail about screenshots and RAM editing

* Add detail about TWiLight Menu++ cheats menu

Also removes a period from a bullet

* Small changes

- Corrects capitalization of `Game Card`
- Corrects `3DS/2DS` to just `3DS`

* Add screenshot/frame advance details

Also
- Adds details on faster/fastest scroll in nds-bootstrap RAM viewer
- Adds detail on changing the in-game menu button combination

* Add detail about custom text color palettes

I think this is also worth adding, even though it's stared under the restrictions

* Decapitalize "custom firmware"

* Add detail about 3D/2D elements

Also corrects capitalization of `GBAtemp`

* Add screenshot controls

Also adds details about screenshots.tar

* Add specific spelling for 3DS as a family of systems

* Update controls.md

* Add Up/Down for cycling screenshot VRAM bank

* Correct frame step button

* Add pressing B to return to the in-game menu from Screenshot

Co-authored-by: RocketRobz <bobesh8@gmail.com>

CONTRIBUTING.md

@@ -61,3 +61,4 @@ Decimal:
 - "Flashcard" should be used for Slot-1 (DS) flashcards
 - "Cartridge" should be be used for standard GBA cartridges
 - "Game Card" should be capitalized
+- "3DS" should be used when referring to the family of systems that includes the 2DS

pages/_en-US/nds-bootstrap/faq.md

@@ -9,34 +9,29 @@ description: FAQ & Troubleshooting for nds-bootstrap
 
 #### Why do I get a white screen when trying to load a game from SD card?
 - First, check the [the nds-bootstrap compatibility list](https://docs.google.com/spreadsheets/d/1LRTkXOUXraTMjg1eedz_f7b5jiuyMv2x6e_jY_nyHSc/htmlview#gid=0) and make sure your game is compatible
-- Try with all cheats disabled for that game as some cheats are not compatible with nds-bootstrap at the moment, you can use <kbd class="l">L</kbd> to disable all cheats for a game
+- Try with all cheats disabled for that game as some cheats are not compatible with nds-bootstrap at the moment, you can use <kbd class="l">L</kbd> in the TWiLight Menu++ cheats menu to disable all cheats for a game
 - If it worked before, delete the `fatTable` and `patchOffsetCache` folders in `sd:/_nds/nds-bootstrap/`
+- Run the game with different settings, including changing the ARM9 CPU Speed, Async card read, DS/DSi Mode, sound quality, Card read DMA, etc
+- It's probably not that big of an issue; ask in the [Discord server](https://discord.gg/yD3spjv)
+If the server says it's an nds-bootstrap issue, check if the game hasn't been reported already on [GitHub](https://github.com/DS-Homebrew/nds-bootstrap/issues). Check the closed issues too in case there has already been an issue closed in preference a different one. If it doesn't have any GitHub issue attached to it, go ahead and make a new one
 
-#### nds-bootstrap troubleshooting
+If no solution has been found at this point, make sure you add it to the [compatibility list](https://wiki.ds-homebrew.com/nds-bootstrap/testing) on Google Sheets.
-If you get issues with using the latest version of nds-bootstrap, here's how you can troubleshoot it.
-
-1. Run the game with different settings, including changing the ARM9 CPU Speed, DS/DSi Mode, sound quality, Card Read DMA, etc
-2. Delete the `fatTable` and `patchOffsetCache` folders in `sd:/_nds/nds-bootstrap/`
-3. It's probably not that big of an issue; ask in the [Discord server](https://discord.gg/yD3spjv)
-
-If the server says it's an nds-bootstrap issue, check if the game hasn't been reported already on GitHub. Check the closed issues too in case there has already been an issue closed in preference a different one. If it doesn't have any GitHub issue attached to it, go ahead and make a new one.
-
-Also, make sure you add it to the [compatibility list](https://wiki.ds-homebrew.com/nds-bootstrap/testing) on Google Sheets.
 
 #### Why are there issues with ROM loading, even though they're run natively?
 nds-bootstrap patches the ROM functions to run from an SD card, as the ROMs are hardcoded to read from Slot-1.
 There are also timing issues and AP measures (which most are already removed), both of which will cause the ROMs to not work properly.
 
 #### Why use nds-bootstrap over a regular flashcard?
-- Certain compatible ROMs are loaded into RAM, allowing for load times to be faster than even normal cartridges
+- Certain compatible ROMs are loaded into RAM, allowing for load times to be faster than even normal Game Cards
 - You can expand the VRAM memory bus to 32-bit
 - Utilize the DSi's additional CPU speed, allowing for better performance in some games
 - Enhance your audio with 48 kHz
 - Use DSi mode, allowing for DSi features
-- Using certain cartridges, you are able to use IR in your application
+- Using certain Game Cards, you are able to use IR in your application
 - nds-bootstrap is open source, meaning developers can always update it to fix bugs and other things, even if the project gets discontinued
 - The DS Memory Expansion Pak is emulated, meaning games that require that accessory will work
 - Swap top and bottom screens in compatible games for more comfortable gameplay, or on systems with a broken or removed screen
+- Take screenshots and edit values in the RAM using the in-game menu
 
 #### Donor ROMs
 Most SDK5 games can be selected as a Donor ROM (which can be done via TWiLight Menu++). The Donor ROM's ARM7 binary is copied by nds-bootstrap and replaces the ARM7 binary for the game that it is trying to run. This allows certain and SDK5 games to boot and save.

pages/_en-US/twilightmenu/controls.md

@@ -41,9 +41,16 @@ These do not apply to DSiWare.
 - <kbd class="l">L</kbd> + <kbd class="r">R</kbd> + <kbd>Down</kbd> + <kbd class="face">A</kbd> for 3 seconds: Dump RAM to `sd:/_nds/nds-bootstrap`, as `ramDump.bin`
 - <kbd class="l">L</kbd> + <kbd class="r">R</kbd> + <kbd>Down</kbd> + <kbd class="face">B</kbd> for 2 seconds: Return to TWiLight Menu++
 - <kbd class="l">L</kbd> + <kbd>Down</kbd> + <kbd>SELECT</kbd>: Open the in-game menu
+   - <kbd class="r">R</kbd>: Advance by one frame
+   - Screenshot
+      - <kbd>Up</kbd>/<kbd>Down</kbd>/<kbd>Left</kbd>/<kbd>Right</kbd>: Change VRAM bank
+      - <kbd class="face">A</kbd>: Save screenshot
+      - <kbd class="face">B</kbd>: Return to in-game menu
    - RAM Viewer
       - <kbd>Up</kbd>/<kbd>Down</kbd>: Scroll
       - <kbd>Left</kbd>/<kbd>Right</kbd>: Fast scroll
+      - <kbd class="r">R</kbd> + <kbd>Down</kbd>/<kbd>Up</kbd>: Faster scroll
+      - <kbd class="r">R</kbd> + <kbd>Left</kbd>/<kbd>Right</kbd>: Fastest scroll
       - <kbd class="face">A</kbd>: Enter RAM Editor
       - <kbd class="face">B</kbd>: Return to in-game menu
       - <kbd class="face">Y</kbd>: Specify an address to jump to
@@ -61,9 +68,11 @@ These do not apply to DSiWare.
         - <kbd>Up</kbd>/<kbd>Down</kbd>: Increase/Decrease selected value
         - <kbd>Left</kbd>/<kbd>Right</kbd>: Select a value
         - <kbd class="face">A</kbd>/<kbd class="face">B</kbd>: Return to RAM Viewer/Editor at specified address
-- The in-game menu is not accessible in DSi Enhanced/Exclusive games running in DSi Mode, so attempting to use the button combo in those games will instead exit the game
+- The in-game menu is not accessible in DSi-Enhanced/Exclusive games running in DSi Mode, so attempting to use the button combo in those games will do nothing
 - Only the screen swap button combo will work in B4DS mode, the others will not work
 - Returning to TWiLight Menu++ may not work on some O3DS models
+- The button combination for opening the in-game menu can be changed in the TWiLight Menu++ settings
+- Screenshots are saved to `sd:/_nds/nds-bootstrap/screenshots.tar`. This file can be opened using an archive viewer such as [7-Zip](https://www.7-zip.org/)
 
 #### Boot shortcuts
 These should be pressed on the TWiLight Menu++ splash screen / right after the Nintendo DSi splash screen.

pages/_en-US/twilightmenu/custom-unlaunch-backgrounds.md

@@ -10,7 +10,7 @@ description: How to make custom Unlaunch backgrounds and install them using TWiL
 You can find premade Unlaunch backgrounds on the [TWiLight Menu++ skins site](https://skins.ds-homebrew.com/unlaunch/).
 {:.alert .alert-info}
 
-Using TWiLight Menu++ you can patch the Unlaunch installer to have a custom background image. This needs to be a 256 x 192 GIF, with a few restrictions:
+Using TWiLight Menu++ you can patch the Unlaunch installer to have a custom background image and text color palette. This needs to be a 256 x 192 GIF, with a few restrictions:
 - Only the first frame will be shown, no animated backgrounds
 - The file must be less than or equal to 15,472 bytes
 - GIFs with more than 31 colors require specially made palettes to prevent breaking the text

pages/_en-US/twilightmenu/faq.md

@@ -11,7 +11,7 @@ description: FAQs and troubleshooting for TWiLight Menu++
 For more FAQs, please visit the [GBAtemp thread](https://gbatemp.net/threads/ds-i-3ds-twilight-menu-gui-for-ds-i-games-and-ds-i-menu-replacement.472200/).
 {:.alert .alert-info}
 
-#### Why does my 3DS/2DS get stuck on black screens, crash, power off, etc when launching TWiLight Menu++?
+#### Why does my 3DS get stuck on black screens, crash, power off, etc when launching TWiLight Menu++?
 TWL_FIRM might've somehow got corrupted.
 Follow this guide to fix the issue: <https://3ds.hacks.guide/troubleshooting#dsi--ds-functionality-is-broken-after-completing-the-guide>
 
@@ -21,15 +21,13 @@ Follow this guide to fix the issue: <https://3ds.hacks.guide/troubleshooting#dsi
 - If that also doesn't work, try a different SD card
 
 #### Where is the Acekard/Wood UI theme?
-The acekard (also called Wood UI) theme was removed due to its buggy behaviour and causing SD Card corruption. Please wait for a fix. Progress for the return of this theme can be found in [this PR](https://github.com/DS-Homebrew/TWiLightMenu/pull/1109).
+The Acekard (also called Wood UI) theme was removed due to its buggy behavior and causing SD card corruption. Please wait for a fix. Progress for the return of this theme can be found in [this PR](https://github.com/DS-Homebrew/TWiLightMenu/pull/1109).
 
 #### How do I fix TWiLight Menu++ restarting or giving a Guru Meditation Error when launching a game?
 Go into TWLMenu++ Settings, and disable `Update recently played list`.
 
-#### Why do I get a white screen when trying to load a game from SD card?
+#### Why do I get a white screen when trying to load a DS game from SD card?
-- First, check [the nds-bootstrap compatibility list](https://docs.google.com/spreadsheets/d/1LRTkXOUXraTMjg1eedz_f7b5jiuyMv2x6e_jY_nyHSc/htmlview#gid=0) and make sure your game is compatible
+See [Why do I get a white screen when trying to load a game from SD card?](../nds-bootstrap/faq?faq=why-do-i-get-a-white-screen-when-trying-to-load-a-game-from-sd-card) on the nds-bootstrap FAQ page.
-- Try with all cheats disabled for that game as some cheats are not compatible with nds-bootstrap at the moment, you can use <kbd class="l">L</kbd> to disable all cheats for a game
-- If it worked before, delete the `fatTable` and `patchOffsetCache` folders in `sd:/_nds/nds-bootstrap/`
 
 #### How do I use cheats?
 You need to have a cheat DB in the form of a `usrcheat.dat` file in the `sd:/_nds/TWiLightMenu/extras/` folder. The most updated cheat database is [DeadSkullzJr's](https://gbatemp.net/threads/deadskullzjrs-flashcart-cheat-databases.488711/). 
@@ -38,7 +36,7 @@ You need to have a cheat DB in the form of a `usrcheat.dat` file in the `sd:/_nd
 Alternatively, you can use [r4cce](http://hp.vector.co.jp/authors/VA013928/soft_en.html) to create your own cheat DB.
 
 #### How do I show a custom picture on the top screen of the DSi theme?
-A random `.png` image in `sd:/_nds/TWiLightMenu/dsimenu/photos/` will be shown each time the menu is loaded.
+A random `.png` image in `sd:/_nds/TWiLightMenu/dsimenu/photos/` will be shown each time the menu is loaded. If there are no applicable images, screenshots taken by nds-bootstrap will be used instead.
 
 - The images(s) must be no bigger than 208x156
 - If you have errors, it's most likely an error with the image size. Please use [tinypng](https://tinypng.com) to reduce the size
@@ -49,7 +47,7 @@ You can download homebrew games from [Universal-DB](https://db.universal-team.ne
 - On DSi you can use [GodMode9i](https://github.com/DS-Homebrew/GodMode9i/releases) to dump your DS games and DSiWare
 - On 3DS you can use [GodMode9](https://github.com/d0k3/GodMode9/releases) to dump your DS games, DSiWare, and Virtual Console titles
 
-#### Can I get the save files from my game cards onto my SD card or vice versa?
+#### Can I get the save files from my Game Cards onto my SD card or vice versa?
 Yes, you can use [GodMode9i](https://github.com/DS-Homebrew/GodMode9i/releases) on DSi and 3DS or [Checkpoint](https://github.com/FlagBrew/Checkpoint/releases) on 3DS.
 
 #### How do I change TWiLight Menu++'s language?
@@ -62,7 +60,6 @@ Yes, you can use [GodMode9i](https://github.com/DS-Homebrew/GodMode9i/releases)
 No, this is not an emulator. The menu and DS games (loaded via nds-bootstrap) are ran natively in the console's DS/DSi mode. The only consoles emulated are the past consoles, but partially for GBA (as some or all parts like graphics are ran natively).
 
 #### What systems does TWiLight Menu++ support?
-
 See [List of Systems Supported by TWiLight Menu++](../ds-index/emulators#list-of-supported-systems-by-twilight-menu).
 
 #### Why isn't touch input working on sudokuhax?

pages/_en-US/twilightmenu/installing-3ds.md

@@ -12,7 +12,7 @@ tabs:
     manual: Manual
 ---
 
-You will first need to have Custom Firmware on your 3DS, follow [3ds.hacks.guide](https://3ds.hacks.guide) to install it
+You will first need to have custom firmware on your 3DS, follow [3ds.hacks.guide](https://3ds.hacks.guide) to install it
 {:.alert .alert-info}
 
 {% capture tab-working-camera %}

pages/_en-US/twilightmenu/playing-in-widescreen.md

@@ -14,7 +14,7 @@ Requires a Nintendo 3DS or 2DS console.
 - Make sure Luma's `boot.firm` is on the SD root for this to work
 
 ### Installing
-1. Download [TWPatch](https://db.universal-team.net/assets/files/TWPatch.cia) and copy `TWPatch.cia` to your SD card ([GBATemp thread](https://gbatemp.net/threads/twpatcher-ds-i-mode-screen-filters-and-patches.542694/))
+1. Download [TWPatch](https://db.universal-team.net/assets/files/TWPatch.cia) and copy `TWPatch.cia` to your SD card ([GBAtemp thread](https://gbatemp.net/threads/twpatcher-ds-i-mode-screen-filters-and-patches.542694/))
 1. Install `TWPatch.cia` using FBI
    - You can also use Universal-Updater to install TWPatch instead of the previous two steps
 1. Return to the home menu and launch TWPatch
@@ -35,3 +35,4 @@ You're all done! Enjoy your DS games in widescreen!
 1. Do not hold <kbd>START</kbd> or <kbd>SELECT</kbd> when launching TWLMenu++, if you don't want widescreen to look glitched
 1. Not every game is widescreen compatible. [Here is a list of games with widescreen support](https://github.com/DS-Homebrew/TWiLightMenu/blob/master/7zfile/3DS%20-%20CFW%20users/Games%20supported%20with%20widescreen.txt)
 1. If you're stuck in widescreen mode in all of TWL_FIRM (including the TWLMenu++ GUI) after following this guide and launching a widescreen-compatible game, delete `TwlBg.cxi` at `sd:/luma/sysmodules/`, and [uninstall](https://wiki.ds-homebrew.com/twilightmenu/uninstalling-3ds) and [re-install](https://wiki.ds-homebrew.com/twilightmenu/installing-3ds) TWiLight Menu++, and re-follow the above guide
+1. Most widescreen patches will only adjust 3D elements for widescreen, 2D elements (such as menus) will only be stretched