Content development

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/github-on-arm/_index.md

@@ -50,7 +50,7 @@ further_reading:
       link: https://github.blog/news-insights/product-news/arm64-on-github-actions-powering-faster-more-efficient-build-systems/
       type: website
 
-    - resource:
+  - resource:
         title: GCP Quickstart Guide to Create a virtual machine
         link: https://cloud.google.com/compute/docs/instances/create-start-instance
         type: website

content/learning-paths/servers-and-cloud-computing/github-on-arm/background.md

@@ -8,11 +8,11 @@ layout: "learningpathall"
 
 ## Google Axion C4A series
 
-The Google Axion C4A series is a family of Arm-based virtual machines built on Google’s custom Axion CPU, which is based on Arm Neoverse-V2 cores. Designed for high-performance and energy-efficient computing, these virtual machines offer strong performance ideal for modern cloud workloads such as CI/CD pipelines, microservices, media processing, and general-purpose applications.
+The Google Axion C4A series is a family of Arm-based virtual machines (VMs) built on Google’s custom Axion CPU, which is based on Arm Neoverse-V2 cores. Designed for high-performance and energy-efficient computing, these virtual machines offer strong performance ideal for modern cloud workloads such as CI/CD pipelines, microservices, media processing, and general-purpose applications.
 
-The C4A series provides offer a cost-effective virtual machine while leveraging the scalability and performance benefits of the Arm architecture in Google Cloud.
+The C4A series provides cost-effective VMs while leveraging the scalability and performance benefits of the Arm architecture on Google Cloud.
 
-To learn more about Google Axion, refer to the blog [Introducing Google Axion Processors, our new Arm-based CPUs](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu).
+Learn more in Google’s announcement: [Introducing Google Axion processors, our new Arm-based CPUs](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu).
 
 ## GitHub Actions and CI/CD
 
@@ -24,4 +24,4 @@ A key feature of GitHub Actions is [self-hosted runners](https://docs.github.com
 - Private network access, allowing secure interaction with internal services or databases.
 - Faster execution, especially for resource-intensive workflows, by using dedicated or high-performance machines.
 
-Self-hosted runners provide more control, flexibility, and cost-efficiency—making them ideal for advanced CI/CD pipelines and platform-specific testing.
+Self-hosted runners give you more control, flexibility, and cost efficiency - ideal for advanced CI/CD pipelines and platform-specific testing.

content/learning-paths/servers-and-cloud-computing/github-on-arm/instance.md

@@ -8,26 +8,28 @@ layout: learningpathall
 
 ## Introduction
 
-This section walks you through creating **Google Axion C4A Arm virtual machine** on GCP with the **c4a-standard-4 (4 vCPUs, 16 GB Memory)** machine type, using the **Google Cloud Console**.
+This section walks you through creating a **Google Axion C4A Arm virtual machine** on Google Cloud with the **c4a-standard-4 (4 vCPUs, 16 GB memory)** machine type using the **Google Cloud Console**. You will use this VM later as the host for a GitHub Actions self-hosted runner.
 
-If you haven't got a Google Cloud account, you can follow the Learning Path on [Getting Started with Google Cloud Platform](https://learn.arm.com/learning-paths/servers-and-cloud-computing/csp/google/) to get started.
+If you don't have a Google Cloud account, see the Learning Path [Getting started with Google Cloud Platform](https://learn.arm.com/learning-paths/servers-and-cloud-computing/csp/google/).
 
-### Create an Arm-based Virtual Machine (C4A)
+### Create an Arm-based virtual machine (C4A)
 
-To create a virtual machine based on the C4A Arm architecture:
-1. Open the [Google Cloud Console](https://console.cloud.google.com/).
-2. Navigate to the card **Compute Engine** and click on **Create Instance**.
-3. Under the **Machine Configuration**:
-      - Fill in basic details like **Instance Name**, **Region**, and **Zone**.
-      - Choose the **Series** as `C4A`.
-      - Select a machine type such as `c4a-standard-4`.
-![Instance Screenshot](./images/select-instance.png)
-4. Under the **OS and Storage**, click on **Change**, pick **Ubuntu** as the Operating System with **Ubuntu 24.04 LTS Minimal** as the Version. Make sure you pick the version of image for Arm.
-5. Under **Networking**, enable **Allow HTTP traffic** to test workloads like NGINX later.
-6. Click on **Create**, and the instance will launch.
+Follow these steps in the Google Cloud Console:
+
+- Open the [Google Cloud Console](https://console.cloud.google.com/).
+- Go to **Navigation menu ▸ Compute Engine ▸ VM instances**, then select **Create instance**.
+- Under **Machine configuration**:
+  - Enter **Instance name**, **Region**, and **Zone**.
+  - Set **Series** to `C4A`.
+  - Choose a machine type such as `c4a-standard-4`.
+- Under **OS and storage**, select **Change**, pick **Ubuntu** as the operating system, and choose **Ubuntu 24.04 LTS Minimal**. Make sure you select the Arm image variant.
+- Under **Networking**, enable **Allow HTTP traffic** so you can test workloads like NGINX later.
+- Select **Create** to launch the instance.
+
+![Google Cloud Console page showing C4A VM creation with c4a-standard-4 selected](./images/select-instance.png "Create a C4A VM in the Google Cloud Console")
 
 {{% notice Important %}}
-You should not enable the **Allow HTTP traffic** permanently, since this poses a security risk. For the long-term, you should only allow traffic from the IP address you use to connect to the instance.
+Do not leave **Allow HTTP traffic** enabled permanently. For long-term use, allow traffic only from the IP addresses you use to connect to the instance.
 {{% /notice %}}
 
-You can access the Google Cloud Console by clicking the **SSH** button in the instance overview. Use this command line interface (CLI) to run the commands in the remainder of this Learning Path.
+Access the VM from the instance list by selecting **SSH** in the instance overview. Use this command line interface (CLI) to run the commands in the remainder of this Learning Path.