Deploying to gh-pages from @ 30ff537 🚀

about/index.html

@@ -1662,7 +1662,7 @@
 
 
 
-<p><a href="https://discord.gg/C29hYvh" target="_blank"><img style="float: right;" src="../img/discord.png"></a></p>
+<p><a href="https://discord.gg/C29hYvh"><img style="float: right;" src="../img/discord.png"></a></p>
 <h1 id="about-this-guide">About this guide<a class="headerlink" href="#about-this-guide" title="Permanent link">&para;</a></h1>
 <p>This guide was written by community members of the <a href="https://discord.gg/C29hYvh">Nintendo Homebrew Discord Server</a>.</p>
 <p><a href="https://github.com/nh-server/switch-guide">You can find this guide on GitHub</a>, It is licensed under the <a href="https://github.com/nh-server/switch-guide/blob/master/LICENSE.md">ISC license</a>.</p>

extras/adding_udev/index.html

@@ -1699,10 +1699,9 @@ <h4 id="adding-a-udev-rule"><strong>Adding a udev rule</strong><a class="headerl
 <p>&nbsp;</p>
 <h3 id="option-2-installing-a-package-with-the-rules"><strong>Option 2: Installing a package with the rules</strong><a class="headerlink" href="#option-2-installing-a-package-with-the-rules" title="Permanent link">&para;</a></h3>
 <p>These rules will actually allow <em>ANY</em> user to access your Switch via USB, not only <em>your</em> user.</p>
-<p>You may just follow the instructions at <a href="https://github.com/pheki/nx-udev" target="_blank">nx-udev</a>, or if you're on Ubuntu / Debian:</p>
+<p>You may just follow the instructions at <a href="https://github.com/pheki/nx-udev">nx-udev</a>, or if you're on Ubuntu / Debian:</p>
 <ol>
-<li>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>.</li>
+<li>Download <a href="https://github.com/pheki/nx-udev/releases/latest/download/nx-udev_latest_all.deb">nx-udev_latest_all.deb</a>.</li>
 <li>Open a terminal in the same directory as your download.</li>
 <li>Run <code>sudo dpkg -i nx-udev_latest_all.deb</code> to install the package</li>
 </ol>

extras/glossary/index.html

@@ -1678,8 +1678,10 @@ <h2 id="hacking-terms">Hacking terms<a class="headerlink" href="#hacking-terms"
 <li><strong>Deja Vu</strong>: An unreleased exploit chain for the Nintendo Switch. The completely unpatched version of this chain will grant access to TrustZone, which effectively means being able to enter CFW. The TrustZone part of this exploit was patched in firmware version 5.0.0 and up, but normal homebrew access can still be gained up to firmware version 6.0.1.</li>
 <li><strong>DNS</strong>: <a href="https://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System</a>. Basically, the internet's addressbook. If you visit a website, the DNS lookup is what tells you what server the site is hosted on.</li>
 <li><strong>Dongle</strong>: Device you can plug in the USB-C of your Switch to automatically send a payload if your Switch is in RCM.</li>
-<li><strong>Encryption keys</strong>: Keys used to encrypt data from the Nintendo Switch.</li>
+<li><strong>Encryption keys</strong>: Keys used to encrypt data from the Nintendo Switch.<ul>
 <li><strong>BIS keys</strong>: Built-in Storage keys. They are used to encrypt/decrypt the NAND's contents.</li>
+</ul>
+</li>
 <li><strong><a href="https://github.com/Qyriad/fusee-launcher/blob/master/report/fusee_gelee.md">fusee-gelee</a>/<a href="https://github.com/fail0verflow/shofel2">ShofEL2</a></strong>: Two names for two different implementations of the <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-6242">same exploit</a>. This is an exploit that grants full bootROM access to the Nintendo Switch from the Tegra X1's RCM, and permitting us to run CFW. This exploit requires an external device or a tiny hardware modification. fusee-gelee is developed by an ex-ReSwitched developer, while ShofEL2 is developed by the failoverfl0w team. This guide uses fusee-gelee.</li>
 <li><strong><a href="https://github.com/SciresM/hactool">hactool</a></strong>: Software used to decrypt Nintendo Switch files like .XCI and .NSP files.</li>
 <li><strong><a href="https://github.com/CTCaer/hekate">Hekate</a></strong>: A bootloader for the Nintendo Switch. The current guide uses this in combination with essential files from Atmosphère to boot CFW.</li>

extras/nandrestore/index.html

@@ -1696,7 +1696,7 @@ <h3 id="what-you-need">What you need:<a class="headerlink" href="#what-you-need"
 <li>If you're missing any of the files above, ask for further help in the <a href="https://discord.gg/C29hYvh">Nintendo Homebrew</a> Discord server.</li>
 </ul>
 </li>
-<li>The <a href="https://github.com/CTCaer/hekate/releases/" target="_blank">Hekate</a> Payload</li>
+<li>The <a href="https://github.com/CTCaer/hekate/releases/">Hekate</a> Payload</li>
 <li>A microSD card larger than 32GB</li>
 </ul>
 <h3 id="instructions">Instructions:<a class="headerlink" href="#instructions" title="Permanent link">&para;</a></h3>
@@ -1730,7 +1730,7 @@ <h3 id="instructions">Instructions:<a class="headerlink" href="#instructions" ti
 <ul>
 <li>Note:  This section can be disregarded for modchipped Switch users.</li>
 </ul>
-<p>A system update is considered a security version when a fuse is burned, you can check <strong><a href="https://switchbrew.org/wiki/Fuses#Anti-downgrade" target=blank>which versions burn fuses here</a></strong>.</p>
+<p>A system update is considered a security version when a fuse is burned, you can check <strong><a href="https://switchbrew.org/wiki/Fuses#Anti-downgrade">which versions burn fuses here</a></strong>.</p>
 <p>If you were in AutoRCM before you upgraded to a newer security version (and still were after the upgrade) you don't have to do this.</p>
 <ol>
 <li>In Hekate's main menu, navigate to <code>Tools</code> and go to the bottom of the page where you will find a button called <code>Archive bit - AutoRCM</code></li>

extras/updating/index.html

@@ -1707,7 +1707,7 @@ <h3 id="updating-atmosphere"><strong>Updating Atmosphere</strong><a class="heade
 </ul>
 </li>
 <li>Navigate to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code> and plug your Switch into your PC via USB.</li>
-<li>Download the latest release of <a href="https://github.com/Atmosphere-NX/Atmosphere/releases" target="_blank">Atmosphere</a> (Download the <code>atmosphere-(version)-master-(version)+hbl-(version)+hbmenu-(version).zip</code> release of Atmosphere.)</li>
+<li>Download the latest release of <a href="https://github.com/Atmosphere-NX/Atmosphere/releases">Atmosphere</a> (Download the <code>atmosphere-(version)-master-(version)+hbl-(version)+hbmenu-(version).zip</code> release of Atmosphere.)</li>
 <li>Copy <em>the contents of</em> the Atmosphere <code>.zip</code> file to the root of your microSD card.<ul>
 <li>If you are prompted to overwrite files, do so.</li>
 </ul>
@@ -1724,7 +1724,7 @@ <h3 id="updating-hekate"><strong>Updating Hekate</strong><a class="headerlink" h
 </ul>
 </li>
 <li>Navigate to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code> and plug your Switch into your PC via USB.</li>
-<li>Download the latest version of <a href="https://github.com/CTCaer/Hekate/releases/" target="_blank">Hekate</a> (Download the <code>hekate_ctcaer_(version).zip</code> release of hekate).</li>
+<li>Download the latest version of <a href="https://github.com/CTCaer/Hekate/releases/">Hekate</a> (Download the <code>hekate_ctcaer_(version).zip</code> release of hekate).</li>
 <li>Copy the <code>bootloader</code> folder from the Hekate <code>.zip</code> file to the root of your microSD card. If you are asked to overwrite or merge files while copying, say yes to merge/overwrite them.</li>
 <li>Eject the <code>UMS</code> device safely from within your computer's operating system.</li>
 <li>Go back to Hekate's main menu and press <code>Reload</code> &gt; <code>Reload</code> to reload Hekate from your microSD card.</li>
@@ -1822,8 +1822,8 @@ <h3 id="updating-emummc-by-dumping-an-updated-firmware-from-your-sysmmc"><strong
 </div>
 <h4 id="what-you-need"><strong>What you need:</strong><a class="headerlink" href="#what-you-need" title="Permanent link">&para;</a></h4>
 <ul>
-<li>The latest release of <a href="https://github.com/suchmememanyskill/TegraExplorer/releases" target="_blank">TegraExplorer</a></li>
-<li>The latest release of <a href="https://github.com/Atmosphere-NX/Atmosphere/releases" target="_blank">Atmosphere</a></li>
+<li>The latest release of <a href="https://github.com/suchmememanyskill/TegraExplorer/releases">TegraExplorer</a></li>
+<li>The latest release of <a href="https://github.com/Atmosphere-NX/Atmosphere/releases">Atmosphere</a></li>
 </ul>
 <h4 id="preparing-your-microsd-card"><strong>Preparing your microSD card</strong><a class="headerlink" href="#preparing-your-microsd-card" title="Permanent link">&para;</a></h4>
 <ol>

faq/index.html

@@ -1742,7 +1742,7 @@ <h3 id="what-firmware-versions-are-currently-hackable"><strong>What firmware ver
 Currently the only way to know if your Switch is hackable is by trying to send the payload in RCM.
 Even with this exploit fixed, many Switch consoles on 8.0.1 and below will be hackable to some degree in the future (see <a href="#should-i-update-my-firmware">Should I update my Firmware?</a> for much more detailed information).
 The serial number on the back of the box can possibly tell you which consoles are patched and which aren't.
-See <a href="https://gbatemp.net/threads/switch-informations-by-serial-number.481215/" target="_blank">here</a> for an up to date list.</p>
+See <a href="https://gbatemp.net/threads/switch-informations-by-serial-number.481215/">here</a> for an up to date list.</p>
 <h3 id="how-do-i-use-fusee-gelee-how-can-i-boot-into-rcm"><strong>How do I use fusee-gelee? How can I boot into RCM?</strong><a class="headerlink" href="#how-do-i-use-fusee-gelee-how-can-i-boot-into-rcm" title="Permanent link">&para;</a></h3>
 <p>To launch CFW through the fusee-gelee, the Switch needs to be in "ReCovery Mode"(RCM).
 The easiest way to enter RCM is by grounding pin 10 in the right joycon rail and holding VOL+ on boot.
@@ -1775,7 +1775,7 @@ <h3 id="should-i-update-my-firmware"><strong>Should I update my Firmware?</stron
 On every boot the Switch firmware checks how many e-fuses have been burned and how many e-fuses the Switch expects to be burned.
 Major updates to the Switch, or updates in which a large vulnerability has been patched, irreversibly burn one of the Switch's 64 "e-fuses".
 <em>If the Switch ever detects that more e-fuses have been burned than expected (meaning a downgrade happened), it will refuse to boot. Replacing e-fuses is not an option.</em>
-You can find more information about fuses <a href="https://switchbrew.org/wiki/Fuses#Anti-downgrade" target="_blank">here</a>
+You can find more information about fuses <a href="https://switchbrew.org/wiki/Fuses#Anti-downgrade">here</a>
 Atmosphèreis maintained to support the latest firmware updates on unpatched units. The situation for patched and new units is as follows:</p>
 <ul>
 <li>
@@ -1794,7 +1794,7 @@ <h3 id="is-it-safe-to-use-homebrew-will-i-get-banned"><strong>Is it safe to use
 As long as the Switch is connected to the internet, Nintendo gets a report about a lot of different actions and states and has the option to log or act on them.
 Even if the Switch is offline and connects to the internet at a later point, Nintendo still recieves information about what happened while the Switch was disconnected.</p>
 <p>To disable some of this telemetry, it is advised to disable the sending of error reports in the System Settings of the Switch.
-Additionally if you live in the EU you can set the "do not share" option on <a href="https://accounts.nintendo.com/setting" target="_blank">Nintendo's website</a> to prevent your Switch from sending a lot of telemetry, although the effectiveness of this is questionable.</p>
+Additionally if you live in the EU you can set the "do not share" option on <a href="https://accounts.nintendo.com/setting">Nintendo's website</a> to prevent your Switch from sending a lot of telemetry, although the effectiveness of this is questionable.</p>
 <p>Nintendo still receives a lot of information, even with those options disabled.
 We also cannot know if Nintendo decides to look for something in the logs and ban people in retrospect.
 They have also shown to expand their telemetry options with every other firmware update.</p>
@@ -1835,7 +1835,7 @@ <h3 id="fake-microsd-cards"><strong>Fake microSD cards</strong><a class="headerl
 <p>Do not buy microSD cards from sites like eBay.
 These microSD cards are often fake and do not have the advertised amount of storage and will result in data corruption if used.
 Amazon has had some problems with fake microSD cards, so we recommend buying them at a physical store. Even on trustworthy sites, <em>always, always check reviews on a product before buying!!</em></p>
-<p>If you suspect your microSD card is fake or damaged, see the instructions <a href="https://wiki.hacks.guide/wiki/Checking_SD_card_integrity" target="_blank">here</a> to verify the integrity of your microSD card.</p>
+<p>If you suspect your microSD card is fake or damaged, see the instructions <a href="https://wiki.hacks.guide/wiki/Checking_SD_card_integrity">here</a> to verify the integrity of your microSD card.</p>
 <h3 id="my-homebrew-apps-are-not-showing-up-in-the-homebrew-menu"><strong>My Homebrew apps are not showing up in the Homebrew menu!</strong><a class="headerlink" href="#my-homebrew-apps-are-not-showing-up-in-the-homebrew-menu" title="Permanent link">&para;</a></h3>
 <p>This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your Homebrew apps, you may need to unset the archive bit with Hekate.</p>
 <ol>

homebrew/edizon/index.html

@@ -1718,10 +1718,14 @@ <h4 id="installation-requirements">Installation requirements:<a class="headerlin
 <ol>
 <li>Boot into Hekate and go to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code>, then plug your Switch into your PC via USB.</li>
 <li>Your microSD card should now be accessible on your PC, open it.</li>
-<li>Extract the <code>.zip</code> file to a location on your computer.</li>
+<li>Extract the <code>.zip</code> file to a location on your computer.<ul>
 <li>If your archive manager allows for it, you can also simply open the <code>.zip</code> file directly.</li>
-<li>Copy the <em>contents</em> of the (extracted) <code>.zip</code> file to the root of your microSD card.</li>
+</ul>
+</li>
+<li>Copy the <em>contents</em> of the (extracted) <code>.zip</code> file to the root of your microSD card.<ul>
 <li><strong>Optional:</strong> You can verify if you've installed EdiZon-SE correctly, you should have a folder called <code>054e4f4558454000</code> (EdiZon-SE) in <code>sd:/atmosphere/contents</code> and an <code>EdiZon.nro</code> file in <code>sd:/switch/EdiZon</code>.</li>
+</ul>
+</li>
 <li>Boot into CFW.</li>
 </ol>
 </div>

homebrew/nxtheme-installer/index.html

@@ -1712,7 +1712,7 @@ <h3 id="index"><strong>Index</strong><a class="headerlink" href="#index" title="
 <h3 id="installing-a-theme"><strong>Installing a theme</strong><a class="headerlink" href="#installing-a-theme" title="Permanent link">&para;</a></h3>
 <div class="admonition note">
 <p class="admonition-title">Community Themes</p>
-<p>If you want to use community made themes, for example from the <a href="https://www.reddit.com/r/NXThemes/" target="_blank">r/NXThemes</a> subreddit or <a href="https://themezer.net">Themezer</a>, you can follow the guide below to install a community provided <code>.nxtheme</code> file.</p>
+<p>If you want to use community made themes, for example from the <a href="https://www.reddit.com/r/NXThemes/">r/NXThemes</a> subreddit or <a href="https://themezer.net">Themezer</a>, you can follow the guide below to install a community provided <code>.nxtheme</code> file.</p>
 </div>
 <h4 id="what-you-need"><strong>What you need:</strong><a class="headerlink" href="#what-you-need" title="Permanent link">&para;</a></h4>
 <ul>
@@ -1748,7 +1748,7 @@ <h3 id="making-a-theme"><strong>Making a theme</strong><a class="headerlink" hre
 <div class="tabbed-content">
 <div class="tabbed-block">
 <h4 id="what-you-need_1"><strong>What you need:</strong><a class="headerlink" href="#what-you-need_1" title="Permanent link">&para;</a></h4>
-<p>The latest release of <a href="https://github.com/exelix11/SwitchThemeInjector/releases" target="_blank"><strong>Switch Theme Injector</strong></a></p>
+<p>The latest release of <a href="https://github.com/exelix11/SwitchThemeInjector/releases"><strong>Switch Theme Injector</strong></a></p>
 <ul>
 <li>You need to download the <code>ReleaseVx.x.zip</code> on the download page</li>
 </ul>
@@ -1765,7 +1765,7 @@ <h4 id="making-the-theme"><strong>Making the theme</strong><a class="headerlink"
 <h4 id="making-the-theme_1"><strong>Making the theme</strong><a class="headerlink" href="#making-the-theme_1" title="Permanent link">&para;</a></h4>
 <p>Make sure that the images you want to use are 1280x720 and in JPG!</p>
 <ol>
-<li>Navigate to <a href="https://exelix11.github.io/SwitchThemeInjector/v2/" target="_blank"><strong>Exelix's Web Injector</strong></a>.</li>
+<li>Navigate to <a href="https://exelix11.github.io/SwitchThemeInjector/v2/"><strong>Exelix's Web Injector</strong></a></li>
 <li>Select a Theme Target you want to edit. After this, click the Open an Image button and select your background image.</li>
 <li>Choose a theme name and an author name and optionally a different layout, then click build NxTheme.</li>
 <li>Your browser will prompt you to download a file. Save this file to a temporary folder.</li>