Fixing broken linksoctopus_14.93.0octopus/14.93.014.93.0

I have fixed all the broken links in the documentation except links for
Yocto project and security section.

Bug-AGL: [SPEC-4470]
Signed-off-by: Vinod Ahuja <vahuja@unomaha.edu>
Change-Id: I1c05bf2c3a9365bba0b67077cf51b294352e7943
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/28384
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Tested-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>

8 files changed, 12 insertions, 14 deletions

diff --git a/docs/01_Getting_Started/01_Quickstart/01_Using_Ready_Made_Images.md b/docs/01_Getting_Started/01_Quickstart/01_Using_Ready_Made_Images.md
index eaae38e..bc4da4b 100644
--- a/docs/01_Getting_Started/01_Quickstart/01_Using_Ready_Made_Images.md
+++ b/docs/01_Getting_Started/01_Quickstart/01_Using_Ready_Made_Images.md
@@ -199,14 +199,14 @@ The AGL demo images do require 1920x1080. The instructions below have been adapt
 
 ### 2. BeagleBone Enhanced (BBE)
 
-  1. Download the [compressed prebuilt image](https://download.automotivelinux.org/AGL/snapshots/master/latest/bbe/deploy/images/bbe/agl-demo-platform-crosssdk-bbe.wic.xz).
+  1. Download the [compressed prebuilt image](https://download.automotivelinux.org/AGL/snapshots/master/latest/bbe/deploy/images/bbe/agl-telematics-demo-platform-bbe.wic.xz).
 
   2. Extract the image into the SD card of BeagleBone Enhanced :
 
     ```sh
     $ lsblk
     $ sudo umount <sdcard_device_name>
-    $ xzcat agl-demo-platform-crosssdk-bbe.wic.xz | sudo dd of=<sdcard_device_name> bs=4M
+    $ xzcat agl-telematics-demo-platform-bbe.wic.xz | sudo dd of=<sdcard_device_name> bs=4M
     $ sync
     ```
 
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/02_Flutter_Instrument_Cluster_(qemu-x86).md b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/02_Flutter_Instrument_Cluster_(qemu-x86).md
index 1ab8ec6..330d996 100644
--- a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/02_Flutter_Instrument_Cluster_(qemu-x86).md
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/02_Flutter_Instrument_Cluster_(qemu-x86).md
@@ -115,7 +115,7 @@ root@qemux86-64:~# /usr/sbin/kuksa_vss_init.py
 
 #### **Using `kuksa_viss_client`**
 
-Know more about kuksa_viss_client, [Follow this](https://github.com/eclipse/kuksa.val/tree/master/kuksa_viss_client)
+Know more about kuksa_viss_client, [Follow this](https://github.com/eclipse/kuksa.val/tree/master/)
 
 - Run the kuksa_viss_client
 - Authorize using token
diff --git a/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md b/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md
index 232f41e..2786bf6 100644
--- a/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md
+++ b/docs/04_Developer_Guides/01_Application_Framework/02_Application_Startup.md
@@ -73,7 +73,7 @@ any valid string, it is highly recommended to use the "reverse DNS" convention i
 to avoid potential name collisions and ease D-Bus integration.
 
 The application ID is set in the desktop entry file itself for
-[graphical applications](../3_Creating_a_New_Application/#graphical-applications):
+[graphical applications](/04_Developer_Guides/03_Creating_a_New_Application/#graphical-applications):
 it is the value of the `StartupWMClass` field, which must be identical to the `app-id`
 advertised through the Wayland XDG toplevel protocol. In case this field is missing
 (as is usually the case for non-graphical application), the application ID will be the
diff --git a/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md b/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md
index 1ac45a6..28ba02a 100644
--- a/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md
+++ b/docs/04_Developer_Guides/02_AGL_Layers/02_meta_agl.md
@@ -10,7 +10,7 @@ You use this layer as the minimal core on which to build AGL profiles.
 
 **NOTE:** The `meta-agl` layer does not include a reference UI.
   The reference UI is included as part of the
-  [`meta-agl-demo`](3_meta-agl-demo.md) layer.
+  [`meta-agl-demo`](03_meta_agl_demo.md) layer.
   Furthermore, `meta-agl` does not include additional components, such
   as security, which are part of the
   `meta-agl-extra` layer.
@@ -121,4 +121,3 @@ design:
 * packagegroup-agl-test.bb
 
   Additional tools used in QA tests (for agl-image*-qa).
-
diff --git a/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md b/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md
index c560989..dbfe374 100644
--- a/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md
+++ b/docs/04_Developer_Guides/02_AGL_Layers/03_meta_agl_demo.md
@@ -58,8 +58,7 @@ The `meta-agl-demo` layer has the following base dependencies:
 ### Hardware Dependencies
 
 Aside from the previously listed base dependencies, if you are using a
-[supported Renesas board](../../0_Getting_Started/2_Building_AGL_Image/5_3_RCar_Gen_3.md)
-supported Renesas board, these dependencies exist:
+[supported Renesas board](/01_Getting_Started/02_Building_AGL_Image/09_Building_for_Supported_Renesas_Boards.md), these dependencies exist:
 
 - AGL's `meta-renesas` Layer:
 
@@ -67,7 +66,7 @@ supported Renesas board, these dependencies exist:
 
 ### Feature Dependencies
 
-The `meta-agl-demo` layer has the following AGL [feature](../../0_Getting_Started/2_Building_AGL_Image/3_Initializing_Your_Build_Environment.md#agl-features)
+The `meta-agl-demo` layer has the following AGL [feature](/01_Getting_Started/02_Building_AGL_Image/04_Initializing_Your_Build_Environment/#agl-features)
 dependencies:
 
 - Yocto Project `meta-security` Layer:
@@ -156,4 +155,4 @@ consist of the following:
 
     Because the `packagegroup-agl-demo-qt-examples` is not mandatory for the AGL
     Application Framework and the AGL DEMO, the packagegroup is added to the layer's
-    `local.conf` file only when needed.
\ No newline at end of file
+    `local.conf` file only when needed.
diff --git a/docs/04_Developer_Guides/03_Creating_a_New_Application.md b/docs/04_Developer_Guides/03_Creating_a_New_Application.md
index 3fb7682..014069d 100644
--- a/docs/04_Developer_Guides/03_Creating_a_New_Application.md
+++ b/docs/04_Developer_Guides/03_Creating_a_New_Application.md
@@ -60,7 +60,7 @@ refer to the [graphical applications](#graphical-applications) section for more
 
 # D-Bus activation
 
-Similarly to [services](../2_Creating_a_New_Service/#d-bus-activation), applications can
+Similarly to [services](../02_Creating_a_New_Service/#d-bus-activation), applications can
 also be activated through D-Bus.
 
 Such applications must name their `.desktop` file after the D-Bus name they register. In addition,
diff --git a/docs/06_Component_Documentation/02_agl_compositor.md b/docs/06_Component_Documentation/02_agl_compositor.md
index 0d3a135..c5221cb 100644
--- a/docs/06_Component_Documentation/02_agl_compositor.md
+++ b/docs/06_Component_Documentation/02_agl_compositor.md
@@ -316,7 +316,7 @@ panel/display, without some kind of compositor driving it, the necessity of
 handling input events is an important feature to have, giving the user to
 possibility to manipulate the application/environment as he or she seems fit.
 The compositor loads a plug-in that streams out the buffers to an output
-remotely, with [another plug-in](2_waltham-receiver_waltham-transmitter.md)
+remotely, with [another plug-in](03_waltham_receiver_transmitter.md)
 handling the input events. The events, which are sent back from the display to
 the compositor, are generated with the help of wayland-eque protocol that works
 over the network, called [Waltham](https://github.com/waltham/waltham).
@@ -336,7 +336,7 @@ SMACK label and compares it with the ones statically defined.
 
 In the works, there's a new policy model, called [Role Based
 Arbitration](https://gerrit.automotivelinux.org/gerrit/admin/repos/staging/rba).
-Internally, how it works, should be found at [RBA](3_rba.md).
+Internally, how it works, should be found at [RBA](04_Rule_Based_Arbitrator.md).
 While the other two policies are embedded into the compositor, the RBA policy
 model is an off the-shell policy.  Obviously, vendors and users can hook up
 their own policies, just like RBA did.  These all work towards satisfying
diff --git a/docs/07_How_To_Contribute/08_Adding_Documentation.md b/docs/07_How_To_Contribute/08_Adding_Documentation.md
index 091b520..b879cc0 100644
--- a/docs/07_How_To_Contribute/08_Adding_Documentation.md
+++ b/docs/07_How_To_Contribute/08_Adding_Documentation.md
@@ -5,7 +5,7 @@ title: Adding Documentation
 The [documentation gerrit
 repository](https://gerrit.automotivelinux.org/gerrit/admin/repos/AGL/documentation)
 contains AGL documentation website template and content, rendering is visible at
-[https://automotivegradelinux.readthedocs.io/en/latest/](https://automotivegradelinux.readthedocs.io/en/latest/).
+[https://docs.automotivelinux.org](https://docs.automotivelinux.org).
 The documentation site is hosted on
 [readthedocs](https://readthedocs.org/projects/automotivegradelinux/) and
 corresponding builds are mentioned