diff --git a/PAKS.md b/PAKS.md
index 77eeed083..b334b4d95 100644
--- a/PAKS.md
+++ b/PAKS.md
@@ -41,7 +41,7 @@ Here's an example "launch.sh":
 	mkdir -p "$CHEATS_PATH/$EMU_TAG"
 	HOME="$USERDATA_PATH"
 	cd "$HOME"
-	minarch.elf "$CORES_PATH/${EMU_EXE}_libretro.so" "$ROM" &> "$LOGS_PATH/$EMU_TAG.txt"
+	minarch.elf "$CORES_PATH/${EMU_EXE}_libretro.so" "$ROM" > "$LOGS_PATH/$EMU_TAG.txt" 2>&1
 
 This will open the requested rom using the "picodrive\_libretro.so" core included with the base NextUI install. To use a different core just change the value of `EMU_EXE` to another core name (minus the "_libretro.so"). If that core is bundled in your pak add the following after the `EMU_EXE` line:
 
@@ -51,8 +51,6 @@ There's no need to edit anything below the line of hash marks. The rest is boile
 
 That's it! Feel free to experiement with cores from the stock firmware, other compatible devices, or building your own.
 
-Oh, if you're creating a pak for Anbernic's RG*XX line you'll need to change the last part of the last line from ` &> "$LOGS_PATH/$EMU_TAG.txt"` to ` > "$LOGS_PATH/$EMU_TAG.txt" 2>&1` because its default shell is whack.
-
 # Option defaults and button bindings
 
 Copy your new pak and some roms to your SD card and launch a game. Press the MENU button and select Options. Configure the Frontend, Emulator, and Controls. NextUI standard practice is to only bind controls present on the physical controller of the original system (eg. no turbo buttons or core-specific features like palette or disk switching). Let the player dig into that if they want to, the same goes for Shortcuts. Finally select Save Changes > Save for Console. Then quit and pop your SD card back into your computer.