diff --git a/documentation/asciidoc/services/connect/ab-boot-update.adoc b/documentation/asciidoc/services/connect/ab-boot-update.adoc
index c247e24b1..5ebc1e0fd 100644
--- a/documentation/asciidoc/services/connect/ab-boot-update.adoc
+++ b/documentation/asciidoc/services/connect/ab-boot-update.adoc
@@ -10,7 +10,7 @@ Configuring for A/B boot requires being able to physically access the device. Th
 
 Raspberry Pi 5 and later devices that use EEPROM boot can also be configured to use A/B boot update. See xref:../computers/raspberry-pi.adoc#ab-bootloader-updates[A/B bootloader updates].
 
-Use https://github.com/raspberrypi/rpi-image-gen[rpi-image-gen] to create both the A/B boot configuration (`.img` file) and the update artefacts (`.tar.zst` files). Use https://www.raspberrypi.com/software/[Raspberry Pi Imager] to configure the `.img` file and write it to the storage device for transfer to the recipient Raspberry Pi.
+Use https://github.com/raspberrypi/rpi-image-gen[rpi-image-gen] to create both the A/B boot configuration (`.img` file) and the update artefacts (`update.tar.zst` files). Use https://www.raspberrypi.com/software/[Raspberry Pi Imager] to configure the `.img` file and write it to the storage device for transfer to the recipient Raspberry Pi.
 
 ==== Prerequisites
 
@@ -264,7 +264,7 @@ To host the update artefact:
 +
 [source,console]
 ----
-$ python -m http.server 8080 --directory ./work/image-myapp-1.1.0
+$ python -m http.server 8080 --directory ./work/image-myapp
 ----
 
 ===== Step 2: Calculate the SHA-256 checksum of the update file
@@ -273,7 +273,7 @@ $ python -m http.server 8080 --directory ./work/image-myapp-1.1.0
 +
 [source,console]
 ----
-$ sha256sum ./work/image-myapp-1.1.0/update.tar.zst
+$ sha256sum ./work/image-myapp/myapp-update.tar.zst
 ----
 . Copy down the checksum.
 
@@ -315,4 +315,4 @@ The command line returns something like the following, indicating that the `Arte
 ----
 Generated using rpi-image-gen e3828f885c860f15991468883d3b8484b0eaf9d8 on 2025-12-09
 Artefact version: 1.1.0
-----
\ No newline at end of file
+----
diff --git a/documentation/asciidoc/services/connect/remote-update.adoc b/documentation/asciidoc/services/connect/remote-update.adoc
index fc8310738..380ef0465 100644
--- a/documentation/asciidoc/services/connect/remote-update.adoc
+++ b/documentation/asciidoc/services/connect/remote-update.adoc
@@ -23,19 +23,19 @@ Host the artefact anywhere the recipient device can reach it: your own web serve
 
 The location must be accessible to the recipient device, but it doesn't have to be accessible to the Raspberry Pi Connect servers, or to the internet at large. Serving an artefact from another computer on the same local network as the recipient device works well.
 
-Here is an example URI: http://192.168.0.1:8080/path/to/update.tar.zst
+Here is an example URI: http://192.168.0.1:8080/path/to/app.update.tar.zst
 
 It contains the following required information:
 
 * The host IP: 192.168.0.1
 * The port: 8080
-* The path: /path/to/update.tar.zst
+* The path: /path/to/app.update.tar.zst
 
 You also need the artefact's SHA-256 checksum, which Connect passes to the device so that it can check that the artefact hasn't been corrupted or tampered with in transit. `otamaker` prints the checksum when it builds a script artefact; otherwise, calculate it with `sha256sum`:
 
 [source,console]
 ----
-$ sha256sum update.tar.zst
+$ sha256sum app.update.tar.zst
 ----
 
 Copy down the URI and the checksum; you need both in the next section.