6 files changed, 24 insertions, 24 deletions
diff --git a/docs/getting-started/app-workflow-image.md b/docs/getting-started/app-workflow-image.md
index e64fd5f..12c9cfb 100644
--- a/docs/getting-started/app-workflow-image.md
+++ b/docs/getting-started/app-workflow-image.md
@@ -63,7 +63,7 @@ Go to the [AGL Download Website](https://download.automotivelinux.org/AGL/releas
 site and follow these links:
 
 ```
-flounder -> 6.0.0 -> qemuarm64 -> deploy -> images -> qemuarm64
+halibut -> 8.0.0 -> qemuarm64 -> deploy -> images -> qemuarm64
 ```
 
 From the list, you could download the ``Image-qemuarm64.bin`` image file.
diff --git a/docs/getting-started/app-workflow-sdk.md b/docs/getting-started/app-workflow-sdk.md
index fba4c7a..6de2670 100644
--- a/docs/getting-started/app-workflow-sdk.md
+++ b/docs/getting-started/app-workflow-sdk.md
@@ -18,11 +18,11 @@ For a look at the SDK installers for supported boards, go to the
 From there, you can explore to find the SDK installer you want to download.
 As an example, consider using a pre-built SDK to develop applications suited for a 64-bit
 ARM-based board that you want to emulate using QEMU.
-Furthermore, you are using the 6.0.0 "Flounder" release of the AGL software.
+Furthermore, you are using the 8.0.0 "Halibut" release of the AGL software.
 Follow these links:
 
 ```
-flounder -> 6.0.0 -> qemuarm64 -> deploy -> sdk
+halibut -> 8.0.0 -> qemuarm64 -> deploy -> sdk
 ```
 
 From the list, you download the ``*.sh`` file, which is an installation script for the SDK.
@@ -31,7 +31,7 @@ Running the SDK installer script installs the SDK onto your build host.
 SDK installation scripts have long names that reflect the platform specifics.
 For example, the following file installs the SDK given the specifics earlier:
 
-``poky-agl-glibc-x86_64-agl-demo-platform-crosssdk-armv7vehf-neon-vfpv4-toolchain-6.0.0.sh``
+``poky-agl-glibc-x86_64-agl-demo-platform-crosssdk-aarch64-toolchain-8.0.0.sh``
 
 **NOTE:** If you want to know more about SDK installer file naming, which is a result of
 BitBake and the Yocto Project, see the
@@ -60,5 +60,5 @@ Assuming your top-level workspace is ``~/workspace_agl``, here is an example loc
 and SDK installer file:
 
 ```
-~/workspace_agl/build/tmp/deploy/sdk/poky-agl-glibc-x86_64-core-image-minimal-cortexa15hf-neon-toolchain-3.0.0+snapshot.sh
+~/workspace_agl/build/tmp/deploy/sdk/poky-agl-glibc-x86_64-agl-demo-platform-crosssdk-aarch64-toolchain-8.0.0.sh
 ```
diff --git a/docs/getting-started/image-workflow-download-sw.md b/docs/getting-started/image-workflow-download-sw.md
index ae41a34..0548056 100644
--- a/docs/getting-started/image-workflow-download-sw.md
+++ b/docs/getting-started/image-workflow-download-sw.md
@@ -45,12 +45,12 @@ The remainder of this section provides steps on how to download the AGL source f
      Using the latest stable release gives you a solid snapshot of the
      latest know release.
      The release is static, tested, and known to work.
-     To download the latest stable release branch (i.e. Flounder 6.0), use
+     To download the latest stable release branch (i.e. Halibut 8.0), use
      the following commands:
 
      ```bash
      $ cd $AGL_TOP
-     $ repo init -b flounder -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
+     $ repo init -b halibut -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
      $ repo sync
      ```
 
diff --git a/docs/getting-started/machines/intel.md b/docs/getting-started/machines/intel.md
index 3658408..4b7e3e1 100644
--- a/docs/getting-started/machines/intel.md
+++ b/docs/getting-started/machines/intel.md
@@ -44,7 +44,7 @@ specific options when you run the script:
 ```bash
 $ source meta-agl/scripts/aglsetup.sh \
     -m intel-corei7-64 \
-    agl-devel agl-demo agl-appfw-smack agl-netboot agl-audio-4a-framework
+    agl-devel agl-demo agl-appfw-smack agl-netboot agl-pipewire
 ```
 
 The "-m" option specifies the "intel-corei7-64" machine.
diff --git a/docs/getting-started/machines/raspberrypi.md b/docs/getting-started/machines/raspberrypi.md
index 76e3929..732d311 100644
--- a/docs/getting-started/machines/raspberrypi.md
+++ b/docs/getting-started/machines/raspberrypi.md
@@ -1,17 +1,17 @@
-# Building for Raspberry PI 2 or 3
+# Building for Raspberry PI 3 or 4
 
 The
 [Raspberry PI](https://www.raspberrypi.org/help/what-%20is-a-raspberry-pi/) is a small
 computer that is ideal for learning computing and computer languages.
 The AGL Project supports building images for the
-[Raspberry PI 2](https://www.raspberrypi.org/products/raspberry-pi-2-model-b/) and the
-[Raspberry PI 3](https://www.raspberrypi.org/products/raspberry-pi-3-model-a-plus/) boards.
+[Raspberry PI 3](https://www.raspberrypi.org/products/raspberry-pi-3-model-a-plus/) and the
+[Raspberry PI 4](https://www.raspberrypi.org/products/raspberry-pi-4-model-b/) boards.
 Each of these boards comes in a variety of models.
 See the
 [Raspberry PI Product Page](https://www.raspberrypi.org/products/) for more information.
 
 This section describes the steps you need to take to build the
-AGL demo image for both the Raspberry PI 2 and 3 boards.
+AGL demo image for both the Raspberry PI 3 and 4 boards.
 
 ## 1. Making Sure Your Build Environment is Correct
 
@@ -25,18 +25,18 @@ specific options when you run the script.
 Use the following commands to initialize your build environment.
 In each case, the "-m" option specifies the machine and the
 list of AGL features used with script are appropriate for development of
-the AGL demo image suited for either Raspberry PI 2 or 3:
+the AGL demo image suited for either Raspberry PI 3 or 4:
 
-**Raspberry PI 2**:
+**Raspberry PI 3**:
 
 ```bash
-$ source meta-agl/scripts/aglsetup.sh -m raspberrypi2 agl-demo agl-netboot agl-appfw-smack
+$ source meta-agl/scripts/aglsetup.sh -m raspberrypi3 agl-demo agl-netboot agl-appfw-smack
 ```
 
-**Raspberry PI 3**:
+**Raspberry PI 4**:
 
 ```bash
-$ source meta-agl/scripts/aglsetup.sh -m raspberrypi3 agl-demo agl-netboot agl-appfw-smack
+$ source meta-agl/scripts/aglsetup.sh -m raspberrypi4 agl-demo agl-netboot agl-appfw-smack
 ```
 
 ## 2. Configuring the Build to Include Packages Under a Commercial License
@@ -95,13 +95,13 @@ $ bitbake agl-demo-platform
 ```
 
 By default, the build process puts the resulting image in the Build Directory.
-Here is example for the Raspberry PI 3 board:
+Here is example for the Raspberry PI 4 board:
 
 ```
-<build_directory>/tmp/deploy/images/raspberrypi3/agl-demo-platform-raspberrypi3.wic.xz
+<build_directory>/tmp/deploy/images/raspberrypi4/agl-demo-platform-raspberrypi4.wic.xz
 ```
 
-If you build for the Raspberry PI 2 board, the location uses "raspberrypi2" in the path.
+If you build for the Raspberry PI 3 board, the location uses "raspberrypi3" in the path.
 
 ## 4. Deploying the AGL Demo Image
 
@@ -109,7 +109,7 @@ Deploying the AGL demo image consists of copying the image on a MicroSD card,
 plugging the card into the Raspberry PI board, and then booting the board.
 
 Follow these steps to copy the image to a MicroSD card and boot
-the image on the Raspberry PI 2 or 3 board:
+the image on the Raspberry PI 3 or 4 board:
 
 1. Plug your MicroSD card into your Build Host (i.e. the system that has your build output).
 
@@ -162,8 +162,8 @@ the image on the Raspberry PI 2 or 3 board:
 3. Now that you know the device name, unmount the device and use the
    `xzcat` command to copy the image to the MicroSD card.
 
-   **NOTE:** For Raspberry PI 2, the image is at `build/tmp/deploy/images/raspberrypi2/agl-demo-platform-raspberrypi2.wic.xz`.
-   For Raspberry PI 3, the image is at `build/tmp/deploy/images/raspberrypi3/agl-demo-platform-raspberrypi3.wic.xz`.
+   **NOTE:** For Raspberry PI 3, the image is at `build/tmp/deploy/images/raspberrypi3/agl-demo-platform-raspberrypi3.wic.xz`.
+   For Raspberry PI 4, the image is at `build/tmp/deploy/images/raspberrypi4/agl-demo-platform-raspberrypi4.wic.xz`.
 
    Be sure you are root, provide the actual device name for *sdcard_device_name*, and the actual
    image name for *image_name*:
diff --git a/docs/getting-started/machines/renesas.md b/docs/getting-started/machines/renesas.md
index 855156d..b121ef6 100644
--- a/docs/getting-started/machines/renesas.md
+++ b/docs/getting-started/machines/renesas.md
@@ -100,7 +100,7 @@ Follow these steps to download the drivers you need:
    You can use the following command:
 
    ```bash
-   chmod a+4 $XDG_DOWNLOAD_DIR/*.zip
+   chmod a+r $XDG_DOWNLOAD_DIR/*.zip
    ```
 
 6. **Check to be Sure the Files are Downloaded and Have the Correct Rights:**