Batch update for Super Salmon M3salmon_18.94.0salmon_18.93.0salmon/18.94.0salmon/18.93.018.94.018.93.0salmon

Update the documentation after branching for Milestone 3.

Bug-AGL: SPEC-5333
Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Change-Id: I04aa470eb53ed937e893445b4b029e24a7b8d12b
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/30759

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/06_Component_Documentation/11_Unified_HMI.md b/docs/06_Component_Documentation/11_Unified_HMI.md
index 2b054b0..0a4f20d 100644
--- a/docs/06_Component_Documentation/11_Unified_HMI.md
+++ b/docs/06_Component_Documentation/11_Unified_HMI.md
@@ -60,11 +60,11 @@ Json files need to be created correctly for your execution environment.
 
 ## How to Build  
 
-Follow the [AGL documentation](https://docs.automotivelinux.org/en/master/#01_Getting_Started/02_Building_AGL_Image/01_Build_Process_Overview/) for the build process, and set up the "[Initializing Your Build Environment](https://docs.automotivelinux.org/en/master/#01_Getting_Started/02_Building_AGL_Image/04_Initializing_Your_Build_Environment/)" section as described below to enable the AGL feature 'agl-uhmi'. 
+Follow the [AGL documentation](https://docs.automotivelinux.org/en/salmon/#01_Getting_Started/02_Building_AGL_Image/01_Build_Process_Overview/) for the build process, and set up the "[Initializing Your Build Environment](https://docs.automotivelinux.org/en/salmon/#01_Getting_Started/02_Building_AGL_Image/04_Initializing_Your_Build_Environment/)" section as described below to enable the AGL feature 'agl-uhmi'. 
 
 For example:
 ```
-$ cd $AGL_TOP/master
+$ cd $AGL_TOP/salmon
 $ source ./meta-agl/scripts/aglsetup.sh -m qemux86-64 -b qemux86-64 agl-demo agl-devel agl-uhmi
 ```
 
@@ -88,9 +88,9 @@ Replace the `<image_name>` with the appropriate values you want. We have confirm
 ## How to setup and boot
 
 For Environment setup instructions for each platform, refer to the following links in the AGL Documentation:
-[Building for x86(Emulation and Hardware)](https://docs.automotivelinux.org/en/master/#01_Getting_Started/02_Building_AGL_Image/06_Building_the_AGL_Image/02_Building_for_x86_%28Emulation_and_Hardware%29/)
-[Building for Raspberry Pi 4](https://docs.automotivelinux.org/en/master/#01_Getting_Started/02_Building_AGL_Image/06_Building_the_AGL_Image/03_Building_for_Raspberry_Pi_4/)
-[Building for Supported Renesas Boards](https://docs.automotivelinux.org/en/master/#01_Getting_Started/02_Building_AGL_Image/06_Building_the_AGL_Image/04_Building_for_Supported_Renesas_Boards/)
+[Building for x86(Emulation and Hardware)](https://docs.automotivelinux.org/en/salmon/#01_Getting_Started/02_Building_AGL_Image/06_Building_the_AGL_Image/02_Building_for_x86_%28Emulation_and_Hardware%29/)
+[Building for Raspberry Pi 4](https://docs.automotivelinux.org/en/salmon/#01_Getting_Started/02_Building_AGL_Image/06_Building_the_AGL_Image/03_Building_for_Raspberry_Pi_4/)
+[Building for Supported Renesas Boards](https://docs.automotivelinux.org/en/salmon/#01_Getting_Started/02_Building_AGL_Image/06_Building_the_AGL_Image/04_Building_for_Supported_Renesas_Boards/)
 
 For Raspberry Pi 4 and Supported Renesas Boards, refer to the above URL for boot methods.
 For x86 emulation (qemu), network bridge is required to enable communication with other devices when using RVGPU.