Refine content for Buildkite on Google Axion: update titles, enhance clarity, and improve instructions across multiple documents.

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/buildkite-gcp/_index.md

@@ -1,22 +1,22 @@
 ---
-title: Build multi-architecture Docker images with Buildkite on Google Axion
+title: Create multi-architecture Docker images with Buildkite on Google Axion
 
 minutes_to_complete: 40
 
-who_is_this_for: This is an introductory topic for developers learning to build and run multi-architecture Docker images with Buildkite on Arm-based Google Cloud C4A virtual machines powered by Google Axion processors.
+who_is_this_for: This is an introductory topic for developers who want to build and run multi-architecture Docker images with Buildkite on Arm-based Google Cloud C4A virtual machines (VM) powered by Google Axion processors.
 
 learning_objectives:
-- Provision an Arm-based virtual machine on Google Cloud running SUSE Linux Enterprise Server or Ubuntu
+- Provision an Arm-based VM on Google Cloud running either SUSE Linux Enterprise Server or Ubuntu
 - Install and configure Docker, Docker Buildx, and the Buildkite agent
 - Write a Dockerfile to containerize a simple Flask-based Python application
 - Configure a Buildkite pipeline to build a multi-architecture Docker image and push it to Docker Hub
-- Run the application to ensure it works as expected
+- Start the application and verify that it runs correctly
 
 prerequisites:
-  - A [Google Cloud Platform (GCP)](https://cloud.google.com/free?utm_source=google&hl=en) account with billing enabled
-  - Basic knowledge of Linux system administration such as creating users, installing packages, and managing services
-  - Familiarity with Docker and container concepts
-  - A GitHub account to host your application repository
+  - A [Google Cloud Platform (GCP) account](https://cloud.google.com/free?utm_source=google&hl=en) with billing enabled
+  - Basic Linux system administration skills, including how to create users, install packages, and manage services
+  - Familiarity with [Docker](https://docs.docker.com/get-started/) and container concepts
+  - A [GitHub account](https://github.com/join) to host your application repository
 
 author: Jason Andrews
 

content/learning-paths/servers-and-cloud-computing/buildkite-gcp/background.md

@@ -1,20 +1,20 @@
 ---
-title: Get started with Buildkite on Google Axion C4A instances
+title: Explore Buildkite on Google Axion C4A instances
 
 weight: 2
 layout: "learningpathall"
 ---
 
-## Google Axion C4A instances on Google Cloud
+## Google Axion C4A Arm VMs for efficient cloud workloads
 
 Google Axion C4A is a family of Arm-based virtual machines powered by Google's custom Axion CPU, which is built on Arm Neoverse V2 cores. Designed for high performance and energy efficiency, these VMs are well-suited for modern cloud workloads such as CI/CD pipelines, microservices, media processing, and general-purpose applications.
 
 The C4A series can provide a cost-efficient alternative to x86 VMs while leveraging the scalability and performance characteristics of the Arm architecture on Google Cloud.
 
-For further information, see the Google 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 this Google blog [Introducing Google Axion Processors, our new Arm-based CPUs](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu).
 
 ## Buildkite for CI/CD on Arm
 
-Buildkite is a flexible and scalable continuous integration and delivery (CI/CD) platform that enables you to run pipelines on your own infrastructure. By deploying Buildkite agents on Google Axion C4A VMs, you can take advantage of Arm's performance and cost efficiency to build, test, and deploy applications, including multi-architecture Docker images.
+Buildkite is a flexible and scalable continuous integration and delivery (CI/CD) platform that enables you to run pipelines on your own infrastructure. By deploying Buildkite agents on Google Axion C4A VMs, you can take advantage of Arm's performance and cost efficiency to build, test, and deploy applications, including multi-architecture Docker images. Buildkite integrates seamlessly with version control systems such as GitHub and supports advanced workflows for cloud migration, multi-arch builds, and testing microservices. 
 
-Buildkite integrates seamlessly with version control systems such as GitHub and supports advanced workflows for cloud migration, multi-arch builds, and testing microservices. Learn more in the [Buildkite documentation](https://buildkite.com/docs).
+To get started, review the [Buildkite documentation](https://buildkite.com/docs) for setup instructions, pipeline configuration, and agent management.

content/learning-paths/servers-and-cloud-computing/buildkite-gcp/installation.md

@@ -81,8 +81,6 @@ The expected output is similar to:
 buildkite-agent version 3.109.1+10971.5c28e309805a3d748068a3ff7f5c531f51f6f495
 ```
 
-
-
 {{% notice Note %}}
 The Buildkite Agent version 3.43.0 introduces Linux/Arm64 Docker image for the Buildkite Agent, making deployment and installation easier for Linux users on Arm. You can view the [Buildkite agent GitHub release note](https://github.com/buildkite/agent/releases/tag/v3.43.0).
 
@@ -92,13 +90,6 @@ The [Arm Ecosystem Dashboard](https://developer.arm.com/ecosystem-dashboard/) re
 
 Buildkite uses Docker to build and push images.
 
-To make sure Docker runs whenever your VM starts, enable and start the Docker service:
-
-```bash
-sudo systemctl enable docker
-sudo systemctl start docker
-```
-
 This step ensures Docker is always available for your CI/CD pipelines.
 
 {{< tabpane code=true >}}
@@ -114,14 +105,6 @@ sudo usermod -aG docker $USER ; newgrp docker
   {{< /tab >}}
 {{< /tabpane >}}
 
-
-If you're using SUSE Linux, you need to run a few extra commands to start Docker. You don't need these steps on Ubuntu:
-
-```console
-sudo systemctl enable docker
-sudo systemctl start docker
-```
-
 Verify the Docker installation by checking the version and running a test container:
 
 ```console

content/learning-paths/servers-and-cloud-computing/buildkite-gcp/instance.md

@@ -6,25 +6,32 @@ weight: 3
 layout: learningpathall
 ---
 
-## Overview
+## Get started
 
-In this section, you'll learn how to provision a Google Axion C4A Arm virtual machine on Google Cloud Platform (GCP) using the `c4a-standard-4` instance type with 4 vCPUs and 16 GB memory in the Google Cloud Console.
+You're about to launch a Google Axion C4A Arm virtual machine on Google Cloud Platform (GCP). This section guides you through each step, from selecting the optimal instance type to configuring your operating system and networking. By the end, you'll have a ready-to-use Arm-based VM, perfect for high-performance workloads and cloud-native development.
+You'll learn how to provision a Google Axion C4A Arm virtual machine on Google Cloud Platform (GCP) using the `c4a-standard-4` instance type with 4 vCPUs and 16 GB memory in the Google Cloud Console.
 
-## Provision a Google Axion C4A VM in the Google Cloud Console
+## Provision a VM
 
 To create a virtual machine based on the C4A instance type:
+- Open the [Google Cloud Console](https://console.cloud.google.com/).
+- In the left navigation pane, select **Compute Engine** > **VM instances**.
+- Select **Create instance**.
+- In the **Machine configuration** section:
+   - Enter a value for **Instance name**.
+   - Select a **Region** and **Zone**.
+   - For **Series**, select **C4A**.
+   - For **Machine type**, select **c4a-standard-4**.
+- The following image shows the **Machine configuration** section with the C4A series and c4a-standard-4 machine type selected.
+
+   ![Screenshot of the Machine configuration section in Google Cloud Console with C4A series and c4a-standard-4 machine type selected.](images/gcp-vm.png "Creating a Google Axion C4A Arm virtual machine in Google Cloud Console")
+
+- In the **OS and storage** section, select **Change**.
+   - In the **Operating system** dialog, choose an Arm64-based image such as **SUSE Linux Enterprise Server** or **Ubuntu**.
+   - Select your preferred version, making sure to choose the Arm architecture.
+   - Select **Select** to confirm your choice.
+- In the **Networking** section, enable the **Allow HTTP traffic** option.
+- Select **Create** to launch your instance.
+
+Once the instance is running, you can connect to it using SSH from the Google Cloud Console or your local terminal. This allows you to configure your environment and begin deploying workloads on your new Arm-based VM.
 
-- Navigate to the [Google Cloud Console](https://console.cloud.google.com/).
-- Go to Compute Engine > VM Instances and select **Create Instance**.
-- Under **Machine configuration**:
-   - Populate fields such as **Instance name**, **Region**, and **Zone**.
-   - Set **Series** to **C4A**.
-   - Select **c4a-standard-4** for machine type.
-
-   ![Create a Google Axion C4A Arm virtual machine in the Google Cloud Console with c4a-standard-4 selected alt-text#center](images/gcp-vm.png "Creating a Google Axion C4A Arm virtual machine in Google Cloud Console")
-
-- Under **OS and Storage**, select **Change**, then choose an Arm64-based OS image. For this Learning Path, use **SUSE Linux Enterprise Server** or **Ubuntu**. Select your preferred version for the operating system. Ensure you choose the Arm version, then select **Select**.
-- Under **Networking**, enable **Allow HTTP traffic**.
-- Select **Create** to launch the instance.
-
-Once the instance is running, connect using SSH.