From 3c732c0dafde0d3420ba9e4c978f74e7c9a1eb26 Mon Sep 17 00:00:00 2001 From: Plailect Date: Mon, 14 Aug 2017 16:56:23 -0400 Subject: [PATCH] whitespace --- _pages/en_US/finalizing-setup.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/_pages/en_US/finalizing-setup.txt b/_pages/en_US/finalizing-setup.txt index ecc6fd079..0a32f03b8 100644 --- a/_pages/en_US/finalizing-setup.txt +++ b/_pages/en_US/finalizing-setup.txt @@ -4,7 +4,6 @@ title: "Finalizing Setup" #### Overview of steps - The file `boot.firm` is what is launched by boot9strap itself after it finishes loading off of NAND, and can be any valid arm9 payload in the FIRM format. This file can be replaced at any time, although Luma3DS allows for the launch of other arm9 payloads in the FIRM format using the Luma3DS chainloader. In this case, we use Luma3DS by [AuroraWright](https://github.com/AuroraWright/) to boot a patched SysNAND directly, allowing us to completely bypass the need for any kind of EmuNAND, vastly simplifying the usage of a hacked 3DS in addition to saving SD card space.