Update install_circleci_runner.md

Author: pareenaverma

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

@@ -8,64 +8,66 @@ layout: learningpathall
 
 ## Install CircleCI Machine Runner on SUSE Arm64
 
-This guide explains how to install and configure the **CircleCI Machine Runner** on a **GCP SUSE Arm64 virtual machine**.  
-This setup allows your self-hosted environment to execute CircleCI jobs targeting Arm64 architecture.
+This section explains how to install and configure the CircleCI Machine Runner on a SUSE Linux Arm64 virtual machine running on Google Cloud C4A (Axion). By installing this runner, you enable your own VM to execute CircleCI Arm-native jobs.
 
 ### Add CircleCI Package Repository
 
-SUSE is an RPM-based distribution, so first add the official CircleCI repository:
+Because SUSE is an RPM-based Linux distribution, you first need to add the official CircleCI package repository from PackageCloud:
 
 ```console
 curl -s https://packagecloud.io/install/repositories/circleci/runner/script.rpm.sh?any=true | sudo bash
 ```
+This command automatically detects your distribution and adds the appropriate repository configuration for SUSE-based systems.
+
 ### Install the CircleCI Runner
-Create a symlink for `adduser` as the Circle CI runner script assumes Ubuntu/Debian as your OS:
+Before installation, create a symbolic link for `adduser`. The CircleCI runner installation script is primarily built for Debian/Ubuntu systems, which use the `adduser` command. SUSE uses `useradd` instead.
 
 ```bash
 sudo ln -s /usr/sbin/useradd /usr/sbin/adduser
 ```
 
-Install the pre-built CircleCI runner package:
+Now install the CircleCI runner package:
 
 ```console
 sudo zypper install -y circleci-runner
 ```
 ### Prepare User and Permissions
-Before starting the runner, ensure the required user, group, and directory permissions are properly set up:
-
-```console
-# Create a symlink for adduser (required on SUSE)
-sudo ln -s /usr/sbin/useradd /usr/sbin/adduser
+Before starting the CircleCI runner, ensure the correct user, group, and directory permissions are in place. These steps ensure the runner operates securely and has proper access to its configuration and work directories.
 
-# Create CircleCI system user and group
+Create CircleCI system user and group: 
+```bash
 sudo useradd -m -r circleci
 sudo groupadd --system circleci
-
-# Set up CircleCI directories and permissions
+```
+Set up CircleCI directories and permissions:
+```bash
 sudo mkdir -p /var/lib/circleci
 sudo chown -R circleci:circleci /var/lib/circleci
 sudo chown -R circleci:circleci /etc/circleci-runner
-
-# Reload systemd and restart the runner service
+```
+Reload systemd and restart the runner service:
+```bash
 sudo systemctl daemon-reload
 sudo systemctl restart circleci-runner
-
-# Verify service status
+```
+Verify service status:
+```bash
 sudo systemctl status circleci-runner
 ```
 
 ### Configure the Runner Token
 
-Replace the authentication token in the runner configuration file.
-Use the token obtained from your Resource Class in the CircleCI Dashboard.
+Now, configure the authentication token that connects your runner to CircleCI.
+Use the token generated earlier from your Resource Class in the CircleCI dashboard.
 
 ```console
 export RUNNER_AUTH_TOKEN="AUTH_TOKEN "
 sudo sed -i "s/<< AUTH_TOKEN >>/$RUNNER_AUTH_TOKEN/g" /etc/circleci-runner/circleci-runner-config.yaml
 ```
+Replace AUTH_TOKEN with the actual token copied from the CircleCI dashboard.
 
 ### Enable and Start the Runner
-Enable the CircleCI runner service to start automatically and verify it’s running:
+Enable the CircleCI service to start automatically at boot, then start and verify the runner:
 
 ```console
 sudo systemctl enable circleci-runner
@@ -90,6 +92,6 @@ Oct 09 11:15:03 lpprojectsusearm64 circleci-runner[10150]: 11:15:03 6f109 46.059
 Oct 09 11:15:03 lpprojectsusearm64 circleci-runner[10150]: 11:15:03 6f109 46.119ms claim app.loop_name=claim:  mode=agent res>
 Oct 09 11:15:03 lpprojectsusearm64 circleci-runner[10150]: 11:15:03 6f109 46.144ms worker loop: claim:  app.backoff_ms=5000 a>
 ```
-Also, you can verify it from the dashboard:
+You can also confirm that your runner is connected and active by visiting the Self-Hosted Runners page in the CircleCI web dashboard.
 
 ![Self-Hosted Runners alt-text#center](images/dashboard.png "Figure 1: Self-Hosted Runners ")