Deploy to production

documentation/asciidoc/accessories/ai-camera/getting-started.adoc

@@ -52,7 +52,7 @@ Once all the system packages are updated and firmware files installed, we can st
 
 The xref:../computers/camera_software.adoc#rpicam-apps[`rpicam-apps` camera applications] include IMX500 object detection and pose estimation stages that can be run in the post-processing pipeline. For more information about the post-processing pipeline, see xref:../computers/camera_software.adoc#post-process-file[the post-processing documentation].
 
-The examples on this page use post-processing JSON files located in `/usr/share/rpicam-assets/`.
+The examples on this page use post-processing JSON files located in `/usr/share/rpi-camera-assets/`.
 
 ==== Object detection
 

documentation/asciidoc/computers/ai/getting-started.adoc

@@ -174,7 +174,7 @@ v4.19::
 To install version 4.19 of Hailo's neural network tooling, run the following commands:
 +
 [source,console]
----
+----
 sudo apt install hailo-tappas-core=3.30.0-1 hailort=4.19.0-3 hailo-dkms=4.19.0-1 python3-hailort=4.19.0-2
 ----
 +

documentation/asciidoc/computers/camera/rpicam_configuration.adoc

@@ -38,7 +38,7 @@ Raspberry Pi OS recognises the following overlays in `/boot/firmware/config.txt`
 
 To use one of these overlays, you must disable automatic camera detection. To disable automatic detection, set `camera_auto_detect=0` in `/boot/firmware/config.txt`. If `config.txt` already contains a line assigning an `camera_auto_detect` value, change the value to `0`. Reboot your Raspberry Pi with `sudo reboot` to load your changes.
 
-If your Raspberry Pi has two camera connectors (Raspberry Pi 5 or one of the Compute Modules, for example), then you can specify which one you are referring to by adding `,cam0` or `,cam1` (don't add any spaces) to the `dtoverlay` that you used from the table above. If you do not add either of these, it will default to checking  camera connector 1 (`cam1`). But note that for official Raspberry Pi camera modules, auto-detection will correctly identify all the cameras connected to your device.
+If your Raspberry Pi has two camera connectors (Raspberry Pi 5 or one of the Compute Modules, for example), then you can specify the use of camera connector 0 by adding `,cam0` to the `dtoverlay` that you used from the table above. If you do not add this, it will default to checking camera connector 1. Note that for official Raspberry Pi camera modules connected to SBCs (not Compute Modules), auto-detection will correctly identify all the cameras connected to your device.
 
 [[tuning-files]]
 ==== Tweak camera behaviour with tuning files

documentation/asciidoc/computers/compute-module/cmio-camera.adoc

@@ -65,19 +65,19 @@ dtparam=cam1_reg
 | directive
 
 | v1 camera
-| `dtoverlay=ov5647,cam1`
+| `dtoverlay=ov5647`
 
 | v2 camera
-| `dtoverlay=imx219,cam1`
+| `dtoverlay=imx219`
 
 | v3 camera
-| `dtoverlay=imx708,cam1`
+| `dtoverlay=imx708`
 
 | HQ camera
-| `dtoverlay=imx477,cam1`
+| `dtoverlay=imx477`
 
 | GS camera
-| `dtoverlay=imx296,cam1`
+| `dtoverlay=imx296`
 |===
 
 . Reboot your Compute Module with `sudo reboot`.

documentation/asciidoc/computers/processors/bcm2712.adoc

@@ -24,3 +24,20 @@ Headline features include:
 ** H264 1080p30 encode (from ISP) ~30–40% CPU
 
 In aggregate, the new features present in BCM2712 deliver a performance uplift of 2-3× over Raspberry Pi 4 for common CPU or I/O-intensive use cases.
+
+=== Vulnerabilities and mitigations
+
+The Cortex-A76 CPU used in the BCM2712 SoC has known vulnerabilites that are all mitigated in Raspberry Pi OS.
+
+To determine the full list of vulnerabilities and the mitigations, you can use the following command line which will list all those in place.
+
+```bash
+$ lscpu | grep Vulnerability | grep -v "Not affected"
+Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
+Vulnerability Spectre v1:             Mitigation; __user pointer sanitization
+Vulnerability Spectre v2:             Mitigation; CSV2, BHB
+```
+
+WARNING: The list above was correct as of April 2025 but may have been superceded. You should use `lscpu` on your Raspberry Pi to get up to date information. This is especially important when using a third-party operating system, as these may not include all the latest mitigations in their Linux kernel builds. The Arm processors used by Raspberry Pi Ltd do not use microcode, so all mitigations are at the kernel level.
+
+The vulnerability information reported by `lscpu` is based on the currently executing kernel's detection scheme. It may not accurately reflect the true vulnerability status of the hardware, especially if the OS lacks recent kernel updates. Further vulnerability information on the CPU vendor advisories can be obtained from https://developer.arm.com/Arm%20Security%20Center/Speculative%20Processor%20Vulnerability referencing the Vendor ID and Model name reported by `lscpu`.

documentation/asciidoc/services/connect/introduction.adoc

@@ -8,6 +8,4 @@ To use Connect, xref:connect.adoc#install-connect[install the Connect software]
 
 Connect uses a secure, encrypted connection. By default, Connect communicates directly between your Raspberry Pi and your browser. However, when Connect can't establish a direct connection between your Raspberry Pi and your browser, we use a relay server. In such cases, Raspberry Pi only retains the metadata required to operate Connect.
 
-Connect is currently in the Beta phase of development.
-
 NOTE: To use Connect, your Raspberry Pi must run https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/[Raspberry Pi OS Bookworm] or later.

documentation/index.json

@@ -247,7 +247,7 @@
                     "subpath": "id.adoc"
                 },
                 {
-                    "title": "Raspberry Pi Connect (Beta)",
+                    "title": "Raspberry Pi Connect",
                     "description": "Connect to your Raspberry Pi from your browser",
                     "image": "full-sized/Connect-BIG.png",
                     "subpath": "connect.adoc"