3 files changed, 17 insertions, 16 deletions
diff --git a/docs/getting-started/image-workflow-build.md b/docs/getting-started/image-workflow-build.md
index 0e28e25..13f542f 100644
--- a/docs/getting-started/image-workflow-build.md
+++ b/docs/getting-started/image-workflow-build.md
@@ -12,7 +12,7 @@ This section, provides links to topics with instructions needed to create images
 three types of supported platforms and for emulation using Quick EMUlator (QEMU)
 or VirtualBox:
 
-* [Most Intel-based 64-Bit Boards](./machines/intel.html/)
-* [Emulation](./machines/qemu.html/)
-* [R Car Starter Kit Gen3 Board](./machines/renesas.html/)
-* [Raspberry PI 2 or 3](./machines/raspberrypi.html/)
+* [Most Intel-based 64-Bit Boards](./machines/intel.html)
+* [Emulation](./machines/qemu.html)
+* [R Car Starter Kit Gen3 Board](./machines/renesas.html)
+* [Raspberry PI 2 or 3](./machines/raspberrypi.html)
diff --git a/docs/getting-started/image-workflow-intro.md b/docs/getting-started/image-workflow-intro.md
index ad36d01..393a9f5 100644
--- a/docs/getting-started/image-workflow-intro.md
+++ b/docs/getting-started/image-workflow-intro.md
@@ -16,9 +16,9 @@ in the AGL Documentation set.
 Links are provided when a set of steps is required that is documented
 elsewhere.
 
-<center><img src="images/image-developer-workflow.png"></center>
+![](images/image-developer-workflow.png){:: style="margin:auto; display:flex"}
 
-1. Prepare your build host to use use the tools needed to build your image.
+1. Prepare your build host to be able to use the tools needed to build your image.
 
 2. Download the AGL software into a local Git repository on your build host.
 
diff --git a/docs/getting-started/machines/renesas.md b/docs/getting-started/machines/renesas.md
index 7fc8309..8660e20 100644
--- a/docs/getting-started/machines/renesas.md
+++ b/docs/getting-started/machines/renesas.md
@@ -24,16 +24,16 @@ You can find more information on building images from these resources:
 This following list looks a bit dated.
 Do we want to update these PDFs or are they still useful?
 
-* [AGL-Devkit-Build-your-1st-AGL-Application.pdf](http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Devkit-Build-your-1st-AGL-Application.pdf)
+* [AGL-Devkit-Build-your-1st-AGL-Application.pdf](https://iot.bzh/download/public/2016/sdk/AGL-Devkit-Build-your-1st-AGL-Application.pdf)
  Generic guide on how to build various application types (HTML5, native, Qt, QML, …) for AGL.
  This is really about building an application and not the AGL image.
-* [AGL-Devkit-HowTo_bake_a_service.pdf](http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/bsp/AGL_Phase2-Devkit-HowTo_bake_a_service.pdf)
+* [AGL-Devkit-HowTo_bake_a_service.pdf](https://iot.bzh/download/public/2016/bsp/AGL_Phase2-Devkit-HowTo_bake_a_service.pdf)
  Generic guide on how to add a new service in the BSP.
  Goes back to 2015 and uses Yocto 2.x.
  Includes stuff on building an image but looks like the focus is really the service.
-* [AGL-Kickstart-on-Renesas-Porter-Board.pdf](http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Kickstart-on-Renesas-Porter-board.pdf)
+* [AGL-Kickstart-on-Renesas-Porter-Board.pdf](https://iot.bzh/download/public/2016/sdk/AGL-Kickstart-on-Renesas-Porter-board.pdf)
  Guide on how to build an image for the Porter Board using AGL 2.0.
-* [AGL-Devkit-Image-and-SDK-for-Porter.pdf](http://docs.automotivelinux.org/docs/devguides/en/dev/reference/iotbzh2016/sdk/AGL-Devkit-Image-and-SDK-for-porter.pdf)
+* [AGL-Devkit-Image-and-SDK-for-Porter.pdf](https://iot.bzh/download/public/2016/sdk/AGL-Devkit-Image-and-SDK-for-porter.pdf)
  Guide on building an AGL image and SDK for the Porter board.
  Uses Yocto 2.x.
 
@@ -61,7 +61,7 @@ Follow these steps to download the drivers you need:
      4:ZIP_2="R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston2-20170904.zip"
      ```
 
-     The script's output identifies the files you need to download from the page.
+     The script's output identifies the files you need to download from the page and the example above correspond to the Electric Eel AGL revision (v5.0.0). Note that since Flounder AGL revision (v6.0.0), both zip have been renamed.
 
 2. **Find the Download Links:**
 
@@ -139,7 +139,8 @@ Follow these steps to download the drivers you need:
      |:-:|:-:|
      | AGL master  | 3.15.0 |
      | AGL 7.0.0  | 3.9.0 |
-     | AGL 6.0.0 | 3.7.0 |
+     | AGL 6.0.3, 6.0.4  | 3.9.0 |
+     | AGL 6.0.0, 6.0.1, 6.0.2 | 3.7.0 |
      | AGL 5.0.x, 5.1.0| 2.23.1 |
      | AGL 4.0.x |2.19.0 |
 
@@ -390,8 +391,8 @@ Follow these steps to update the firmware:
    You only need to make these updates one time per device.
 
    Follow the procedure found on the
-   [eLinux.org wiki][R-car loader update] to update to at least version 3.02,
-   which is mandatory to run the AGL image.
+   eLinux.org wiki to update to at least version 3.02,
+   which is mandatory to run the AGL image ([R-car loader update](https://elinux.org/R-Car/Boards/Kingfisher#How_to_update_of_Sample_Loader_and_MiniMonitor)).
 
 2. **Update the Firmware Stack:**
 
@@ -402,8 +403,8 @@ Follow these steps to update the firmware:
    As such, they have a firmware stack that is divided across: **ARM Trusted Firmware**, **OP-Tee** and **U-Boot**.
 
    If you are using the Eel (5.0) version or later of the AGL software, you must update
-   the firmware using the **[h3ulcb][R-car h3ulcb firmware update]**
-   or **[m3ulcb][R-car m3ulcb firmware update]** links from the
+   the firmware using the **[h3ulcb][R-car h3ulcb firmware update](http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware)**
+   or **[m3ulcb][R-car m3ulcb firmware update](https://elinux.org/R-Car/Boards/M3SK#Flashing_firmware)** links from the
    [Embedded Linux Wiki](https://www.elinux.org/Main_Page) (i.e. `elinux.org`).
 
    The table in the wiki lists the files you need to flash the firmware.