SafeB9SInstaller sometimes doesn't properly display the top screen (or also bottom screen sometimes, but that is not covered by this PR). If the bottom screen is still displaying then we can safely just tell people to enter the key combo blindly.
* Update a9lh-to-b9s.md
rewrote overwriting files note
* Update restoring-updating-cfw.md
changed wording to "If any of the files exist, overwrite them with the new files" from ",replacing any existing files"
* changed wording about replacing files
changed wording to "If any of the files exist, overwrite them with the new files" from "overwrite any existing files"
* changed wording about replacing files
changed wording to "If any of the files exist, overwrite them with the new files" from "overwrite any existing files"
* changed wording about replacing files
changed wording to "If any of the files exist, overwrite them with the new files" from "overwrite any existing files"
* changed wording about replacing files
changed wording to "If any of the files exist, overwrite them with the new files" from "overwrite any existing files"
* changed wording about replacing files
changed wording to "If any of the files exist, overwrite them with the new files" from "overwrite any existing files"
* changed wording about replacing files
changed wording to "If any of the files exist, overwrite them with the new files" from "overwrite any existing files"
* Update installing-boot9strap-(super-skaterhax).md
fixed punctuation
* Update restoring-updating-cfw.md
fixed punctuation
- Particularly on-console steps don't really have any reason to be
different between mobile and desktop versions.
- Fix some instances of 3DS to console as written on other pages while
at it
- Minor changes to reflect that not *everything* everything is nuked
(because some paranoid people keep asking)
The version of Python from the Microsoft Store does not work with MSET9,
in part because this version doesn't include the "py" launcher, which is
what MSET9-Windows.bat wants. I don't know if it does actually work if
mset9.py is used directly though, but until then, the python.org
installers should be recommended.
They're the same for all occurrances of this include, so why not?
It also fixes an issue in Crowdin where it is converting this include
into a codeblock.
It also inadvertantly fixes a typo where `1.` was defined twice.
Things that happen in this shameless squash:
- Removed 404 page
- It doesn't work in VitePress and making it work in VitePress needs
some invasive hack in the theme that I'm not willing to do
- The default is more than enough, though
- Moved consoleVersionSelect include to another directory
- This avoids being uploaded to Crowdin for translation
- Inline all SafeB9SInstaller includes
- Not only do parameterized includes not work, but if/else statements
don't work at all
- The sysupdate include parameter hasn't been used since MSET9, so it
actually works just fine without any parameters. Hooray(?)
- Move mset9-chorus to an include, that logic doesn't work in VitePress
- Removed Get Started button from homepage, it breaks translations
- Tables in get-started are now shown by default; it seems VitePress really does
not want us to use inline script. So we cannot enable it upon
realizing that the browser is JS capable
- Include parameters are now in frontmatter to allow translation
- Hacked in a bunch of CSS values kanged from the old theme to make it
look not stupid
- Drop headers down one level to make table of contents work
