Update documentation

Signed-off-by: Frederic Marec <frederic.marec@iot.bzh>

4 files changed, 19 insertions, 19 deletions

diff --git a/docs/getting-started-book.yml b/docs/getting-started-book.yml
index 12b4b75..b6a40b9 100644
--- a/docs/getting-started-book.yml
+++ b/docs/getting-started-book.yml
@@ -41,7 +41,7 @@ books:
     - url: "getting-started/machines/renesas.md"
       name: Build for R Car Starter Kit gen3 board
     - url: "getting-started/machines/raspberrypi.md"
-      name: Build for Raspberry PI 2/3
+      name: Build for Raspberry PI 3/4
 -
     id: troubleshooting
     order: 51
diff --git a/docs/getting-started/image-workflow-download-sw.md b/docs/getting-started/image-workflow-download-sw.md
index ae41a34..82c2b5e 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. Guppy 7.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 guppy -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*: