diff --git a/README.md b/README.md
index 364a235..746c6b9 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ This repository contains the scripts and pre-compiled binaries used to create th
 For bootloader support the best place to start is the Raspberry Pi [General Users forum](https://www.raspberrypi.org/forums/viewforum.php?f=63) or for discussion of beta releases try the [Advanced Users forum](https://www.raspberrypi.org/forums/viewforum.php?f=29&sid=9bbc277968ad953e77749b255d0ce3a2)
 
 # Rescue image
-If the Raspberry Pi4 is not booting, then it's very unlikely that the EEPROM is corrupted. If you think it has an invalid image or you want to revert to the factory setting, then download the rescue image from the Raspberry Pi [downloads page](https://www.raspberrypi.org/downloads/)
+If the Raspberry Pi4 is not booting, then it's very unlikely that the EEPROM is corrupted. The first thing that you should check is that the OS image was correctly installed using the Raspberry Pi Imager which is available on the [downloads page](https://www.raspberrypi.org/downloads/). If that doesn't work or you wish to revert EEPROM configuration changes to factory defaults then you can also create an EEPROM recovery SD card image using the Raspberry Pi Imager.
 
 # Bootloader documentation
 * [The boot folder](https://www.raspberrypi.org/documentation/configuration/boot_folder.md)
@@ -21,7 +21,7 @@ Bootloader bugs are especially difficult to describe because there's no display.
 * Wireshark trace for network boot. Filtering for DHCP and TFTP protocols or by mac-address for the Pi4 is fine.
 
 # BETA versions of the bootloader
-If you want to try the BETA version of the bootloader then we recommend that you always try this with a spare sd-card and comfortable with using the rescue image. For debugging you may find a USB serial cable useful.
+If you want to try the BETA version of the bootloader then we recommend that you always try this with a spare sd-card and are comfortable with using the rescue image. For debugging you may find a USB serial cable useful.
 
-Beta features are always documented [here](https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/raspberry_pi4_network_boot_beta.md) first. Once the configuration has stabalised then the [Bootloader configuration](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md) will be updated, however, there's normally a bit of a delay in order to allow official documentation to be reviewed.
+Beta features are always documented [here](https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md) first. Once the configuration has stabalised then the [Bootloader configuration](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md) will be updated, however, there's normally a bit of a delay in order to allow official documentation to be reviewed.
 
diff --git a/firmware/release-notes.md b/firmware/release-notes.md
index 785b0a2..2c0006a 100644
--- a/firmware/release-notes.md
+++ b/firmware/release-notes.md
@@ -1,5 +1,10 @@
 # Raspberry Pi4 bootloader EEPROM release notes
 
+## 2020-04-07 Promote 2020-03-19 beta firmware to stable.
+    * No major bugs reported. Promote this to stable as a step
+      towards getting HDMI diagnostics into the default firmware
+      via a critical update.
+
 ## 2020-03-19 Add 2020-03-19 beta firmware
     * Minor mods for manufacture test.
 
diff --git a/firmware/stable/pieeprom-2020-03-19.bin b/firmware/stable/pieeprom-2020-03-19.bin
new file mode 100644
index 0000000..6b13ad0
Binary files /dev/null and b/firmware/stable/pieeprom-2020-03-19.bin differ
diff --git a/firmware/stable/recovery.bin b/firmware/stable/recovery.bin
index c69c191..8a1e66a 100644
Binary files a/firmware/stable/recovery.bin and b/firmware/stable/recovery.bin differ