Apply little birdie suggestions

documentation/asciidoc/computers/raspberry-pi/boot-eeprom.adoc

@@ -2,9 +2,9 @@
 
 The following Raspberry Pi models use an EEPROM to boot the system:
 
-* Flagship models since 4
-* Compute Module models since 4 (including Compute Module 4S)
-* Keyboard models since 400
+* Flagship models since Raspberry Pi 4
+* Compute Module models since CM4 (including CM4S)
+* Keyboard models since Pi 400
 
 All other models of Raspberry Pi computer use the `bootcode.bin` file located in the boot filesystem.
 
@@ -19,12 +19,11 @@ If an error occurs during boot, then an xref:configuration.adoc#led-warning-flas
 
 There are multiple ways to update the bootloader of your Raspberry Pi.
 
-==== Flagship models since 4; Compute Modules since 5; Keyboard models since 400
+==== Flagship models since Raspberry Pi 4; Compute Modules since CM5; Keyboard models since Pi 400
 
 Raspberry Pi OS automatically updates the bootloader for important bug fixes. To manually update the bootloader or change the boot order, use xref:configuration.adoc#raspi-config[raspi-config].
 
-NOTE: Compute Module 4 and Compute Module 4S do not support automatic bootloader updates because the bootrom cannot load the `recovery.bin` file from eMMC.
-The recommended update mechanism is `rpiboot` or via `flashrom` - see `rpi-eeprom-update -h` for more information.
+NOTE: Compute Module 4 and Compute Module 4S do not support automatic bootloader updates because the bootrom cannot load the `recovery.bin` file from eMMC. The recommended update mechanism is `rpiboot` or via `flashrom` - see `rpi-eeprom-update -h` for more information.
 
 [[imager]]
 ==== Use Raspberry Pi Imager to update the bootloader

documentation/asciidoc/computers/raspberry-pi/eeprom-bootloader.adoc

@@ -47,7 +47,7 @@ Default: `115200`
 
 If `1` then `sudo halt` will run in a lower power mode until either GPIO3 or GLOBAL_EN are shorted to ground.
 
-This setting is not relevant on Flagship models since 5, Compute Modules since 5, and Keyboard models since 500 because the xref:raspberry-pi.adoc#power-button[dedicated power button] may always be used to wake from `HALT` or `STANDBY`.
+This setting is not relevant on Flagship models since Raspberry Pi 5, Compute Modules since CM5, and Keyboard models since Pi 500 because the xref:raspberry-pi.adoc#power-button[dedicated power button] may always be used to wake from `HALT` or `STANDBY`.
 
 Default: `1`
 
@@ -60,7 +60,7 @@ Raspberry Pi 400 has a dedicated power button which operates even if the process
 
 On Raspberry Pi 5 this places the PMIC in `STANDBY` mode where all outputs are switched off. There is no need to set `WAKE_ON_GPIO` and pressing the xref:raspberry-pi.adoc#power-button[dedicated power button] will boot the device.
 
-Default: `1` on Compute Modules since 5 and Keyboard models since 400; otherwise `0`
+Default: `1` on Compute Modules since CM5 and Keyboard models since Pi 400; otherwise `0`
 
 [[BOOT_ORDER]]
 ==== `BOOT_ORDER`
@@ -398,7 +398,7 @@ This setting is ignored and network install is disabled if `DISABLE_HDMI=1` is s
 
 In order to detect the keyboard, network install must initialise the USB controller and enumerate devices. This increases boot time by approximately 1 second so it may be advantageous to disable network install in some embedded applications.
 
-Default: `1` on Flagship models since 4 and Keyboard models since 400; `0` on Compute Modules since 4 (including Compute Module 4S).
+Default: `1` on Flagship models since Raspberry Pi 4 and Keyboard models since Pi 400; `0` on Compute Modules since CM4 (including CM4S).
 
 [[NET_INSTALL_AT_POWER_ON]]
 ==== `NET_INSTALL_AT_POWER_ON`