Tech review of GitHub Arm-hosted runners.

Author: jasonrandrews

content/learning-paths/laptops-and-desktops/gh-arm-runners-win/_index.md

@@ -1,6 +1,10 @@
 ---
 title: Automate Windows on Arm Builds with GitHub Arm-hosted Runners
 
+draft: true
+cascade:
+    draft: true
+
 minutes_to_complete: 20
 
 who_is_this_for: This is an introductory tutorial for software developers interested in automating Windows application builds on Arm architecture using GitHub Actions.
@@ -11,14 +15,14 @@ learning_objectives:
     - Automate the build process of Windows applications using GitHub Actions.
 
 prerequisites:
-    - A GitHub account
-    - Basic knowledge of GitHub Actions
+    - A GitHub account. 
+    - Basic knowledge of GitHub Actions.
 
 author: 
     - Pareena Verma
 
 ### Tags
-skilllevels: Introducory
+skilllevels: Introductory
 subjects: CI-CD
 armips:
     - Cortex-A

content/learning-paths/laptops-and-desktops/gh-arm-runners-win/automate-win-app.md

@@ -15,7 +15,7 @@ A basic overview of the application is provided here but for details on building
 The source code for the application that renders a rotating 3D cube to perform the calculations using different programming options is provided in this GitHub repository. 
 
 ```console
-https://github.com/odincodeshen/SpinTheCubeInGDI.git
+https://github.com/arm/SpinTheCubeInGDI
 ```
 
 The application implements a spinning cube and consists of four key components:
@@ -26,21 +26,21 @@ The application implements a spinning cube and consists of four key components:
 
 The code has two options to calculate the rotation:
 
-1. Multithreading: the application utilizes multithreading to improve performance by distributing the rotation calculations across multiple threads.
-2. Arm Performance Libraries: the application utilizes optimized math library functions for the rotation calculations.
+1. Multithreading: the application uses multithreading to improve performance by distributing the rotation calculations across multiple threads.
+2. Arm Performance Libraries: the application uses optimized math library functions for the rotation calculations.
 
-You will learn how to automate the build process for this application by using GitHub Actions that leverages the Arm-hosted Windows runners.
+You will learn how to automate the build process for this application by using GitHub Actions with Arm-hosted Windows runners.
 
 ### Automate the Build Process
 
-This GitHub Actions workflow [`msbuild.yml`](https://github.com/odincodeshen/SpinTheCubeInGDI/blob/main/.github/workflows/msbuild.yml) that automates the build process for this project using MSBuild for Windows on Arm is included in this repository.
+The [GitHub Actions workflow `msbuild.yml`](https://github.com/arm/SpinTheCubeInGDI/blob/main/.github/workflows/msbuild.yml) that automates the build process using MSBuild for Windows on Arm is included in the repository.
 
 Below is an explanation of the steps in the workflow:
 
 
-   **Trigger Events**: The workflow runs when there is a push or pull_request event on the main branch.
+   **Trigger Events**: The workflow runs when there is a push or pull request event on the main branch.
 
-   **Job Definition**: A single job named build is defined. It runs on the GitHub Arm-hosted Windows runner (`windows-11-arm`) as shown:
+   **Job Definition**: A single job named `build` is defined. It runs on the GitHub Arm-hosted Windows runner (`windows-11-arm`) as shown:
 
 ```console
 jobs:
@@ -65,7 +65,17 @@ jobs:
 
    **Upload Build Artifact**: Uploads the built executable as an artifact using `actions/upload-artifact@v4`.
 
-This workflow automates the process of dependency management, environment setup, building your Windows on Arm project, and storing the final artifact all using GitHub Arm-hosted runner. You can view the `Actions` logs on the repository for each step. 
+This workflow automates the process of dependency management, environment setup, building the project, and storing the final artifact all using a GitHub Arm-hosted Windows runner. 
+
+### Fork the repository and run the workflow
+
+To run the workflow, you can fork the repository and run the workflow in your GitHub account.
+
+To fork the repository, go to the repository page on GitHub and click the `Fork` button in the top right corner. This will create a copy of the repository under your own GitHub account. 
+
+You can then run the workflow in your forked repository by navigating to the `Actions` tab and selecting the MSBuild workflow, then clicking `Run workflow`.
+
+You can view the `Actions` logs in the repository for each step. 
 ![action #center](_images/actions.png)
 
-You have successfully built your Windows application and uploaded the application as an artifact of your workflow using the GitHub Arm-hosted Windows runner.
+You have learned how to build a Windows application and upload the result as an artifact of your workflow using the GitHub Arm-hosted Windows runner.

content/learning-paths/laptops-and-desktops/gh-arm-runners-win/introduction.md

@@ -6,7 +6,7 @@ weight: 2
 ### FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
-GitHub Arm-hosted runners for Windows are now available in public preview, providing a powerful and efficient way to build, test and deploy your Windows applications on Arm without the need for virtualization. These runners come with a Windows 11 Desktop image, equipped with many tools to get started with your workflows. 
+GitHub Arm-hosted runners for Windows are now available in public preview, providing a powerful and efficient way to build, test, and deploy your Windows applications on Arm without the need for virtualization. These runners come with a Windows 11 Desktop image, equipped with many tools to get started with your workflows. 
 
 ### What are GitHub Arm-hosted Runners?
 
@@ -16,17 +16,22 @@ Arm-hosted runners are available for public repositories at no cost, subject to
 
 ### How to use GitHub Arm-hosted Windows Runners?
 
-To leverage the GitHub Windows Arm64 hosted runners, you will need to use the following label in your public repository workflow runs:
+To leverage the GitHub Windows Arm64 hosted runners, you need to use the following label in your public repository workflow runs:
 
 ```yaml
 runs-on: windows-11-arm
 ```
 
-Please note that this label will not work in private repositories, the workflow will fail if you add it. 
+{{% notice Note %}}
+This label will not work in private repositories, the workflow will fail if you use it. 
+{{% /notice %}}
 
-Two types of GitHub-hosted runners are available; standard runners, and larger runners. Larger runners are differentiated from standard runners because users can control the amount of RAM, the number of CPUs, and configure the allocated disk space. You can also use the Windows 11 Desktop Arm Image with larger runners. To use this image on large runners, you will need to create a new runner.
 
-### How can I create an GitHub Arm-hosted Windows large runner?
+### What types of GitHub-hosted runners are available?
+
+Two types of GitHub-hosted runners are available; standard runners and larger runners. Larger runners are differentiated from standard runners because you can control the amount of RAM, the number of CPUs, and configure the allocated disk space. You can also use the Windows 11 Desktop Arm Image with larger runners. To use this image on larger runners, you will need to create a new runner.
+
+### How can I create an GitHub Arm-hosted Windows larger runner?
 
 Arm-hosted runners are created at the organization level.
 
@@ -36,7 +41,6 @@ On the `Runners` page, select the `New runner` drop-down on the top right, and t
 
 ![new-runner #center](_images/new-runner.png)
 
-
 Specify a name for the runner, this is the `runs-on` field in your workflows so make the name clear for others who use it.
 
 Choose Windows ARM64 for the platform and click `Save`.
@@ -47,7 +51,7 @@ Specify the operating system image for the runner, select `Microsoft Windows 11
 
 ![image #center](_images/win_image.png)
 
-Select the size of the large runner you need and and click `Save`.
+Select the size of the larger runner you need and click `Save`.
 
 ![specifications #center](_images/size.png)
 
@@ -59,17 +63,18 @@ You can also set the runner group for this runner. The runner group controls the
 
 Finally, click `Create runner`.
 
-Your new Arm-hosted runner Windows large runner is ready to use. You will need to remember the runner name for use in your workflows with the `runs-on` label. 
+Your new Arm-hosted Windows larger runner is ready to use. Remember the runner name so you can use it in your workflows with the `runs-on` label. 
+
+### How do I check the server hardware used by the Arm-hosted Windows Runners?
 
-### Check the server hardware used by the Arm-hosted Windows Runners
 The Arm-hosted runners are powered by Microsoft Azure Cobalt 100 processors, based on the Arm Neoverse N2, with 4 vCPUs and Armv9-A features, including Scalable Vector Extension 2 (SVE2).
 
 The output from running the `wmic` command on the Arm-hosted runner is below.
 
 ![Arm-hosted runner info #center](_images/cpuinfo.png)
 
 
-### Check Installed Software on the Arm-hosted Windows Runners
+### How can I find the software installed on the Arm-hosted Windows Runners?
 
 To find out more about the software installed on the Arm-hosted runners, visit the [GitHub Actions Partner Images repository](https://github.com/actions/partner-runner-images/). Check the [image documentation](https://github.com/actions/partner-runner-images/blob/main/images/arm-windows-11-image.md) for a list of software packages installed on the Windows 11 by Arm Limited image. You can also use this repository to report issues or request additional software.
 

content/learning-paths/laptops-and-desktops/windows_armpl/_index.md

@@ -23,6 +23,7 @@ tools_software_languages:
     - Visual Studio
     - C#
     - .NET
+    - Arm Performance Libraries
 operatingsystems:
     - Windows