docs/case_closed_debugging_cr50.md: Unify shell prompt formatting

Use the standard used across the documentation for specifying different
shell prompts:

(chroot) $
(dut) $
cr50 >

This makes it clear where the command should be run.

BUG=none
TEST=view in gitiles

Signed-off-by: Tom Hughes <tomhughes@chromium.org>
Change-Id: I0383e00825b5d9b500464ac1979555ca5afd8296
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2136870
Commit-Queue: Mary Ruthven <mruthven@chromium.org>
Reviewed-by: Mary Ruthven <mruthven@chromium.org>
(cherry picked from commit 8f13313b8b0b8787e01f5604cc6b812155c2a6ac)
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2278522
Tested-by: Vadim Bendebury <vbendeb@chromium.org>

1 files changed, 211 insertions, 140 deletions

diff --git a/docs/case_closed_debugging_cr50.md b/docs/case_closed_debugging_cr50.md
index 7cc97977eb..e46bca66c6 100644
--- a/docs/case_closed_debugging_cr50.md
+++ b/docs/case_closed_debugging_cr50.md
@@ -72,31 +72,38 @@ differences between the MP and prePVT versions of images. It is just a little
 easier to CCD open prePVT images. You can't run prePVT images on MP devices, so
 if you're trying to update to .prepvt and it fails try using .prod.
 
-*   Sync chroot to TOT (run repo sync in chromiumos directory) update servod and
-    gsctool in chroot
+*   Sync chroot to TOT (run `repo sync` in chromiumos directory) update `servod`
+    and `gsctool` in chroot
 
-        from chroot > sudo emerge hdctools ec-devutils servo-firmware
-                  chromeos-cr50 chromeos-cr50-scripts
+    ```bash
+    (chroot) $ sudo emerge hdctools ec-devutils servo-firmware chromeos-cr50 chromeos-cr50-scripts
+    ```
 
 *   Update servo v4 firmware
 
-        from chroot > sudo servo_updater -b servo_v4
+    ```bash
+    (chroot) $ sudo servo_updater -b servo_v4
+    ```
 
-*   Ensure cr50 firmware is up to date. You can run these gsctool commands from
-    the AP console or you can run them as root from inside the chroot if suzyq
-    is connected.
+*   Ensure cr50 firmware is up to date. You can run these `gsctool` commands
+    from the AP console or you can run them as root from inside the chroot if
+    suzyq is connected.
 
     *   If you're doing this from the AP, install a test image newer than M66.
     *   check the cr50 version
 
-                sudo gsctool -a -f
+        ```bash
+        (dut) $ sudo gsctool -a -f
+        ```
 
     *   If the RW version is greater than 0.(3|4).9 then you don't need to
         update cr50. If it's not, then you need to update cr50.
 
     *   Update cr50.
 
-                sudo gsctool -a /opt/google/cr50/firmware/cr50.bin.prod
+        ```bash
+        (dut) $ sudo gsctool -a /opt/google/cr50/firmware/cr50.bin.prod
+        ```
 
     *   Check the cr50 version again to make sure it's now newer than 0.X.9
 
@@ -112,16 +119,16 @@ if you're trying to update to .prepvt and it fails try using .prod.
     lowest `/dev/ttyUSB*` device created by Cr50 or `/dev/google/<device
     name>/serial/Shell`
 
-2.  [Open CCD](#Open-CCD)
+1.  [Open CCD](#Open-CCD)
 
-3.  [Modify capabilities](#Enable-Open-Without-Requiring-Device-to-Boot) to make
+1.  [Modify capabilities](#Enable-Open-Without-Requiring-Device-to-Boot) to make
     it easier to open cr50 or access necessary capabilities - this step is
     optional, but **the open state will be lost if cr50 reboots or the device
     loses power**. If your use of CCD will possibly brick the device, it is
     recommended you modify the capability settings or set a ccd password, so you
     can reopen the device.
 
-4.  Use CCD
+1.  Use CCD
 
 ## Open CCD
 
@@ -131,7 +138,9 @@ https://storage.googleapis.com/chromeos-localmirror/distfiles/cr50.r0.0.10.w0.3.
 
 You can download the cr50 image and then flash cr50 using Suzy-Q from the chroot
 
-    from chroot > sudo gsctool cr50.r0.0.10.w0.3.9/cr50.bin.prod
+```bash
+(chroot) $ sudo gsctool cr50.r0.0.10.w0.3.9/cr50.bin.prod
+```
 
 If you are only briefly using ccd and aren’t doing anything that may brick the
 device, you can probably just stick to opening cr50. **The open state will be
@@ -153,43 +162,30 @@ will not work.
     set GBB flags by running. If you can’t access the shell, because you aren’t
     in dev mode, then you’re fine. You can skip steps 1, 2, and 3.
 
-        AP > /usr/share/vboot/bin/get_gbb_flags.sh
-
-2.  Clear 0x8 from the GBB flags and set the new value
+    ```bash
+    (chroot) $ /usr/share/vboot/bin/get_gbb_flags.sh
+    ```
 
-        AP > /usr/share/vboot/bin/set_gbb_flags.sh $OLD_FLAG_VALUE & ~0x8
+1.  Clear `0x8` from the GBB flags and set the new value
 
-3.  Reboot the device
+    ```bash
+    (chroot) $ /usr/share/vboot/bin/set_gbb_flags.sh $OLD_FLAG_VALUE & ~0x8
+    ```
 
-4.  Put the device into recovery mode
+1.  Reboot the device
 
-    -   **Tablets/Detachables** - hold power button vol up and vol down for 10
-        seconds. Release and wait until the device boots into recovery
-    -   **Clamshells/Convertibles** - press power button escape refresh
-    -   **Chromeboxes** - Use a paperclip to press the recovery button while
-        plugging in AC.
-    -   **Using servo** - If cr50 is open or you are using a flex cable you can,
-        you can use `dut-control power_state:rec`
+1.  Put the device into [Recovery Mode].
 
-5.  Enable developer mode
+1.  Enable [Developer Mode].
 
-    -   **Tablets/Detachables** - After the device boots into recovery, press
-        volume up and volume down at the same time to get to the enable dev mode
-        menu. Use volume up button to navigate to “confirm disabling os
-        verification” use the power button to select it
-    -   **Clamshells/Convertibles** - press ctrl+d on keyboard or AP console to
-        select developer mode then enter to enable it.
-    -   **Chromeboxes** - Use a paper clip to press the dedicated recovery
-        button
-
-6.  Verify Cr50 knows the device is in dev mode. The TPM state will print
+1.  Verify Cr50 knows the device is in dev mode. The TPM state will print
     `dev_mode` if cr50 knows the device is in dev mode. If it doesn’t say
     `dev_mode`, ccd open will fail. If you see "`TPM: dev_mode`" you are okay to
     CCD open now. **If you don’t see `TPM: dev_mode`, recheck the gbb flags to
     make sure they aren’t forcing dev mode. Retry the manual entry of dev
     mode.**
 
-```
+    ```
     cr50 > ccd
           State: Locked
           Password: none
@@ -216,7 +212,7 @@ will not work.
           OpenFromUSB     - 0=Default (IfOpened)
           TPM: dev_mode                         <==== This is the important part
           Use 'ccd help' to print subcommands
-```
+    ```
 
 #### Run ccd open
 
@@ -225,12 +221,14 @@ need to press the power button when prompted open cr50.
 
 1.  Start the ccd open process from the AP.
 
-         AP shell > gsctool -a -o
+    ```bash
+    (chroot) $ gsctool -a -o
+    ```
 
-2.  Over the next 5 minutes you will be prompted to tap the power button.
+1.  Over the next 5 minutes you will be prompted to press the power button.
 
-3.  After the process is finished, use ‘ccd’ on the cr50 console to verify the
-    state is open
+1.  After the process is finished, use ‘ccd’ on the cr50 console to verify the
+    state is open.
 
 The Open setting will be lost whenever cr50 reboots. Make sure to setup ccd so
 you will be able to recover the device even if Open is lost. To open cr50 you
@@ -265,18 +263,22 @@ correctly before flashing the AP/EC.
 
 1.  Disconnect the battery
 
-2.  Send ‘ccd open’ from the cr50 console.
+1.  Send `ccd open` from the cr50 console.
 
 #### CCD testlab is enabled
 
-You can check if testlab is enabled cr50 from the console.
+You can check if `testlab` is enabled cr50 from the console.
 
-    cr50 > ccd testlab
-            CCD test lab mode enabled
+```
+cr50 > ccd testlab
+       CCD test lab mode enabled
+```
 
 If it’s enabled, you can open cr50 from the console without physical presence.
 
-    cr50 > ccd testlab open
+```
+cr50 > ccd testlab open
+```
 
 #### OpenNoDevMode and OpenFromUSB are set to Always
 
@@ -289,7 +291,9 @@ cr50 from the console without dev mode.
 
 You can run ccd open with the password to open from the console.
 
-    cr50 > ccd open $PASSWORD
+```
+cr50 > ccd open $PASSWORD
+```
 
 ## Configure CCD
 
@@ -309,12 +313,16 @@ You can go through the capability descriptions and figure out which ccd
 capabilities you want to use. After you figure that out you can modify the
 capabilities to Always be accessible.
 
-    > ccd set $CAP $REQ
+```
+cr50 > ccd set $CAP $REQ
+```
 
 For example if the EC console needs to be read-write even when Cr50 is locked
 set the capability to Always.
 
-    > ccd set UartGscTxECRx Always
+```
+cr50 > ccd set UartGscTxECRx Always
+```
 
 If you want to restrict capabilities more you can set them to IfOpened. If you
 don’t want the AP/EC uart to be accessible at all when cr50 is locked, you can
@@ -322,26 +330,36 @@ set them all to IfOpened.
 
 Restrict EC
 
-    > ccd set UartGscTxECRx IfOpened
-    > ccd set UartGscRxECTx IfOpened
+```
+cr50 > ccd set UartGscTxECRx IfOpened
+cr50 > ccd set UartGscRxECTx IfOpened
+```
 
 Restrict AP
 
-    > ccd set UartGscTxAPRx IfOpened
-    > ccd set UartGscRxAPTx IfOpened
+```
+cr50 > ccd set UartGscTxAPRx IfOpened
+cr50 > ccd set UartGscRxAPTx IfOpened
+```
 
 If you want things as accessible as possible and want all capabilities to be
 Always, you can run
 
-    > ccd reset factory
+```
+cr50 > ccd reset factory
+```
 
 This will also permanently disable write protect. To reset write protect run
 
-    > wp follow_batt_pres atboot
+```
+cr50 > wp follow_batt_pres atboot
+```
 
 To reset capabilities to Default run
 
-    > ccd reset
+```
+cr50 > ccd reset
+```
 
 ### Enable Open Without Requiring Device to Boot
 
@@ -357,8 +375,10 @@ is best for you.
 After opening cr50, you can set these capabilities to reduce the restrictions
 required to open cr50.
 
-    > ccd set OpenFromUSB Always
-    > ccd set OpenNoDevMode Always
+```
+cr50 > ccd set OpenFromUSB Always
+cr50 > ccd set OpenNoDevMode Always
+```
 
 #### CCD Password
 
@@ -369,22 +389,27 @@ can be done to reopen cr50.
 
 ##### Set Password
 
-Run the gsctool command and enter the password when prompted. It will prompt for
-the password twice.
+Run the `gsctool` command and enter the password when prompted. It will prompt
+for the password twice.
 
-    from ap shell > gsctool -a -P
+```bash
+(chroot) $ gsctool -a -P
+```
 
 You can use the ccd command to check if the password is set.
 
-    cr50 > ccd
-           ...
-           Password: [none|set]
-           ...
+```
+cr50 > ccd
+       ...
+       Password: [none|set]
+       ...
+```
 
 ##### Clear Password
 
-You can clear the password by opening cr50 and then running the gsctool command
-agatin. When prompted for the password enter `clear:$PASSWORD` at both prompts.
+You can clear the password by opening cr50 and then running the `gsctool`
+command again. When prompted for the password enter `clear:$PASSWORD` at both
+prompts.
 
 You can also use the cr50 `ccd reset` command when cr50 is open. This will clear
 the password and reset all ccd capabilities to default.
@@ -394,13 +419,17 @@ the password and reset all ccd capabilities to default.
 After the password has been set you can use it to run ccd commands from the cr50
 console.
 
-    cr50 > ccd open $PASSWORD
-    cr50 > ccd unlock $PASSWORD
+```
+cr50 > ccd open $PASSWORD
+cr50 > ccd unlock $PASSWORD
+```
 
 You can use it from the AP shell
 
-    cr50 > gsctool -a -o
-    cr50 > gsctool -a -u
+```
+cr50 > gsctool -a -o
+cr50 > gsctool -a -u
+```
 
 enter the password when prompted
 
@@ -415,13 +444,17 @@ can use a cr50 command to tell cr50 to ignore the voltages on these cc lines and
 just keep ccd enabled. There are many things that could interfere with rdd, so
 it’s probably best to run this before doing anything else using ccd.
 
-    cr50 > rddkeepalive enable
+```
+cr50 > rddkeepalive enable
+```
 
 This command is useful for making sure ccd stays enabled during debugging. It
 will increase cr50 power a lot when the debug cable is disconnected. If you’re
 worried about that, disable rddkeepalive when you're not using ccd.
 
-    cr50 > rddkeepalive disable
+```
+cr50 > rddkeepalive disable
+```
 
 ## Consoles
 
@@ -441,11 +474,15 @@ relevant ones.
 
 Servo can also figure this out for you. You can start servo like you normally do
 
-    chroot > sudo servod -b $BOARD
+```bash
+(chroot) $ sudo servod -b $BOARD
+```
 
 After starting servo, you can use dut-control to get the consoles
 
-    chroot > dut-control cr50_uart_pty ec_uart_pty cpu_uart_pty
+```bash
+(chroot) $ dut-control cr50_uart_pty ec_uart_pty cpu_uart_pty
+```
 
 ## Flashing EC
 
@@ -459,8 +496,10 @@ can get pretty complicated and are board specific.
 You will need to start servod then `flash_ec` will handle sending the correct
 cr50 console commands and updating the EC.
 
-    chroot > sudo servod -b $BOARD
-    chroot > ~/trunk/src/platform/ec/util/flash_ec -i $IMAGE -b $BOARD
+```bash
+(chroot) $ sudo servod -b $BOARD
+(chroot) $ ~/trunk/src/platform/ec/util/flash_ec -i $IMAGE -b $BOARD
+```
 
 ## Flashing the AP
 
@@ -469,7 +508,9 @@ flash the AP.
 
 Flashing the AP is standard across boards.
 
-    chroot > sudo flashrom -p raiden_debug_spi:target=AP -w $IMAGE
+```bash
+(chroot) $ sudo flashrom -p raiden_debug_spi:target=AP -w $IMAGE
+```
 
 This default flashing command takes a very long time to complete, there are ways
 to speed up flashing process by cutting some corners, see the next section.
@@ -477,11 +518,15 @@ to speed up flashing process by cutting some corners, see the next section.
 If you have a lot of ccd devices plugged in, you may want to use the cr50
 serialname. You can get this by running
 
-    chroot > lsusb -vd 18d1:5014 | grep iSer
+```bash
+(chroot) $ lsusb -vd 18d1:5014 | grep iSer
+```
 
 You can add the serialname to the flashrom command using
 
-    chroot > sudo flashrom -p raiden_debug_spi:target=AP,serial=$SERIAL -w $IMAGE
+```bash
+(chroot) $ sudo flashrom -p raiden_debug_spi:target=AP,serial=$SERIAL -w $IMAGE
+```
 
 **If you don’t see cr50 print any messages when you’re running the flashrom
 command, you probably need to use the serialname.**
@@ -527,29 +572,31 @@ Only a few sections are essential for maintaining the device identity and for
 booting the device in recovery mode. The `-i` command line option of `flashrom`
 allows the user to indicate which sections should be read/written.
 
-The below sequence of commands allows to quickly reprogram the AP flash: ``` #
-This will save device flash map and VPD sections in # /tmp/bios.essentials.bin.
-VPD sections contain information like device # firmware ID, WiFi calibration,
-enrollment status, etc. Use the below command # only if you need to preserve the
-DUT's identity, no need to run it in case # the DUT flash is not programmed at
-all, or you do not care about preserving # the device identity. sudo flashrom -p
-raiden_debug_spi:target=AP -i FMAP -i RO_VPD -i RW_VPD -r
-/tmp/bios.essentials.bin --fast-verify
-
-\# This command will erase the entire flash chip in one shot, the fastest #
-possible way to erase. sudo flashrom -p raiden_debug_spi:target=AP -E
---do-not-diff
-
-\# This command will program essential flash sections necessary for the # Chrome
-OS device to boot in recovery mode. Note that the SI_ALL section is # not always
-present in the flash image, do not include it if it is not in # dump_fmap
-output. sudo flashrom -p raiden_debug_spi:target=AP -w image-atlas.bin -i FMAP
--i WP_RO [-i SI_ALL] --do-not-diff --noverify
-
-\# This command will restore the previously preserved VPD sections of the #
-flash, provided it was saved in the first step above. sudo flashrom -p
-raiden_debug_spi:target=AP -w /tmp/bios.essential.bin -i RO_VPD -i RW_VPD
---do-not-diff --noverify ```
+The below sequence of commands allows to quickly reprogram the AP flash:
+
+```bash
+# This will save device flash map and VPD sections in
+# /tmp/bios.essentials.bin. VPD sections contain information like device
+# firmware ID, WiFi calibration, enrollment status, etc. Use the below command
+# only if you need to preserve the DUT's identity, no need to run it in case
+# the DUT flash is not programmed at all, or you do not care about preserving
+# the device identity.
+sudo flashrom -p raiden_debug_spi:target=AP -i FMAP -i RO_VPD -i RW_VPD -r /tmp/bios.essentials.bin --fast-verify
+
+# This command will erase the entire flash chip in one shot, the fastest
+# possible way to erase.
+sudo flashrom -p raiden_debug_spi:target=AP -E --do-not-diff
+
+# This command will program essential flash sections necessary for the
+# Chrome OS device to boot in recovery mode. Note that the SI_ALL section is
+# not always present in the flash image, do not include it if it is not in
+# dump_fmap output.
+sudo flashrom -p raiden_debug_spi:target=AP -w image-atlas.bin -i FMAP -i WP_RO [-i SI_ALL] --do-not-diff --noverify
+
+# This command will restore the previously preserved VPD sections of the
+# flash, provided it was saved in the first step above.
+sudo flashrom -p raiden_debug_spi:target=AP -w /tmp/bios.essential.bin -i RO_VPD -i RW_VPD --do-not-diff --noverify
+```
 
 Once flash is programmed, the device can be booted in recovery mode and start
 Chrome OS from external storage, following the usual recovery procedure. Once
@@ -566,8 +613,8 @@ write protect using battery presence.
 
 You can use the cr50 console command to change the write protect settings.
 
-There are three write protect settings: `forced enabled, forced disabled,
-follow_batt_pres`.
+There are three write protect settings: `forced enabled`, `forced disabled`,
+`follow_batt_pres`.
 
 *   **`follow_batt_pres`** - DEFAULT SETTING - use battery presence to determine
     the write protect setting. If the battery is connected, enable write
@@ -584,12 +631,14 @@ follow_batt_pres`.
 
 You can set these from the cr50 console
 
-    cr50 > wp [enable|disable|follow_batt_pres]
+```
+cr50 > wp [enable|disable|follow_batt_pres]
+```
 
 This setting will persist until it is cleared using the wp command or until cr50
-reboots/loses power. After these resets, cr50 will default to the atboot
-setting. The default setting is follow\_batt\_pres, so cr50 will go back to
-following battery presence after reboot unless the atboot setting has been
+reboots/loses power. After these resets, cr50 will default to the `atboot`
+setting. The default setting is `follow_batt_pres`, so cr50 will go back to
+following battery presence after reboot unless the `atboot` setting has been
 overridden.
 
 Using the `atboot` arg will update the current and atboot wp state. If the
@@ -599,23 +648,27 @@ want to disable/enable write protect for a short time, make sure atboot is set
 to `follow_batt_pres`. If you want to permanently disable or enable write
 protect and want to ignore the battery, this is a good setting to update.
 
-    cr50 > wp [enable|disable|follow_batt_pres]
+```
+cr50 > wp [enable|disable|follow_batt_pres]
+```
 
 You can use the wp command to get the write protect state even if the capability
 is restricted.
 
 ```
-    cr50 > wp
+cr50 > wp
 
-           Flash WP: [forced ]enabled|disabled
-             atboot: forced enabled | force disabled | follow_batt_pres
+       Flash WP: [forced ]enabled|disabled
+         atboot: forced enabled | force disabled | follow_batt_pres
 ```
 
-Gsctool also supports getting the write protect state
+`gsctool` also supports getting the write protect state
 
-    AP > gsctool -a -W
+```bash
+(dut) $ gsctool -a -W
+```
 
-The output will show the current and atboot setting.
+The output will show the current and `atboot` setting.
 
 The current wp setting will not explicitly show that write protect is currently
 following battery presence. You have to get this by checking if the wp state is
@@ -623,11 +676,11 @@ following battery presence. You have to get this by checking if the wp state is
 console command. If it just shows the state without forced, write protect is
 following battery presence.
 
-The atboot setting shows what the wp state will reset to after reboot.
+The `atboot` setting shows what the wp state will reset to after reboot.
 
 ### Battery Presence
 
-If the OverriedWP command isn’t accessible, you can use battery presence to
+If the OverrideWP command isn’t accessible, you can use battery presence to
 change the wp state as long as the wp setting is still `follow_batt_pres`.
 
 *   wp disable - disconnect the battery
@@ -637,7 +690,9 @@ change the wp state as long as the wp setting is still `follow_batt_pres`.
 If the wp setting has been overridden by ccd, this won’t work until the current
 wp setting is reset to `follow_batt_pres`
 
-    cr50 > wp follow_batt_pres atboot
+```
+cr50 > wp follow_batt_pres atboot
+```
 
 ### HW WP Issues
 
@@ -657,7 +712,7 @@ need to remove the screw.
 
 #### AP Off
 
-Cr50 puts the device in reset to flash the AP. Due to hardware limitiations Cr50
+Cr50 puts the device in reset to flash the AP. Due to hardware limitations Cr50
 may not be able to disable write protect while the device is in reset. If you
 want to reflash RO firmware using CCD and your board has issues disabling HW WP,
 you may need to disable SW write protect.
@@ -666,15 +721,19 @@ Check if your board has this issue
 
 1.  Disable write protect using the cr50 console command
 
-2.  Check it's still disabled when the AP is off. This command should show write
+1.  Check it's still disabled when the AP is off. This command should show write
     protect is disabled. If it shows it's enabled, then cr50 can't disable WP
     when the AP is off. You should disable SW WP to flash RO firmware using ccd.
 
-        chroot > sudo flashrom -p raiden_debug_spi:target=AP --wp-status
+    ```bash
+    (chroot) $ sudo flashrom -p raiden_debug_spi:target=AP --wp-status
+    ```
 
 Disable SW WP if the ccd flashrom command doesn't show write protect disabled.
 
-    from AP > flashrom -p host --wp-disable
+```bash
+(chroot) $ flashrom -p host --wp-disable
+```
 
 # CCD as a Servo replacement
 
@@ -683,10 +742,12 @@ able to be used as a servo replacement. It has all of the capabilities servo
 does and support has been added to hdctools to convert servo controls to cr50
 and ec console commands.
 
-If you start servod and select the ccd device, you should be able to use servo
-dut-control comands normally.
+If you start `servod` and select the ccd device, you should be able to use servo
+`dut-control` commands normally.
 
-    chroot > sudo servod -b $BOARD
+```bash
+(chroot) $ sudo servod -b $BOARD
+```
 
 If cr50 reboots or usb disconnects for some reason, servod will lose the
 connection to the cr50 usb. Support has just been added to hdctools to
@@ -731,7 +792,7 @@ The `cr50-rescue` utility is used to flash a given firmware to cr50 using rescue
 mode. This tool must be installed inside the chroot.
 
 ```bash
-sudo emerge cr50-utils
+(chroot) $ sudo emerge cr50-utils
 ```
 
 ## Preparing an RW image
@@ -739,7 +800,9 @@ sudo emerge cr50-utils
 To prepare the signed hex RW image, fetch a released image from Google storage,
 which can be found by running:
 
-`gsutil ls gs://chromeos-localmirror/distfiles/cr50*`
+```bash
+(chroot) $ gsutil ls gs://chromeos-localmirror/distfiles/cr50*
+```
 
 (depending on your setup you might have to do this inside chroot). Copy the
 image you want to use for rescue to your workstation and extract cr50.bin.prod
@@ -753,7 +816,7 @@ Once the binary image is ready, use the following commands to carve out the RW A
 section out of it and convert it into hex format:
 
 ```bash
-dd if=<cr50 bin file> of=cr50.rw.bin skip=16384 count=233472 bs=1
+(chroot) $ dd if=<cr50 bin file> of=cr50.rw.bin skip=16384 count=233472 bs=1
 objcopy -I binary -O ihex --change-addresses 0x44000 cr50.rw.bin cr50.rw.hex
 ```
 
@@ -762,11 +825,17 @@ then you can use `cr50.rw.hex` as the image passed to `cr50-rescue`.
 ## Programming the RW image with rescue mode
 
 With servo_micro (or servo_v2 reworked for connecting to Cr50 console), run
-servod and disable cr50 ec3po and uart timestamp: `bash dut-control
-cr50_uart_timestamp:off dut-control cr50_ec3po_interp_connect:off`
+servod and disable cr50 ec3po and uart timestamp:
 
-Get a raw cr50 uart device path and use it for cr50-rescue argument ‘-d’ below.
-`bash dut-control raw_cr50_uart_pty`
+```bash
+(chroot) $ dut-control cr50_uart_timestamp:off dut-control cr50_ec3po_interp_connect:off
+```
+
+Get a raw cr50 uart device path and use it for cr50-rescue argument `-d` below.
+
+```bash
+(chroot) $ dut-control raw_cr50_uart_pty
+```
 
 Prior to running `cr50-rescue`, the terminal from the cr50 console UART must be
 disconnected, and cr50 must be unpowered-- the system needs to have AC power and
@@ -775,8 +844,7 @@ battery disconnected.
 After ensuring those steps, the rescue command may be run as follows:
 
 ```bash
-cr50-rescue -v -i <path to the signed hex RW image>
-        -d <cr50 console UART tty>
+(chroot) $ cr50-rescue -v -i <path to the signed hex RW image> -d <cr50 console UART tty>
 ```
 
 After starting the command, provide power to the board and rescue mode will
@@ -797,8 +865,9 @@ currently present RW and RW_B images will be wiped out first.
 
 ### Sample output
 
-```
-cr50-rescue -v -i cr50.3.24.rw.hex -d /dev/pts/0
+```bash
+(chroot) $ cr50-rescue -v -i cr50.3.24.rw.hex -d /dev/pts/0
+
 low 00044000, high 0007cfff
 base 00044000, size 00039000
 ..startAdr 00000000
@@ -823,3 +892,5 @@ oops?|0.1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19.20.21.22.23.24.25.26.27.
 ```
 
 [chromeos-cr50 ebuild]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/refs/heads/master/chromeos-base/chromeos-cr50/chromeos-cr50-0.0.1.ebuild
+[Developer Mode]: https://chromium.googlesource.com/chromiumos/docs/+/master/developer_mode.md#dev-mode
+[Recovery Mode]: https://chromium.googlesource.com/chromiumos/docs/+/master/debug_buttons.md