merging tech review updates

Author: anupras-mohapatra-arm

content/install-guides/arm-toolchains-repository.md

@@ -1,40 +1,32 @@
 ---
-### Title the install tools article with the name of the tool to be installed
-### Include vendor name where appropriate
 title: Arm Toolchains Repository
 
 draft: true
 
-### Optional additional search terms (one per line) to assist in finding the article
 additional_search_terms:
 - Arm Toolchains
 - Arm Toolchain for Linux
 - Arm Performance Libraries
 - Linux
 - HPC
 
-### Estimated completion time in minutes (please use integer multiple of 5)
 minutes_to_complete: 15
 
 test_maintenance: false
 test_images:
   - ubuntu:latest
 
-### Link to official documentation
 official_docs: https://developer.arm.com/tools-and-software
 description: Configure the Arm Toolchains Repository package archive on supported Linux AArch64 distributions to enable installing Arm Toolchains products using the system package manager.
 author: Gary Carroll
 
-### PAGE SETUP
 weight: 1                       # Defines page ordering. Must be 1 for first (or only) page.
 tool_install: true              # Set to true to be listed in main selection page, else false
 multi_install: false            # Set to true if first page of multi-page article, else false
 multitool_install_part: false   # Set to true if a sub-page of a multi-page article, else false
 layout: installtoolsall         # DO NOT MODIFY. Always true for tool install articles
 ---
 
-# Arm Toolchains Repository
-
 The Arm Toolchains Linux repositories provide a native and convenient way to install selected Arm software products on supported Linux hosts using the host operating system package manager.
 
 The repositories are published at [https://developer.arm.com/packages/arm-toolchains/](https://developer.arm.com/packages/arm-toolchains/).
@@ -46,7 +38,7 @@ They are used to distribute Linux packages for Arm Toolchains products, includin
 
 Using the Arm Toolchains Linux repositories allows you to install, upgrade, and manage these products using standard Linux package-management tools such as `apt`, `dnf`, `yum`, and `zypper`.
 
-Note: root permissions are required to install system packages.
+Root or `sudo` permissions are required to install system packages.
 
 {{% notice Repository signing key update July 2026 %}}
 Arm has recently reviewed and strengthened the repository management and publication processes used for the Arm Toolchains Linux repositories.
@@ -60,17 +52,27 @@ Existing installed copies of Arm Toolchain for Linux and Arm Performance Librari
 
 ## Before you begin
 
-You need a supported Linux host with `aarch64` architecture.
+Confirm you are using an Arm Linux system by running:
+
+```bash
+uname -m
+```
 
-You also need the package manager for your Linux distribution:
+The output should be:
+
+```output
+aarch64
+```
+
+The commands in this guide use the native package manager for your distribution:
 
 - `apt` for Ubuntu LTS releases from 22.04
 - `dnf` or `yum` for RHEL 8 or later and Amazon Linux 2023
 - `zypper` for SLES 15 or 16
 
 ## What is the Arm Toolchains repository package?
 
-Arm provides an `arm-toolchains-repository` package for each supported Linux distribution.
+Arm provides an `arm-toolchains-repository` for each supported Linux distribution.
 
 This package configures the Arm Toolchains Linux package repository on your host system.
 
@@ -84,27 +86,34 @@ Install this repository package before you install Arm Toolchain for Linux or Ar
 
 ## Why the signing key matters
 
-Linux package managers use signing keys to verify that repository metadata and packages come from the expected publisher.
+Linux package managers use cryptographic signing keys to verify that repository metadata and packages are authentic and come directly from Arm.
+
+If you are setting up a new system, installing the `arm-toolchains-repository` package automatically configures the current repository signing key for you. No manual key installation or fingerprint verification is required.
 
-For the Arm Toolchains Linux repositories, the signing key is part of the trust model for package installation and upgrades. If your package manager does not have the current Arm Toolchains repository signing key installed, it might refuse to refresh repository metadata or install packages from the repository.
+However, if you are upgrading a system that previously configured the Arm Toolchains Linux repository before July 2026, you must update the repository configuration to use the new key. Otherwise, your package manager may refuse to refresh repository metadata or install packages.
 
-The previous Arm Toolchains repository signing key was replaced in July 2026.
+### Repository signing key fingerprints
 
-The previous key fingerprint was:
+For reference or manual verification, the fingerprints of the previous and current Arm Toolchains signing keys are:
+
+Previous fingerprint:
 
 ```output
 EE37 7ACD D5AD 4AB6 BD79  9B8A B83D 741E 7A05 AF82
 ```
 
-The current key fingerprint is:
+Current fingerprint:
 
 ```output
 A406 5BCE 9386 DD1E 62FD  E03B 8144 CA16 11A0 BD71
 ```
 
-You can display the fingerprint from a downloaded key file with:
+### (Optional) Manually verifying the signing key
+
+If you want to manually verify the signing key, ensure the `gpg` utility (part of GnuPG) is installed on your system, then download the key file and display its fingerprint:
 
 ```bash
+curl -O https://developer.arm.com/packages/arm-toolchains/arm-toolchains.gpg
 gpg --show-keys --fingerprint arm-toolchains.gpg
 ```
 
@@ -149,49 +158,41 @@ The examples below install the repository package directly from [https://develop
 {{< tabpane code=true >}}
   {{< tab header="Ubuntu 24.04" language="bash" >}}
 curl -O https://developer.arm.com/packages/arm-toolchains/ubuntu/pool/arm-toolchains-repository_2-2~noble_all.deb
-
 sudo dpkg -i arm-toolchains-repository_2-2~noble_all.deb
 sudo apt update
   {{< /tab >}}
   {{< tab header="Ubuntu 22.04" language="bash" >}}
 curl -O https://developer.arm.com/packages/arm-toolchains/ubuntu/pool/arm-toolchains-repository_2-2~jammy_all.deb
-
 sudo dpkg -i arm-toolchains-repository_2-2~jammy_all.deb
 sudo apt update
   {{< /tab >}}
   {{< tab header="RHEL 10" language="bash" >}}
 sudo dnf install -y https://developer.arm.com/packages/arm-toolchains/rhel/el10/aarch64/arm-toolchains-repository-2-2.el10.noarch.rpm
-
 sudo dnf clean all
 sudo dnf makecache
   {{< /tab >}}
   {{< tab header="RHEL 9" language="bash" >}}
 sudo dnf install -y https://developer.arm.com/packages/arm-toolchains/rhel/el9/aarch64/arm-toolchains-repository-2-2.el9.noarch.rpm
-
 sudo dnf clean all
 sudo dnf makecache
   {{< /tab >}}
   {{< tab header="RHEL 8" language="bash" >}}
 sudo dnf install -y https://developer.arm.com/packages/arm-toolchains/rhel/el8/aarch64/arm-toolchains-repository-2-2.el8.noarch.rpm
-
 sudo dnf clean all
 sudo dnf makecache
   {{< /tab >}}
   {{< tab header="Amazon Linux 2023" language="bash" >}}
 sudo dnf install -y https://developer.arm.com/packages/arm-toolchains/amazonlinux/al2023/aarch64/arm-toolchains-repository-2-2.al2023.noarch.rpm
-
 sudo dnf clean all
 sudo dnf makecache
   {{< /tab >}}
   {{< tab header="SLES 15" language="bash" >}}
 sudo zypper install -y https://developer.arm.com/packages/arm-toolchains/sles/sles15/aarch64/arm-toolchains-repository-2-2.sles15.noarch.rpm
-
 sudo zypper clean
 sudo zypper refresh
   {{< /tab >}}
   {{< tab header="SLES 16" language="bash" >}}
 sudo zypper install -y https://developer.arm.com/packages/arm-toolchains/sles/sles16/aarch64/arm-toolchains-repository-2-2.sles16.noarch.rpm
-
 sudo zypper clean
 sudo zypper refresh
   {{< /tab >}}
@@ -245,7 +246,6 @@ Install the current Arm Toolchains repository signing key:
 
 ```bash
 curl -O https://developer.arm.com/packages/arm-toolchains/arm-toolchains.gpg
-
 sudo install -D -m 0644 arm-toolchains.gpg \
   /usr/share/keyrings/arm-toolchains-archive-keyring.gpg
 ```
@@ -294,7 +294,6 @@ Install the current Arm Toolchains repository signing key:
 
 ```bash
 curl -O https://developer.arm.com/packages/arm-toolchains/arm-toolchains.gpg
-
 sudo rpm --import arm-toolchains.gpg
 ```
 

content/learning-paths/cross-platform/ai-agent-cpu-orchestration/2-setup.md

@@ -13,17 +13,6 @@ Prepare the following before running the agent: a Serper API key for web search,
 
 These steps are identical on an Apple silicon MacBook, an Arm Linux machine, and an NVIDIA DGX Spark.
 
-### Get a Serper API key
-
-The agent searches the web through [Serper](https://serper.dev/), a Google Search API. The free tier is enough for you to complete the Learning Path.
-
-To get an API key:
-
-1. Go to [serper.dev](https://serper.dev/) and create a free account.
-2. Open your dashboard and copy your API key.
-
-You'll set this key as an environment variable later in this section, so the agent can read it without the key being written into the code.
-
 ### Create a project directory and virtual environment
 
 A virtual environment keeps the agent's dependencies isolated from your system Python, so you always run against the right package versions.
@@ -54,16 +43,21 @@ Install the two packages:
 pip install requests beautifulsoup4
 ```
 
-### Set your Serper API key
+## Set your Serper API key
 
-Export your API key as an environment variable in the same terminal session:
+The agent searches the web through [Serper](https://serper.dev/), a Google Search API. The free tier is enough to complete this Learning Path.
 
-```bash
-export SERPER_API_KEY="your-serper-api-key"
-```
+1. Go to [serper.dev](https://serper.dev/) and create a free account.
+2. After logging in, you'll see the dashboard. On the left, select **API Keys**.
+3. Copy the Default key.
+4. Export your API key as an environment variable in the same terminal session as your virtual environment:
+
+    ```bash
+    export SERPER_API_KEY="your-serper-api-key"
+    ```
 
 {{% notice Tip %}}
-This variable lasts only for the current terminal session. To keep the variable across sessions, add the same line to your shell profile, for example `~/.zshrc` on macOS or `~/.bashrc` on Linux.
+This variable only lasts for the current terminal session. To keep it across sessions, add the same line to your shell profile, for example `~/.zshrc` on macOS or `~/.bashrc` on Linux.
 {{% /notice %}}
 
 ### Download the agent script

content/learning-paths/cross-platform/ai-agent-cpu-orchestration/3-ollama.md

@@ -21,26 +21,33 @@ Running locally has three benefits that matter for an agent:
 
 ## Install and start Ollama
 
-Install [Ollama](https://ollama.com/) and start its server using one of the following options. The server exposes a local API at `http://localhost:11434` that the agent connects to.
+Install [Ollama](https://ollama.com/) and start its server. The server exposes a local API at `http://localhost:11434` that the agent connects to.
+
+1. Install Ollama using one of the following options:
 
 {{< tabpane code=true >}}
-{{< tab header="Homebrew (Recommended)" language="bash">}}
-# Install Ollama
+{{< tab header="Homebrew" language="bash">}}
 brew install ollama
-
-# Start the server as a background service (no terminal to keep open)
-brew services start ollama
 {{< /tab >}}
 {{< tab header="Install script" language="bash">}}
-# Install Ollama
 curl -fsSL https://ollama.com/install.sh | sh
+{{< /tab >}}
+{{< /tabpane >}}
+
+2. Start the Ollama server using the same method you used to install it:
 
-# Start the server (leave this running, and open a second terminal)
+{{< tabpane code=true >}}
+{{< tab header="Homebrew" language="bash">}}
+brew services start ollama
+{{< /tab >}}
+{{< tab header="Install script" language="bash">}}
 ollama serve
 {{< /tab >}}
 {{< /tabpane >}}
 
-With [Homebrew](https://brew.sh/), `brew services` runs Ollama in the background, so you can use the same terminal throughout. With the install script, `ollama serve` runs in the foreground, so keep that terminal open and use a second terminal for the remaining commands.
+With [Homebrew](https://brew.sh/), `brew services` runs Ollama in the background, so you can use the same terminal throughout. To stop it later, run `brew services stop ollama`.
+
+With the install script, `ollama serve` runs in the foreground. Keep that terminal open and use a second terminal for the remaining commands. To stop it later, press **Ctrl+C** in the terminal running `ollama serve`.
 
 ## Pull the Gemma model
 

content/learning-paths/servers-and-cloud-computing/minecraft-on-oci/_index.md

@@ -3,7 +3,7 @@ title: Run a Minecraft server on an Arm-based Oracle Cloud Infrastructure instan
 
 description: Deploy a Minecraft Java Edition server on an Arm-based OCI A1 instance, open port `25565`, and connect from the Minecraft client.
 
-minutes_to_complete: 10
+minutes_to_complete: 30
 
 who_is_this_for: This is an introductory topic for developers who are new to Oracle Cloud Infrastructure (OCI) and want to provision an arm64 instance and run a persistent Minecraft server on it.
 

content/learning-paths/servers-and-cloud-computing/performix-instruction-mix/_index.md

@@ -0,0 +1,68 @@
+---
+title: Profile GPT-2 instruction mix with Arm Performix
+
+description: Learn how to profile GPT-2 inference on Arm Neoverse with the Arm Performix Instruction Mix recipe, identify scalar versus vector execution patterns, and improve throughput with NEON, SVE, and KleidiAI kernels.
+
+minutes_to_complete: 45
+
+who_is_this_for: This is an introductory topic for developers who want to get started using the instruction mix recipe in Arm Performix through a practical example.
+
+learning_objectives: 
+    - Explain how the Instruction Mix recipe combines static disassembly with runtime sampling to show execution behavior
+    - Build and run the GPT-2 inference example on an Arm Linux server
+    - Identify why matrix multiplication dominates runtime and how vectorization changes the instruction mix
+    - Compare throughput and instruction mix across scalar, NEON, SVE, and KleidiAI implementations
+
+prerequisites:
+    - Access to Arm Performix configured with a remote Arm Linux target. For setup, see the [Arm Performix install guide](/install-guides/performix/)
+    - Basic understanding of C++ and compiler optimization
+    - Basic understanding of matrix multiplication
+    - Basic understanding of writing SIMD code with Neon and/or SVE.
+
+author:
+    - Kieran Hejmadi
+    - Oliver Grainge
+
+### Tags
+skilllevels: Introductory
+subjects: Performance and Architecture
+armips:
+    - Neoverse
+tools_software_languages:
+    - Arm Performix
+    - C++
+    - LLM
+    - NEON
+    - SVE
+operatingsystems:
+    - Linux
+further_reading:
+    - resource:
+        title: Arm Performix User Guide
+        link: https://developer.arm.com/documentation/110163/latest
+        type: documentation
+    - resource:
+        title: Find code hotspots with Arm Performix
+        link: /learning-paths/servers-and-cloud-computing/cpu_hotspot_performix/
+        type: learning-path
+    - resource:
+        title: Identify code hotspots using Arm Performix through the Arm MCP Server
+        link: /learning-paths/servers-and-cloud-computing/performix-mcp-agent/
+        type: learning-path
+    - resource:
+        title: Arm MCP Server GitHub Repository
+        link: https://github.com/arm/mcp
+        type: website
+    - resource:
+        title: GPT-2 Example repository
+        link: https://github.com/arm-education/GPT-2-Example
+        type: website
+
+
+
+### FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 1                       # _index.md always has weight of 1 to order correctly
+layout: "learningpathall"       # All files under learning paths have this same wrapper
+learning_path_main_page: "yes"  # This should be surfaced when looking for related content. Only set for _index.md of learning path content.
+---

content/learning-paths/servers-and-cloud-computing/performix-instruction-mix/_next-steps.md

@@ -0,0 +1,8 @@
+---
+# ================================================================================
+#       FIXED, DO NOT MODIFY THIS FILE
+# ================================================================================
+weight: 21                  # The weight controls the order of the pages. _index.md always has weight 1.
+title: "Next Steps"         # Always the same, html page title.
+layout: "learningpathall"   # All files under learning paths have this same wrapper for Hugo processing.
+---