Trixie image updates and accessibility changes #4207

katshann-raspberry · 2025-10-07T11:57:00Z

No description provided.

Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v5) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5 to 6. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v5...v6) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

Bumps [actions/stale](https://github.com/actions/stale) from 9 to 10. - [Release notes](https://github.com/actions/stale/releases) - [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md) - [Commits](actions/stale@v9...v10) --- updated-dependencies: - dependency-name: actions/stale dependency-version: '10' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

Bumps [pyyaml](https://github.com/yaml/pyyaml) from 6.0.2 to 6.0.3. - [Release notes](https://github.com/yaml/pyyaml/releases) - [Changelog](https://github.com/yaml/pyyaml/blob/6.0.3/CHANGES) - [Commits](yaml/pyyaml@6.0.2...6.0.3) --- updated-dependencies: - dependency-name: pyyaml dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>

Arm trademark correction

…ml-6.0.3 Bump pyyaml from 6.0.2 to 6.0.3

…evelop/actions/stale-10 Bump actions/stale from 9 to 10

…evelop/actions/setup-python-6 Bump actions/setup-python from 5 to 6

…/checkout-5

…evelop/actions/checkout-5 Bump actions/checkout from 4 to 5

Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>

…dress.adoc Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>

Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>

Trixie followup

Accessibility tweaks

JeuneseRPi · 2025-10-07T11:59:42Z

documentation/asciidoc/accessories/build-hat/preparing-build-hat.adoc

 NOTE: Before starting to work with your Raspberry Pi Build HAT you should xref:../computers/getting-started.adoc#setting-up-your-raspberry-pi[set up] your Raspberry Pi, xref:../computers/getting-started.adoc#installing-the-operating-system[install] the latest version of the operating system using https://www.raspberrypi.com/downloads/[Raspberry Pi Imager].

-Attach 9mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.  
+Attach 9mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.


Suggested change

Attach 9mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.

Attach 9 mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.

JeuneseRPi · 2025-10-07T12:00:01Z

documentation/asciidoc/accessories/build-hat/preparing-build-hat.adoc

 === Set up your Raspberry Pi

-Once the Raspberry Pi has booted, open the Raspberry Pi Configuration tool by clicking on the Raspberry Menu button and then selecting "Preferences" and then "Raspberry Pi Configuration".
+Once the Raspberry Pi has booted, open the Control Centre tool by selecting the Raspberry Menu button and then selecting **Preferences > Control Centre**.


Suggested change

Once the Raspberry Pi has booted, open the Control Centre tool by selecting the Raspberry Menu button and then selecting **Preferences > Control Centre**.

After the Raspberry Pi has booted, open the Control Centre tool by selecting the Raspberry Menu button and then selecting **Preferences > Control Centre**.

JeuneseRPi · 2025-10-07T12:02:23Z

documentation/asciidoc/computers/configuration/raspi-config.adoc

-To open the configuration tool from the desktop GUI, go to **Preferences** > **Raspberry Pi Configuration**.
+To open the configuration tool from the desktop GUI, go to **Preferences** > **Control Centre**.
+
+NOTE: In previous versions of Raspberry Pi OS, the Control Centre application was called Raspberry Pi Configuration.


Suggested change

NOTE: In previous versions of Raspberry Pi OS, the Control Centre application was called Raspberry Pi Configuration.

NOTE: In previous versions of Raspberry Pi OS, the *Control Centre* application was called *Raspberry Pi Configuration*.

JeuneseRPi · 2025-10-07T12:03:14Z

documentation/asciidoc/computers/configuration/screensaver.adoc

+Click the Raspberry Pi button in the menu bar. Navigate to *Preferences* > *Control Centre*.

-image::images/pi-configuration.png[opening the Raspberry Pi Configuration menu from the desktop]
+NOTE: In previous versions of Raspberry Pi OS, the Control Centre application was called Raspberry Pi Configuration.


Suggested change

NOTE: In previous versions of Raspberry Pi OS, the Control Centre application was called Raspberry Pi Configuration.

NOTE: In previous versions of Raspberry Pi OS, the *Control Centre* application was called *Raspberry Pi Configuration*.

JeuneseRPi · 2025-10-07T12:04:29Z

documentation/asciidoc/computers/processors/bcm2711.adoc

 The BCM2711 chip continues to use the heat spreading technology started with the BCM2837B0, which provides better thermal management.

-*Processor:*  Quad-core https://en.wikipedia.org/wiki/ARM_Cortex-A72[Cortex-A72] (ARM v8) 64-bit SoC @ 1.5 GHz.
+*Processor:*  Quad-core https://en.wikipedia.org/wiki/ARM_Cortex-A72[Cortex-A72] (Armv8-A) 64-bit SoC @ 1.5 GHz.


Suggested change

*Processor:* Quad-core https://en.wikipedia.org/wiki/ARM_Cortex-A72[Cortex-A72] (Armv8-A) 64-bit SoC @ 1.5 GHz.

*Processor:* Quad-core https://en.wikipedia.org/wiki/ARM_Cortex-A72[Cortex-A72] (Armv8-A) 64-bit SoC at 1.5 GHz.

JeuneseRPi · 2025-10-07T12:04:50Z

documentation/asciidoc/computers/processors/bcm2712.adoc


 Headline features include:

 * Quad-core Arm Cortex-A76 @ 2.4GHz


Suggested change

* Quad-core Arm Cortex-A76 @ 2.4GHz

* Quad-core Arm Cortex-A76 at 2.4 GHz

JeuneseRPi · 2025-10-07T12:05:10Z

documentation/asciidoc/computers/processors/bcm2712.adoc

 * Quad-core Arm Cortex-A76 @ 2.4GHz
-** ARMv8-A ISA
+** Armv8-A ISA
 ** 64KByte I and D caches


Suggested change

** 64KByte I and D caches

* 64 KB I and D caches

JeuneseRPi · 2025-10-07T12:05:25Z

documentation/asciidoc/computers/processors/bcm2712.adoc

-** ARMv8-A ISA
+** Armv8-A ISA
 ** 64KByte I and D caches
 ** 512KB L2 per core, 2MB shared L3


Suggested change

** 512KB L2 per core, 2MB shared L3

** 512 KB L2 per core, 2 MB shared L3

JeuneseRPi · 2025-10-07T12:05:58Z

documentation/asciidoc/computers/processors/bcm2837.adoc

+This is the Broadcom chip used in the Raspberry Pi 3 Model B, later models of the Raspberry Pi 2 Model B, and the Raspberry Pi Compute Module 3. The underlying architecture of the BCM2837 is identical to the BCM2836. The only significant difference is the replacement of the Armv7 quad core cluster with a quad-core Arm Cortex A53 (Armv8) cluster.

-The ARM cores run at 1.2GHz, making the device about 50% faster than the Raspberry Pi 2. The VideoCore IV runs at 400MHz.
+The Arm cores run at 1.2GHz, making the device about 50% faster than the Raspberry Pi 2. The VideoCore IV runs at 400MHz.


Suggested change

The Arm cores run at 1.2GHz, making the device about 50% faster than the Raspberry Pi 2. The VideoCore IV runs at 400MHz.

The Arm cores run at 1.2 GHz, making the device about 50% faster than the Raspberry Pi 2. The VideoCore IV runs at 400 MHz.

JeuneseRPi · 2025-10-07T12:06:20Z

documentation/asciidoc/computers/processors/bcm2837b0.adoc

+This is the Broadcom chip used in the Raspberry Pi 3 Models A+, B+, and the Raspberry Pi Compute Module 3+. The underlying architecture of the BCM2837B0 is identical to the BCM2837 chip used in other versions of the Raspberry Pi. The Arm core hardware is the same, only the frequency is rated higher.

-The ARM cores are capable of running at up to 1.4GHz, making the 3B+/3A+ about 17% faster than the original Raspberry Pi 3. The VideoCore IV runs at 400MHz. The ARM core is 64-bit, while the VideoCore IV is 32-bit.
+The Arm cores are capable of running at up to 1.4GHz, making the 3B+/3A+ about 17% faster than the original Raspberry Pi 3. The VideoCore IV runs at 400MHz. The Arm core is 64-bit, while the VideoCore IV is 32-bit.


Suggested change

The Arm cores are capable of running at up to 1.4GHz, making the 3B+/3A+ about 17% faster than the original Raspberry Pi 3. The VideoCore IV runs at 400MHz. The Arm core is 64-bit, while the VideoCore IV is 32-bit.

The Arm cores are capable of running at up to 1.4 GHz, making the 3B+/3A+ about 17% faster than the original Raspberry Pi 3. The VideoCore IV runs at 400MHz. The Arm core is 64-bit, while the VideoCore IV is 32-bit.

JeuneseRPi · 2025-10-07T12:07:09Z

documentation/asciidoc/computers/processors/rp3a0.adoc

 == RP3A0

-The Raspberry Pi RP3A0 is our first System-in-Package (SiP) consisting of a Broadcom BCM2710A1 — which is the silicon die packaged inside the Broadcom xref:processors.adoc#bcm2837[BCM2837] chip which is used on the xref:raspberry-pi.adoc#raspberry-pi-3-model-b-2[Raspberry Pi 3] — along with 512MB of DRAM. 
+The Raspberry Pi RP3A0 is our first System-in-Package (SiP) consisting of a Broadcom BCM2710A1 — which is the silicon die packaged inside the Broadcom xref:processors.adoc#bcm2837[BCM2837] chip which is used on the xref:raspberry-pi.adoc#raspberry-pi-3-model-b-2[Raspberry Pi 3] — along with 512MB of DRAM.


Suggested change

The Raspberry Pi RP3A0 is our first System-in-Package (SiP) consisting of a Broadcom BCM2710A1 — which is the silicon die packaged inside the Broadcom xref:processors.adoc#bcm2837[BCM2837] chip which is used on the xref:raspberry-pi.adoc#raspberry-pi-3-model-b-2[Raspberry Pi 3] — along with 512MB of DRAM.

The Raspberry Pi RP3A0 is our first System-in-Package (SiP) consisting of a Broadcom BCM2710A1, which is the silicon die packaged inside the Broadcom xref:processors.adoc#bcm2837[BCM2837] chip which is used on the xref:raspberry-pi.adoc#raspberry-pi-3-model-b-2[Raspberry Pi 3], along with 512 MB of DRAM.

JeuneseRPi · 2025-10-07T12:07:37Z

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

 SD0 is the Broadcom SD card/MMC interface. When the boot ROM within the SoC runs, it always connects SD0 to the built-in microSD card slot. On Compute Modules with an eMMC device, SD0 is connected to that; on the Compute Module Lite SD0 is available on the edge connector and connects to the microSD card slot in the CMIO carrier board. SD1 is the Arasan SD card/MMC interface which is also capable of SDIO. All Raspberry Pi models with built-in wireless LAN use SD1 to connect to the wireless chip via SDIO.

-The default pull resistance on the GPIO lines is 50KΩ, as documented on page 102 of the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[BCM2835 ARM peripherals datasheet]. A pull resistance of 5KΩ is recommended to pull a GPIO line up: this will allow the GPIO to function but not consume too much power.
+The default pull resistance on the GPIO lines is 50KΩ, as documented on page 102 of the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[BCM2835 Arm peripherals datasheet]. A pull resistance of 5KΩ is recommended to pull a GPIO line up: this will allow the GPIO to function but not consume too much power.


Suggested change

The default pull resistance on the GPIO lines is 50KΩ, as documented on page 102 of the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[BCM2835 Arm peripherals datasheet]. A pull resistance of 5KΩ is recommended to pull a GPIO line up: this will allow the GPIO to function but not consume too much power.

The default pull resistance on the GPIO lines is 50 KΩ, as documented on page 102 of the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[BCM2835 Arm peripherals datasheet]. A pull resistance of 5 KΩ is recommended to pull a GPIO line up: this will allow the GPIO to function but not consume too much power.

JeuneseRPi · 2025-10-07T12:09:01Z

documentation/asciidoc/computers/raspberry-pi/frequency-management.adoc

 NOTE: This setting has been removed on 5-series devices and is effectively always mode 3.

-In addition, a more stepped CPU governor is also used to produce finer-grained control of ARM core frequencies, which means the DVFS is more effective. The steps are now 1500MHz, 1000MHz, 750MHz, and 600MHz. These steps can also help when the SoC is being throttled, and mean that throttling all the way back to 600MHz is much less likely, giving an overall increase in fully loaded performance.
+In addition, a more stepped CPU governor is also used to produce finer-grained control of Arm core frequencies, which means the DVFS is more effective. The steps are now 1500MHz, 1000MHz, 750MHz, and 600MHz. These steps can also help when the SoC is being throttled, and mean that throttling all the way back to 600MHz is much less likely, giving an overall increase in fully loaded performance.


Suggested change

In addition, a more stepped CPU governor is also used to produce finer-grained control of Arm core frequencies, which means the DVFS is more effective. The steps are now 1500MHz, 1000MHz, 750MHz, and 600MHz. These steps can also help when the SoC is being throttled, and mean that throttling all the way back to 600MHz is much less likely, giving an overall increase in fully loaded performance.

In addition, a more stepped CPU governor is also used to produce finer-grained control of Arm core frequencies, which means the DVFS is more effective. The steps are now 1500 MHz, 1000 MHz, 750 MHz, and 600 MHz. These steps can also help when the SoC is being throttled, and mean that throttling all the way back to 600 MHz is much less likely, giving an overall increase in fully loaded performance.

JeuneseRPi · 2025-10-07T12:10:04Z

documentation/asciidoc/computers/remote-access/vnc.adoc

 image::images/vnc-tigervnc-username-password.png[alt="Entering a username and password to authenticate via TigerVNC",width="60%"]
 --
-. Click the "OK" button to authenticate with the VNC server. If your credentials are correct, TigerVNC should open a window containing the desktop corresponding to your account on the Raspberry Pi. You should be able to move your mouse and keyboard to input text and interact with the desktop.
+. Click the "OK" button to authenticate with the VNC server. If your credentials are correct, TigerVNC should open a window containing the desktop corresponding to your account on the Raspberry Pi. You should be able to use your mouse and keyboard to interact with the desktop and input text.


Suggested change

. Click the "OK" button to authenticate with the VNC server. If your credentials are correct, TigerVNC should open a window containing the desktop corresponding to your account on the Raspberry Pi. You should be able to use your mouse and keyboard to interact with the desktop and input text.

. Select "OK" to authenticate with the VNC server. If your credentials are correct, TigerVNC should open a window containing the desktop corresponding to your account on the Raspberry Pi. You should be able to use your mouse and keyboard to interact with the desktop and input text.

lurch · 2025-10-07T12:10:38Z

@JeuneseRPi I think the general practice is that changes are only made on the develop branch, and master then only accepts merges from the develop branch.

JeuneseRPi · 2025-10-07T12:11:57Z

documentation/asciidoc/microcontrollers/debug-probe/swd-connection.adoc

 === Standalone program upload

-Once you have built a binary: 
+Once you have built a binary:


Suggested change

Once you have built a binary:

After you've built a binary:

JeuneseRPi · 2025-10-07T12:14:26Z

@JeuneseRPi I think the general practice is that changes are only made on the develop branch, and master then only accepts merges from the develop branch.

I was sent this to review by @katshann-raspberry. Just discussed this with her now.

dependabot bot and others added 29 commits August 12, 2025 06:46

Start updating Arm trademark.

cb3629b

Update Arm trademarks

8b64bf1

Update for correct instruction set name

d10cc1c

Merge pull request #4202 from raspberrypi/arm-arm

25e04c1

Arm trademark correction

Merge pull request #4199 from raspberrypi/dependabot/pip/develop/pyya…

95a1233

…ml-6.0.3 Bump pyyaml from 6.0.2 to 6.0.3

Merge pull request #4176 from raspberrypi/dependabot/github_actions/d…

efaeeda

…evelop/actions/stale-10 Bump actions/stale from 9 to 10

Merge pull request #4175 from raspberrypi/dependabot/github_actions/d…

9481079

…evelop/actions/setup-python-6 Bump actions/setup-python from 5 to 6

Merge branch 'develop' into dependabot/github_actions/develop/actions…

71a2965

…/checkout-5

Merge pull request #4153 from raspberrypi/dependabot/github_actions/d…

4d43c3f

…evelop/actions/checkout-5 Bump actions/checkout from 4 to 5

Update a couple of images

cd3a172

Update some screenshots and related words

d20c54e

Crop one image

a81ce28

Fix broken link

8172f87

Update documentation/asciidoc/computers/os/updating.adoc

0c63b16

Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>

Update documentation/asciidoc/computers/remote-access/find-your-ip-ad…

ee89a7f

…dress.adoc Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>

Update documentation/asciidoc/computers/remote-access/vnc.adoc

cef2f3b

Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>

Update documentation/asciidoc/computers/software-sources.adoc

e1a6b95

Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>

Add two more image changes

382a85d

Updates from Andrew review!

0853827

Some quick accessibility wins

6e4c577

Accessibility tweak

f1a6166

Update nav header to h2. CSS tweak to retain size.

12bcd32

Further CSS tweaks

93c3553

Merge pull request #4204 from raspberrypi/trixie-followup

81eebfd

Trixie followup

Merge pull request #4206 from raspberrypi/accessibility-tweaks

8ac282a

Accessibility tweaks

katshann-raspberry requested a review from JeuneseRPi October 7, 2025 11:57

JeuneseRPi reviewed Oct 7, 2025

View reviewed changes

katshann-raspberry merged commit 8d5f016 into master Oct 7, 2025
1 check passed

JeuneseRPi reviewed Oct 7, 2025

View reviewed changes

	Attach 9mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.
	Attach 9 mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.

	Once the Raspberry Pi has booted, open the Control Centre tool by selecting the Raspberry Menu button and then selecting Preferences > Control Centre.
	After the Raspberry Pi has booted, open the Control Centre tool by selecting the Raspberry Menu button and then selecting Preferences > Control Centre.

	NOTE: In previous versions of Raspberry Pi OS, the Control Centre application was called Raspberry Pi Configuration.
	NOTE: In previous versions of Raspberry Pi OS, the Control Centre application was called Raspberry Pi Configuration.

	Processor: Quad-core https://en.wikipedia.org/wiki/ARM_Cortex-A72[Cortex-A72] (Armv8-A) 64-bit SoC @ 1.5 GHz.
	Processor: Quad-core https://en.wikipedia.org/wiki/ARM_Cortex-A72[Cortex-A72] (Armv8-A) 64-bit SoC at 1.5 GHz.


		Headline features include:

		* Quad-core Arm Cortex-A76 @ 2.4GHz

	* Quad-core Arm Cortex-A76 @ 2.4GHz
	* Quad-core Arm Cortex-A76 at 2.4 GHz

	** 512KB L2 per core, 2MB shared L3
	** 512 KB L2 per core, 2 MB shared L3

	The Arm cores run at 1.2GHz, making the device about 50% faster than the Raspberry Pi 2. The VideoCore IV runs at 400MHz.
	The Arm cores run at 1.2 GHz, making the device about 50% faster than the Raspberry Pi 2. The VideoCore IV runs at 400 MHz.

	The Arm cores are capable of running at up to 1.4GHz, making the 3B+/3A+ about 17% faster than the original Raspberry Pi 3. The VideoCore IV runs at 400MHz. The Arm core is 64-bit, while the VideoCore IV is 32-bit.
	The Arm cores are capable of running at up to 1.4 GHz, making the 3B+/3A+ about 17% faster than the original Raspberry Pi 3. The VideoCore IV runs at 400MHz. The Arm core is 64-bit, while the VideoCore IV is 32-bit.

	The Raspberry Pi RP3A0 is our first System-in-Package (SiP) consisting of a Broadcom BCM2710A1 — which is the silicon die packaged inside the Broadcom xref:processors.adoc#bcm2837[BCM2837] chip which is used on the xref:raspberry-pi.adoc#raspberry-pi-3-model-b-2[Raspberry Pi 3] — along with 512MB of DRAM.
	The Raspberry Pi RP3A0 is our first System-in-Package (SiP) consisting of a Broadcom BCM2710A1, which is the silicon die packaged inside the Broadcom xref:processors.adoc#bcm2837[BCM2837] chip which is used on the xref:raspberry-pi.adoc#raspberry-pi-3-model-b-2[Raspberry Pi 3], along with 512 MB of DRAM.

	The default pull resistance on the GPIO lines is 50KΩ, as documented on page 102 of the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[BCM2835 Arm peripherals datasheet]. A pull resistance of 5KΩ is recommended to pull a GPIO line up: this will allow the GPIO to function but not consume too much power.
	The default pull resistance on the GPIO lines is 50 KΩ, as documented on page 102 of the https://datasheets.raspberrypi.com/bcm2835/bcm2835-peripherals.pdf[BCM2835 Arm peripherals datasheet]. A pull resistance of 5 KΩ is recommended to pull a GPIO line up: this will allow the GPIO to function but not consume too much power.

	. Click the "OK" button to authenticate with the VNC server. If your credentials are correct, TigerVNC should open a window containing the desktop corresponding to your account on the Raspberry Pi. You should be able to use your mouse and keyboard to interact with the desktop and input text.
	. Select "OK" to authenticate with the VNC server. If your credentials are correct, TigerVNC should open a window containing the desktop corresponding to your account on the Raspberry Pi. You should be able to use your mouse and keyboard to interact with the desktop and input text.

Trixie image updates and accessibility changes #4207

Trixie image updates and accessibility changes #4207

Uh oh!

Conversation

katshann-raspberry commented Oct 7, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JeuneseRPi Oct 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JeuneseRPi Oct 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

lurch commented Oct 7, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JeuneseRPi commented Oct 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

JeuneseRPi Oct 7, 2025 •

edited

Loading

JeuneseRPi Oct 7, 2025 •

edited

Loading