Merge pull request #2688 from ArmDeveloperEcosystem/main

production update

Author: jasonrandrews

.github/copilot-instructions.md

@@ -5383,4 +5383,60 @@ ultraedge
 unclound
 wNdi
 whatsapp
-workdir
+workdir
+Alexandre
+CRI
+ClickHouse's
+EDuJ
+EOL
+ERNIE's
+Expb
+FEXPA
+Grasset
+Idxb
+LOQ
+MEC
+MECID
+MECIDs
+MIMEType
+Martino
+NvLxg
+Nydus
+PASes
+PolicyDeny
+Remb
+Romana
+SLdG
+TCB
+aMWqFmwBgwT
+actix
+ae
+aot
+cdd
+columnalt
+cri
+decrypt
+eade
+empt
+expBits
+exponentials
+jsozZm
+jyco
+keyprovider
+Linux's
+minimax
+modelcontextprotocol
+nter
+nydus
+oMdFIQ
+outputNAME
+poweroff
+qJs
+rBD
+rMDhjcaEM
+remBits
+snapshotter
+unmounting
+vnd
+xqcqqYHrjZ
+ztPjILBCbFEqnVlbvjUpM

.wordlist.txt

@@ -69,7 +69,7 @@ Run the installer(s) and follow on-screen instructions.
 
 ### How do I install Git for version control functionality?
 
-You can download the latest version from [here](https://git-scm.com/).
+You can download the latest version from [git-scm.com](https://git-scm.com/).
 
 ### What about Keil Studio for VS Code?
 

content/install-guides/github-copilot.md

@@ -52,7 +52,7 @@ Streamline CLI tools are supported on the following Arm CPUs:
 
 Use the Arm Sysreport utility to determine whether your system configuration supports hardware-assisted profiling. Follow the instructions in [Get ready for performance analysis with Sysreport][1] to discover how to download and run this utility.
 
-[1]: https://learn.arm.com/learning-paths/servers-and-cloud-computing/sysreport/
+[1]: /learning-paths/servers-and-cloud-computing/sysreport/
 
 The `perf counters` entry in the generated report indicates how many CPU counters are available. The `perf sampling` entry indicates if SPE is available. You will achieve the best profiles in systems with at least 6 available CPU counters and SPE.
 

content/install-guides/stm32_vs.md

@@ -15,7 +15,7 @@ The example has been tested on [AWS EC2](https://aws.amazon.com/ec2/) and an [Am
 
 ## Installation
 
-You need Docker to run Open AD Kit. Refer to the [Docker install guide](https://learn.arm.com/install-guides/docker/) to learn how to install Docker on an Arm platform.
+You need Docker to run Open AD Kit. Refer to the [Docker install guide](/install-guides/docker/) to learn how to install Docker on an Arm platform.
 
 First, verify Docker is installed on your development computer by running:
 

content/install-guides/streamline-cli.md

@@ -17,7 +17,7 @@ In modern vehicles, multiple sensors such as LiDAR, radar, and cameras must cont
 DDS ensures these components share data seamlessly and in real time, both within the vehicle and across infrastructure such as V2X systems, including traffic lights and road sensors.
 
 {{% notice Tip %}}
-To get started with open-source DDS on Arm platforms, see the [Installation Guide for CycloneDDS](https://learn.arm.com/install-guides/cyclonedds).
+To get started with open-source DDS on Arm platforms, see the [Installation Guide for CycloneDDS](/install-guides/cyclonedds).
 {{% /notice %}}
 
 

content/learning-paths/automotive/openadkit1_container/3_setup_openadkit.md

@@ -10,7 +10,7 @@ layout: learningpathall
 
 Now that you’ve explored the concept of a safety island, a dedicated subsystem responsible for executing safety-critical control logic, and learned how DDS (Data Distribution Service) enables real-time, distributed communication, you’ll refactor the original OpenAD Kit architecture into a multi-instance deployment.
 
-The predecessor Learning Path, [Deploy Open AD Kit containerized autonomous driving simulation on Arm Neoverse](http://learn.arm.com/learning-paths/automotive/openadkit1_container/), showed how to  deploying three container components on a single Arm-based instance, to handle:
+The predecessor Learning Path, [Deploy Open AD Kit containerized autonomous driving simulation on Arm Neoverse](/learning-paths/automotive/openadkit1_container/), showed how to  deploying three container components on a single Arm-based instance, to handle:
 - The simulation environment
 - Visualization
 - Planning and control

content/learning-paths/automotive/openadkit2_safetyisolation/2_data_distribution_service.md

@@ -86,7 +86,7 @@ On the Simulation and Visualization node, execute:
 
 Once both machines are running their launch scripts, the Visualizer container exposes a web-accessible interface at: http://6080/vnc.html.
 
-Open this link in your browser to observe the simulation in real time. The demo closely resembles the output in the [previous Learning Path, Deploy Open AD Kit containerized autonomous driving simulation on Arm Neoverse](http://learn.arm.com/learning-paths/automotive/openadkit1_container/4_run_openadkit/). 
+Open this link in your browser to observe the simulation in real time. The demo closely resembles the output in the [previous Learning Path, Deploy Open AD Kit containerized autonomous driving simulation on Arm Neoverse](/learning-paths/automotive/openadkit1_container/4_run_openadkit/). 
 
 ![Distributed OpenAD Kit simulation running on two Arm-based instances with visualizer and simulator coordination over DDS alt-text#center](split_aws_run.gif "Visualizer output from a distributed OpenAD Kit simulation showing ROS 2 modules running across two cloud instances using DDS communication.")
 

content/learning-paths/automotive/openadkit2_safetyisolation/3_container_spliting.md

@@ -164,7 +164,7 @@ Place a `MicroPacFile` in your project directory.
 -   **limits**: Resource limits (memory, cpu)
 -   **mount**: Volume mount points
 -   **network**: Network configuration
--   **createdBy**: maintanier of the application
+-   **createdBy**: maintainer of the application
 -   **description**: description of the application
 
 ### Building the MicroPac