Improve documentation clarity and consistency for CircleCI workflows on SUSE Arm, including title adjustments, section headings, and enhanced explanations.

Author: madeline-underwood

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

@@ -1,13 +1,9 @@
 ---
 title: CircleCI Arm Native Workflows on SUSE Arm (GCP VM)
-
-draft: true
-cascade:
-    draft: true
 
 minutes_to_complete: 45
 
-who_is_this_for: This is an introductory topic for software developers and DevOps engineers looking to set up and run CircleCI Arm native workflows on SUSE Linux Arm64 VMs, specifically on Google Cloud C4A with Axion processors, using self-hosted runners.
+who_is_this_for: This is an introductory topic for software developers and DevOps engineers looking to set up and run CircleCI Arm native workflows on SUSE Linux Arm64 virtual machines (VMs), specifically on Google Cloud C4A with Axion processors, using self-hosted runners.
 
 learning_objectives:
   - Provision a SUSE Arm64 virtual machine on Google Cloud (C4A with Axion processors)

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

@@ -6,15 +6,15 @@ weight: 2
 layout: "learningpathall"
 ---
 
-## Google Axion C4A Arm instances in Google Cloud
+## Explore Google Axion C4A Arm instances on Google Cloud
 
 Google Axion C4A 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 for modern cloud workloads such as CI/CD pipelines, microservices, media processing, and general-purpose applications.
 
 The C4A series provides a cost-effective alternative to x86 virtual machines while leveraging the scalability and performance benefits of the Arm architecture in Google Cloud.
 
-To learn more about Google Axion, refer to the [Introducing Google Axion Processors, our new Arm-based CPUs](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu) blog.
+To learn more about Google Axion, 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).
 
-## CircleCI
+## Learn about CircleCI for Arm-based CI/CD workflows
 
 CircleCI is a cloud-based Continuous Integration and Continuous Delivery (CI/CD) platform that automates the process of building, testing, and deploying software.
 

content/learning-paths/servers-and-cloud-computing/circleci-gcp/create_resource_class.md

@@ -6,9 +6,10 @@ weight: 5
 layout: learningpathall
 ---
 
-## Create a Resource Class for Self-Hosted Runner in CircleCI
-This section explains how to create a Resource Class in the CircleCI Web Dashboard for a self-hosted runner.
-A Resource Class is a unique identifier that links your self-hosted runner to your CircleCI organization (namespace). It defines the “machine type” that CircleCI jobs can target, ensuring that only authorized jobs run on your managed infrastructure, in this case, your SUSE Linux Arm64 VM on Google Cloud C4A (Axion).
+## Create a resource class for a self-hosted runner in CircleCI
+This section explains how to create a resource class in the CircleCI web dashboard for a self-hosted runner.
+
+A resource class is a unique identifier that links your self-hosted runner to your CircleCI organization (namespace). It defines the *machine type* that CircleCI jobs can target, ensuring that only authorized jobs run on your managed infrastructure, which in this case is your SUSE Linux Arm64 VM on Google Cloud C4A (Axion).
 
 ### Steps
 
@@ -19,9 +20,9 @@ A Resource Class is a unique identifier that links your self-hosted runner to yo
      Check “Yes, I agree to the terms” to enable runner functionality for your organization.
    - After accepting, click Self-Hosted Runners again to continue the setup process.
 
-![Self-Hosted Runners alt-text#center](images/shrunner0.png "Figure 1: Self-Hosted Runners ")
+![CircleCI dashboard showing the Self-Hosted Runners section. The main panel displays options to add a new runner and manage existing ones. The left navigation menu highlights Self-Hosted Runners. The environment is a web interface with a neutral, professional tone. Visible text includes Self-Hosted Runners and related setup instructions. alt-text#center](images/shrunner0.png "Self-Hosted Runners")
 
-2. Create a New Resource Class
+## Create a New Resource Class
 
 On your CircleCI Dashboard, click Create Resource Class.
 

content/learning-paths/servers-and-cloud-computing/circleci-gcp/install-circleci-cli.md

@@ -1,5 +1,5 @@
 ---
-title: Install CircleCI CLI
+title: Install CircleCI CLI on GCP VM
 weight: 4
 
 ### FIXED, DO NOT MODIFY
@@ -9,9 +9,11 @@ layout: learningpathall
 ## Install CircleCI CLI on GCP VM
 This section explains how to install the CircleCI Command Line Interface (CLI) on a SUSE Linux (Arm64) virtual machine running on Google Cloud C4A (Axion). The CLI allows you to interact with CircleCI directly from your terminal, to validate configuration files, run jobs locally, or manage runners.
 
-### Install Required Packages
+## Install required packages on SUSE Arm64
 
-Before installing the CLI, make sure your SUSE environment has the necessary repositories and development tools. Add the openSUSE Leap repository:
+Before installing the CLI, make sure your SUSE environment has the necessary repositories and development tools. 
+
+Add the openSUSE Leap repository:
 
 ```bash
 sudo zypper addrepo https://download.opensuse.org/distribution/leap/15.5/repo/oss/ openSUSE-Leap-15.5-OSS
@@ -23,8 +25,9 @@ sudo zypper refresh
 ```
 This updates the local metadata so that zypper recognizes the latest available packages and dependencies.
 
-# Install git
-Before installing the CircleCI CLI, make sure your system has the basic tools required for downloading and extracting files.
+## Install git
+
+Before installing the CircleCI CLI, make sure your system has the basic tools required for downloading and extracting files:
 
 ```console
 sudo zypper install -y curl tar gzip coreutils gpg git-core

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

@@ -26,6 +26,6 @@ To create a virtual machine based on the C4A instance 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**. Pick the preferred version for your Operating System. Ensure you select the **Arm image** variant. Click **Select**.
+- Under **OS and Storage**, select **Change**, then select an Arm64-based OS image. For this Learning Path, use **SUSE Linux Enterprise Server**. Pick the preferred version for your Operating System. Ensure you select the **Arm image** variant. Click **Select**.
 - Under **Networking**, enable **Allow HTTP traffic**.
 - Click **Create** to launch the instance.