@@ -73,6 +73,8 @@ NOTE: Newer firmware supports the loading of multiple `ramfs` files. You should
 [[initramfs]]
 === `initramfs`
 
+NOTE: Building and updating `initramfs` is considered an advanced technique that's undertaken only by experienced users. It isn't officially supported by Raspberry Pi and we therefore don't provide instructions for it.
+
 The `initramfs` command specifies both the ramfs filename *and* the memory address to which to load it. It performs the actions of both `ramfsfile` and `ramfsaddr` in one parameter. The address can also be `followkernel` (or `0`) to place it in memory after the kernel image. Example values are: `initramfs initramf.gz 0x00800000` or `initramfs init.gz followkernel`. As with `ramfsfile`, newer firmwares allow the loading of multiple files by comma-separating their names.
 
 NOTE: This option uses different syntax from all the other options, and you should not use the `=` character here.
 
@@ -50,9 +50,11 @@ Text-based housekeeping information containing the date and git commit ID of the
 
 ==== `initramfs*`
 
+NOTE: Building and updating `initramfs` is considered an advanced technique that's undertaken only by experienced users. It isn't officially supported by Raspberry Pi and we therefore don't provide instructions for it.
+
 Contents of the initial ramdisk. This loads a temporary root file system into memory before the real root file system can be mounted.
 
-Raspberry Pi OS _Bookworm_ includes an `initramfs` file by default. To enable the initial ramdisk, configure it in xref:config_txt.adoc[`config.txt`] with the xref:config_txt.adoc#auto_initramfs[`auto_initramfs`] keyword.
+Raspberry Pi OS _Bookworm_  and later include an `initramfs` file by default. To enable the initial ramdisk, configure it in xref:config_txt.adoc[`config.txt`] with the xref:config_txt.adoc#auto_initramfs[`auto_initramfs`] keyword.
 
 Raspberry Pi OS _Trixie_ includes the `auto_initramfs` keyword by default.
 
 
@@ -223,16 +223,29 @@ $ sudo reboot
 
 [TIP]
 ====
-Alternatively, copy the kernel with a different filename (for example, `kernel-myconfig.img`) instead of overwriting the `kernel.img` file. Then, edit `config.txt` in the boot partition to select your kernel:
+Alternatively, copy the kernel with a different filename (for example, `kernel-myconfig.img`) instead of overwriting the `$KERNEL.img` file. Then, edit `config.txt` in the boot partition to select your kernel:
 
 [source,ini]
 ----
 kernel=kernel-myconfig.img
 ----
 
 Combine this approach with a custom `LOCALVERSION` to keep your custom kernel separate from the stock kernel image managed by the system. With this arrangement, you can quickly revert to a stock kernel in the event that your kernel cannot boot.
+
+Raspberry Pi OS Bookworm and later include an `initramfs` by default, enabled by using `auto_initramfs` in `config.txt`.
+
+When `auto_initramfs` is set to `1`, the firmware expects the `initramfs` filename to match the kernel filename by replacing the `kernel` prefix with `initramfs` (and omitting any file extension). For example, `kernel-myconfig.img` looks for `initramfs-myconfig`.
+
+If you don't provide a matching filename, you must specify the ramdisk using an explicit `initramfs` directive without an `=` sign, for example:
+
+[source,ini]
+----
+initramfs <filename> followkernel
+----
 ====
 
+NOTE: Building and updating `initramfs` is considered an advanced technique that's undertaken only by experienced users. It isn't officially supported by Raspberry Pi and we therefore don't provide instructions for it.
+
 === Cross-compile the kernel
 
 First, you will need a suitable Linux cross-compilation host. We tend to use Ubuntu; since Raspberry Pi OS is also a Debian distribution, compilation commands are similar.
@@ -459,15 +472,24 @@ $ sudo umount mnt/root
 
 Finally, connect the boot media to your Raspberry Pi and connect it to power to run your freshly-compiled kernel.
 
-
 [TIP]
 ====
-Alternatively, copy the kernel with a different filename (for example, `kernel-myconfig.img`) instead of overwriting the `kernel.img` file. Then, edit `config.txt` in the boot partition to select your kernel:
+Alternatively, copy the kernel with a different filename (for example, `kernel-myconfig.img`) instead of overwriting the `$KERNEL.img` file. Then, edit `config.txt` in the boot partition to select your kernel:
 
 [source,ini]
 ----
 kernel=kernel-myconfig.img
 ----
 
 Combine this approach with a custom `LOCALVERSION` to keep your custom kernel separate from the stock kernel image managed by the system. With this arrangement, you can quickly revert to a stock kernel in the event that your kernel cannot boot.
-====
+
+Raspberry Pi OS Bookworm and later include an `initramfs` by default, enabled by using `auto_initramfs` in `config.txt`.
+
+When `auto_initramfs` is set to `1`, the firmware expects the `initramfs` filename to match the kernel filename by replacing the `kernel` prefix with `initramfs` (and omitting any file extension). For example, `kernel-myconfig.img` looks for `initramfs-myconfig`.
+
+If you don't provide a matching filename, you must specify the ramdisk using an explicit `initramfs` directive without an `=` sign, for example:
+
+[source,ini]
+----
+initramfs <filename> followkernel
+----
@@ -475,7 +475,9 @@ Default: `""` (not set)
 
 The Raspberry Pi Imager application is configured with a JSON file downloaded at startup. By default, Raspberry Pi Imager uses the JSON at https://downloads.raspberrypi.com/os_list_imagingutility_v4.json.
 
-Set `IMAGER_REPO_URL` in the EEPROM configuration to specify the location of the JSON file to use during a network install with the embedded Raspberry Pi Imager.
+// Set `IMAGER_REPO_URL` in the EEPROM configuration to specify the location of the JSON file to use during a network install with the embedded Raspberry Pi Imager.
+
+NOTE: Using `IMAGER_REPO_URL` to configure a network install with the embedded Raspberry Pi Imager isn't currently supported because of a https://github.com/raspberrypi/rpi-imager/issues/894[known issue].
 
 You can also change the URL of the JSON file used by the Raspberry Pi Imager application to get it to offer your own images by one of the following methods:
 
 
@@ -3,4 +3,5 @@
 MicroPython is a full implementation of the Python 3 programming language that runs directly on embedded hardware like Raspberry Pi Pico. You get an interactive prompt (the REPL) to execute commands immediately through USB Serial, and a built-in filesystem. The Pico port of MicroPython includes modules for accessing low-level chip-specific hardware.
 
 * The https://github.com/micropython/micropython/wiki[MicroPython Wiki]
-* The https://forum.micropython.org/[MicroPython Forums]
+* The https://github.com/orgs/micropython/discussions/[MicroPython Discussions]
+* https://discord.com/invite/RB8HZSAExQ[MicroPython's Discord]