readme: Update product names

Author: timg236

Readme.md

@@ -11,7 +11,7 @@ For more information, run `rpiboot -h`.
 Devices supporting the fast Linux-based `mass-storage-gadget`
 
 * Raspberry Pi Zero2W
-* Raspberry Pi
+* Raspberry Pi 3A+
 * Compute Module 3
 * Compute Module 3+
 * Compute Module 3E
@@ -25,8 +25,8 @@ Devices supporting the fast Linux-based `mass-storage-gadget`
 * Compute Module 5
 
 Devices which require the legacy `msd` firmware loading interface
-* Raspberry Pi 1A
-* Compute Module
+* Raspberry Pi 1A+
+* Compute Module 1
 * Raspberry Pi Zero
 
 The `mass-storage-gadget` boots a Linux initramfs image that scans for SD/EMMC, NVMe, and USB block devices and uses `configfs` to expose them as USB mass-storage devices. Because it runs Linux, it also provides a console login via both the hardware UART and the USB CDC-UART interfaces.
@@ -135,6 +135,18 @@ submodules by running:
 git submodule update --init
 ```
 
+## Enabling `rpiboot` support - Pi 4B, Pi 400 & Pi 500
+
+### Pi 4B and Pi 400
+Raspberry Pi 4B and Pi 400 do not have a dedicated `nRPIBOOT` jumper. Instead, a GPIO on the 40-pin header can be selected, which,
+if pulled to ground during boot, will cause the bootrom to entire `rpiboot` mode.
+**This option is permenantly changes the OTP and cannot be altered afterwards**
+
+
+
+### Pi 500
+Pi 500 requires the QMK keyboard firmware to be updated via `raspi-config` to the latest release to enable `rpiboot` via the power button
+
 ## Running
 
 ### Compute Module 3
@@ -154,7 +166,7 @@ Otherwise, the SPI EEPROM bootloader image will be loaded instead.
 * Hold the power button down
 * Connect the USB-C cable (from the `RPIBOOT` host to the Pi 5)
 
-**Pi 500 requires the QMK keyboard firmware to be updated (via `raspi-config`) to the latest release to enable `rpiboot`.**
+
 
 <a name="extensions"></a>
 ## Provisioning extensions

secure-boot-recovery/README.md

@@ -5,36 +5,6 @@ and recovery.bin files that support secure-boot.
 
 Steps for enabling secure boot:
 
-## Extra steps for Raspberry Pi 4B & Pi 400
-Raspberry Pi 4B and Pi400 do not have a dedicated RPIBOOT jumper so a different GPIO
-must be used to enable RPIBOOT if pulled low. The available GPIOs are `2,4,5,6,7,8`
-since these are high by default.
-
-Pi4 Model B rev 1.3 and older use the BCM2711B0 processor which does not support secure-boot.
-All CM4, CM4S and Pi400 boards use BCM2711C0 which supports secure-boot.
-
-### Step 1 - Erase the EEPROM
-In order to avoid this OTP configuration being accidentally set on Pi 4B / Pi 400
-this option can only be set via RPIBOOT. To force RPIBOOT on a Pi 4B / Pi 400
-erase the SPI EEPROM.
-
-* Use `Raspberry Pi Imager` to flash a bootloader image to a spare SD card.
-* Remove `pieeprom.bin` and `pieeprom.sig` from the SD card image.
-* Add a `config.txt` file to the SD card with the following entries then boot the Pi with this card.
-
-```
-erase_eeprom=1
-uart_2ndstage=1
-```
-
-### Step 2 - Select the nRPIBOOT GPIO
-Edit the `secure-boot-recovery/config.txt` file to specify the GPIO to use for nRPIBOOT. For example:
-```
-program_rpiboot_gpio=6
-```
-
-This can either be programmed in isolation or combined with the steps to program the secure-boot OTP settings.
-
 ## Optional. Specify the private key file in an environment variable.
 Alternatively, specify the path when invoking the helper scripts.
 ```bash