Merge pull request #139 from leahneukirchen/tweaks

Two small changes that stumped me a bit

src/docs/firmware/suzyq.md

@@ -19,7 +19,7 @@ This method requires a SuzyQable, a chromeOS debug cable.
 1. Open VT-2 (`ctrl` + `alt` + `f2` (right arrow)).
 2. Login as `root`.
 3. Run `gsctool -a -o`. 
-4. You will be prompted to press the `PP` (physical presence) button several times. This is a fancy way of saying to press the power button.
+4. You will be prompted to press the `PP` (physical presence) button several times. This is a fancy way of saying to press the power button. This process takes several minutes and ends with the message `PP Done!`.
 5. The device will suddenly reboot and exit developer mode. Re-enable developer mode and continue with the instructions.
 
 ## Step 2: Disable Write Protect.

src/docs/unbricking/unbrick-suzyq.md

@@ -75,7 +75,7 @@ You don't need to do this if flashing a stock firmware backup created by the Fir
 1. For both the options below, we'll need to use the cbfstool (coreboot filesystem) binary, so let's download/extract that:
     * `wget https://mrchromebox.tech/files/util/cbfstool.tar.gz && tar -zxf cbfstool.tar.gz`
     * Option 1: Extract VPD from the firmware on device
-        * `sudo flashrom -p ch341a_spi -r badflash.rom`
+        * `sudo flashrom -p raiden_debug_spi:target=AP -r badflash.rom`
         * `./cbfstool badflash.rom read -r RO_VPD -f vpd.bin`
     * Option 2: Extract VPD from stock firmware backup created by Firmware Utility Script (this assumes the file has been copied into working directory)
         * `./cbfstool stock-firmware-<devicename>-<date>.rom read -r RO_VPD -f vpd.bin`