Merge pull request #3084 from ArmDeveloperEcosystem/main

Production update

Author: jasonrandrews

content/install-guides/asct.md

@@ -1,5 +1,5 @@
 ---
-title: Arm System Characterization Tool
+title: Arm System Characterization Tool (ASCT)
 
 additional_search_terms:
 - ASCT

content/install-guides/performix.md

@@ -2,25 +2,25 @@
 title: Arm Performix
 
 additional_search_terms:
-- performix
-- performance
-- profiling
-- analysis
-- neoverse
-- optimization
-- perf
-- top-down
+  - performix
+  - performance
+  - profiling
+  - analysis
+  - neoverse
+  - optimization
+  - perf
+  - top-down
 
 minutes_to_complete: 30
 
 author: Pareena Verma
 
 ### Link to official documentation
-official_docs: https://developer.arm.com/documentation/110163/latest 
+official_docs: https://developer.arm.com/documentation/110163/latest
 
-weight: 1                  
-tool_install: true        
-multi_install: false        
+weight: 1
+tool_install: true
+multi_install: false
 multitool_install_part: false
 layout: installtoolsall
 ---
@@ -47,8 +47,8 @@ Arm Linux target systems running Amazon Linux 2023, Ubuntu 22.04, or Ubuntu
 
 Arm Performix requires different packages depending on your host platform:
 
-* **Windows**: Windows 10 or later (Arm64 or x64 architecture)
-* **macOS**: macOS on Arm64 (Apple Silicon)
+* **Windows**: Windows 10 or later on Arm64 or x64 architecture
+* **macOS**: macOS on Arm64 (Apple Silicon) or x64 architecture
 * **Linux**: Debian-based distribution on Arm64 or x64 architecture
 
 You also need access to an Arm Linux target system for profiling.
@@ -64,12 +64,12 @@ Download the Windows installer package for your architecture from the [Arm Perfo
 Alternatively, download using PowerShell. These commands require PowerShell and do not work in the Windows Command Prompt (CMD):
 
 {{< tabpane code=true >}}
-  {{< tab header="Arm64" >}}
+{{< tab header="Arm64" >}}
 curl -o ArmPerformix-windows-arm64.exe https://artifacts.tools.arm.com/arm-performix/app/latest/windows/arm64/ArmPerformix-windows-arm64.exe
-  {{< /tab >}}
-  {{< tab header="x64" >}}
+{{< /tab >}}
+{{< tab header="x64" >}}
 curl -o ArmPerformix-windows-x64.exe https://artifacts.tools.arm.com/arm-performix/app/latest/windows/x64/ArmPerformix-windows-x64.exe
-  {{< /tab >}}
+{{< /tab >}}
 {{< /tabpane >}}
 
 After downloading the `.exe` file, locate it in your Downloads folder and double-click it to start the installation wizard.
@@ -93,12 +93,12 @@ Download the Linux installer package for your architecture from the [Arm Perform
 Alternatively, download using `wget`:
 
 {{< tabpane code=true >}}
-  {{< tab header="Arm64" >}}
-wget -P $HOME https://artifacts.tools.arm.com/arm-performix/app/latest/linux/arm64/ArmPerformix-linux-arm64.deb 
-  {{< /tab >}}
-  {{< tab header="x64" >}}
-wget -P $HOME https://artifacts.tools.arm.com/arm-performix/app/latest/linux/x64/ArmPerformix-linux-amd64.deb 
-  {{< /tab >}}
+{{< tab header="Arm64" >}}
+wget -P $HOME https://artifacts.tools.arm.com/arm-performix/app/latest/linux/arm64/ArmPerformix-linux-arm64.deb
+{{< /tab >}}
+{{< tab header="x64" >}}
+wget -P $HOME https://artifacts.tools.arm.com/arm-performix/app/latest/linux/x64/ArmPerformix-linux-amd64.deb
+{{< /tab >}}
 {{< /tabpane >}}
 
 After downloading the `.deb` file, navigate to the directory where you downloaded it:
@@ -147,13 +147,18 @@ Arm Performix daemon version: 1.0.0
 
 ### How do I install Arm Performix on macOS?
 
-Download the macOS installer package from the [Arm Performix download page](https://developer.arm.com/servers-and-cloud-computing/arm-performix).
+Download the macOS installer package for your architecture from the [Arm Performix download page](https://developer.arm.com/servers-and-cloud-computing/arm-performix).
 
 Alternatively, download using `curl`:
 
-```bash
+{{< tabpane code=true >}}
+{{< tab header="Arm64" >}}
 curl -Lo ArmPerformix-darwin-arm64.pkg https://artifacts.tools.arm.com/arm-performix/app/latest/darwin/arm64/ArmPerformix-darwin-arm64.pkg
-```
+{{< /tab >}}
+{{< tab header="x64" >}}
+curl -Lo ArmPerformix-darwin-arm64.pkg https://artifacts.tools.arm.com/arm-performix/app/latest/darwin/x64/ArmPerformix-darwin-x64.pkg
+{{< /tab >}}
+{{< /tabpane >}}
 
 After downloading the `.pkg` file, navigate to the directory where you downloaded it and double-click the file to start the installer.
 
@@ -250,9 +255,9 @@ In the **Configure Target** form, provide the following details:
 * **Port**: the SSH port number (default is 22)
 * **User**: the username for SSH connection
 * **SSH Private Key**: choose **Automatically Detect Key** or **Select Key Manually**
-  * For manual selection, enter the path to your private key (usually `~/.ssh/id_rsa` or `~/.ssh/id_ed25519`)
+    * For manual selection, enter the path to your private key (usually `~/.ssh/id_rsa` or `~/.ssh/id_ed25519`)
 * **Host Key Verification**: Choose **Strict** (recommended) or **Ignore**
-  * Strict mode verifies the server identity using your `~/.ssh/known_hosts` file
+    * Strict mode verifies the server identity using your `~/.ssh/known_hosts` file
 
 ![Arm Performix target configuration form displaying input fields including Host with IP address 192.168.1.10, Name field for descriptive target identifier, Port field set to 22, User field for SSH username, SSH Private Key section with radio buttons for Automatically Detect Key and Select Key Manually options, and Host Key Verification dropdown menu set to Strict mode with explanation text about verifying server identity using known_hosts file alt-txt#center](/install-guides/_images/atp-target-config.png "Configure Target form with connection settings")
 
@@ -361,32 +366,32 @@ apx target add '{
 Choose one of the following methods to authenticate with your target:
 
 * **Use an existing SSH key in a non-default location:**
-  
+
   If your private key is not in `~/.ssh/id_rsa` or `~/.ssh/id_ed25519`, specify its path in the target command:
   ```bash
   apx target add user@host:22:/path/to/private_ssh_key
   ```
 
 * **Automatically detect an existing SSH key:**
-  
+
   Arm Performix searches common locations (`~/.ssh/id_rsa`, `~/.ssh/id_ed25519`, etc.) for a usable key:
   ```bash
   apx target add user@host --find-keys
   ```
 
 * **Generate and configure a new SSH key pair using password authentication:**
-  
+
   If your target supports password-based SSH login, Performix can generate a new key pair and configure it automatically:
   ```bash
   apx target add user@host --password
   ```
   This option:
-  - Generates an RSA 4096-bit key pair on your host (without a passphrase)
-  - Authenticates to the target using the password you provide
-  - Adds the public key to the target's `~/.ssh/authorized_keys` file
-  - Records the target's host key in the known hosts list
-  - Stores the private key securely for future connections
-  - Discards the password immediately after use (not stored)
+    - Generates an RSA 4096-bit key pair on your host (without a passphrase)
+    - Authenticates to the target using the password you provide
+    - Adds the public key to the target's `~/.ssh/authorized_keys` file
+    - Records the target's host key in the known hosts list
+    - Stores the private key securely for future connections
+    - Discards the password immediately after use (not stored)
 
 **Host key verification:**
 

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

@@ -19,7 +19,7 @@ In this Learning Path, you will split the simulation and visualization stack fro
 
 These nodes communicate using ROS 2 with DDS as the middleware layer, ensuring low-latency and fault-tolerant data exchange between components.
 
-## Architectural Benefits
+## Architectural benefits
 
 This architecture brings several practical benefits:
 
@@ -31,7 +31,7 @@ This architecture brings several practical benefits:
 
 - **Support for Modular CI/CD Workflows**: with containerized separation, you can build, test, and deploy each module independently, which enables agile development and faster iteration cycles.
 
-![img1 alt-text#center](aws_example.jpg "Split instance example in AWS")
+![Diagram showing OpenAD Kit deployment split across two AWS instances, with simulation and visualization on one instance and planning-control on another, connected via DDS communication#center](aws_example.jpg "Split instance example in AWS")
 
 ## Configure networking for DDS communication
 
@@ -54,7 +54,7 @@ Within the EC2 Security Group settings:
 - Add an inbound rule that allows all traffic from the same Security Group by setting the source to the security group itself.
 - Outbound traffic is typically allowed by default and usually does not require changes.
 
-![img2 alt-text#center](security_group.jpg "AWS Security Group Setting")
+![Screenshot of AWS Security Group configuration showing inbound rule allowing all traffic from the same security group to enable DDS peer discovery between instances#center](security_group.jpg "AWS Security Group Setting")
 
 This configuration allows automatic discovery and peer-to-peer communication between DDS participants across the two instances.
 
@@ -143,7 +143,7 @@ Copy the following configuration into docker/cycloneDDS.xml on both machines, an
 - For more information on CycloneDDS settings, see the [Cyclone DDS Configuration Guide](https://cyclonedds.io/docs/cyclonedds/latest/config/config_file_reference.html#cyclonedds-domain-internal-socketreceivebuffersize).
 {{% /notice %}}
 
-## Update the Docker Compose Configuration for Multi-Host Deployment
+## Update the Docker Compose configuration for multi-host deployment
 
 To support running containers across two separate hosts, you’ll need to modify the docker/docker-compose-2ins.yml file. 
 This includes removing inter-container dependencies and updating the network and environment configuration.
@@ -256,7 +256,7 @@ services:
 
 Before moving to the next step, make sure that `docker-compose-2ins.yml` and `cycloneDDS.xml` are already present on both instances.
 
-## Optimize Network Settings for DDS Communication
+## Optimize network settings for DDS communication
 
 In a distributed DDS setup, `high-frequency UDP traffic` between nodes may lead to  `IP packet fragmentation` or  `buffer overflows`, especially under load. 
 These issues can degrade performance or cause unexpected system behavior.

content/learning-paths/automotive/openadkit2_safetyisolation/4_multiinstance_executing.md

@@ -88,7 +88,7 @@ Once both machines are running their launch scripts, the Visualizer container ex
 
 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.")
+![Animated visualization showing the OpenAD Kit simulation running across two distributed Arm-based instances, with the planning-control module on one node communicating over DDS with the simulator and visualizer on another node, demonstrating real-time autonomous driving scenario execution#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.")
 
 You’ve now run the OpenAD Kit across two nodes with separated control and visualization roles. DDS enabled real-time, peer-to-peer communication between the ROS 2 nodes, supporting synchronized behavior across the planning and simulation components deployed on two separate instances.
 

content/learning-paths/automotive/openadkit2_safetyisolation/_index.md

@@ -1,5 +1,6 @@
 ---
 title: Prototype safety-critical isolation for autonomous driving systems on Neoverse
+description: Learn how to implement functional safety isolation for autonomous driving systems on Arm Neoverse using DDS-based communication, containerized deployment, and ISO 26262 compliance principles.
 
 minutes_to_complete: 60
 

content/learning-paths/automotive/system76-auto/_index.md

@@ -1,6 +1,8 @@
 ---
 title: Develop Arm automotive software on the System76 Thelio Astra
 
+description: Learn how to build and run the Arm Automotive Solutions Software Reference Stack locally on the System76 Thelio Astra desktop using Multipass virtualization and Yocto build tools.
+
 minutes_to_complete: 60
 
 who_is_this_for: This is an introductory topic for automotive developers interested in local development using the System76 Thelio Astra Linux desktop computer. 
@@ -22,6 +24,10 @@ armips:
 operatingsystems:
     - Linux
 tools_software_languages:
+    - Multipass
+    - Yocto
+    - Docker
+    - Git
 
 further_reading:
     - resource:

content/learning-paths/automotive/system76-auto/about.md

@@ -6,7 +6,7 @@ weight: 2
 
 layout: "learningpathall"
 ---
-### About the Thelio Astra
+## About the Thelio Astra
 
 Thelio Astra is an Arm-based desktop computer designed by System76 for autonomous vehicle development and other general-purpose Arm software development.
 

content/learning-paths/automotive/system76-auto/build.md

@@ -31,7 +31,7 @@ Press the space bar and the arrow keys to select the three components shown in t
 - **Safety Island Actuation Demo**.
 - **Baremetal**. 
 
-![configuration #center](configure.png)
+![Kas configuration menu showing three selected options: EULA acceptance, Safety Island Actuation Demo, and Baremetal, with Build button highlighted at bottom#center](configure.png)
 
 {{% notice Note %}}
 To build and run, you must accept the EULA. 

content/learning-paths/automotive/zenacssdebug/_index.md

@@ -1,6 +1,7 @@
 ---
 title: Debug Arm Zena CSS Reference Software Stack with Arm Development Studio
 
+description: Learn how to debug the Arm Zena CSS Reference Software Stack using Arm Development Studio on a Fixed Virtual Platform, covering RSE, Safety Island, and Linux kernel debugging workflows.
 
 minutes_to_complete: 60
 

content/learning-paths/automotive/zenacssdebug/rse.md

@@ -87,5 +87,5 @@ stepi
 Use the `Commands` or `History` pane to see and copy the equivalent debugger commands of the GUI actions.
 {{% /notice %}}
 
-![RSE.launch in Arm Development Studio showing Debugger pane with TF-M symbols loaded and path substitution mapping alt-text#center](debugger_commands.png "RSE Debugger pane with TF-M symbol loading and source path substitution")
+![RSE.launch in Arm Development Studio showing Debugger pane with TF-M symbols loaded and path substitution mapping#center](debugger_commands.png "RSE Debugger pane with TF-M symbol loading and source path substitution")