GitHub Windows Arm runner LP

Author: pareenaverma

content/learning-paths/laptops-and-desktops/gh-arm-runners-win/_images/actions.png

@@ -37,22 +37,35 @@ This GitHub Actions workflow [`msbuild.yml`](https://github.com/odincodeshen/Spi
 
 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.
-  **Job Definition**: A single job named build is defined. It runs on the GitHub Arm-hosted Windows runner (`windows-11-arm`) as shown:
+
+   **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:
+
 ```console
 jobs:
   build:
     runs-on: windows-11-arm
 ```
-  **Checkout Repository**: Uses the `actions/checkout@v4` action to fetch the code.
-  **Add MSBuild to PATH**: Adds MSBuild tools for the build process using `microsoft/[email protected]`.
-  **Restore Dependencies**: Runs `nuget restore` to restore NuGet packages required by the solution.
-  **Create Download Directory**: Creates a directory to store downloaded files and verifies the Python version.
-  **Download ARM Performance Libraries**: Downloads the Windows installer for ARM Performance Libraries (APL) and verifies the downloaded files.
-  **Install ARM Performance Libraries**: Installs the downloaded ARM Performance Libraries using `msiexec.exe` with a quiet mode and logs the process.
-  **Check Installation Success**: Verifies the success of the APL installation by checking the exit code and logs.
-  **Build the Solution**: Runs MSBuild to build the solution with the specified configuration (Debug) and platform (ARM64).
-  **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.
+   **Checkout Repository**: Uses the `actions/checkout@v4` action to fetch the code.
+
+   **Add MSBuild to PATH**: Adds MSBuild tools for the build process using `microsoft/[email protected]`.
+
+   **Restore Dependencies**: Runs `nuget restore` to restore NuGet packages required by the solution.
+
+   **Create Download Directory**: Creates a directory to store downloaded files and verifies the Python version.
+
+   **Download ARM Performance Libraries**: Downloads the Windows installer for ARM Performance Libraries (APL) and verifies the downloaded files. 
+
+   **Install ARM Performance Libraries**: Installs the downloaded ARM Performance Libraries using `msiexec.exe` with a quiet mode and logs the process.
+
+   **Check Installation Success**: Verifies the success of the APL installation by checking the exit code and logs.
+
+   **Build the Solution**: Runs MSBuild to build the solution with the specified configuration (Debug) and platform (ARM64).
+
+   **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. 
+![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.

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

@@ -14,7 +14,7 @@ Runners are the machines that execute jobs in a GitHub Actions workflow. An Arm-
 
 Arm-hosted runners are available for public repositories at no cost, subject to [standard usage limits](https://docs.github.com/en/actions/administering-github-actions/usage-limits-billing-and-administration#usage-limits). 
 
-### How to Use GitHub Arm-hosted Windows Runners
+### 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:
 
@@ -51,7 +51,7 @@ Select the size of the large runner you need and and click `Save`.
 
 ![specifications #center](_images/size.png)
 
-The `Capacity` section includes the maximum concurrency, which is the number of jobs to run at the same time. Specify at least two for this Learning Path.
+The `Capacity` section includes the maximum concurrency, which is the number of jobs to run at the same time.
 
 You can also set the runner group for this runner. The runner group controls the settings for this runner. Pay attention to the runner group as you may need to return to the runner group settings if any configuration changes are needed.