Refine documentation for Node.js on Google Cloud C4A: update titles, enhance clarity, and improve installation instructions

Author: madeline-underwood

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

@@ -1,5 +1,5 @@
 ---
-title:  Deploy Node.js on Google Cloud C4A on Arm-based Axion VMs
+title:  Deploy Node.js on Google Cloud C4A Arm-based Axion VMs
 
 
 
@@ -9,9 +9,9 @@ who_is_this_for: This is an introductory topic for software developers migrating
 
 
 learning_objectives:
-  - Provision an Arm-based SUSE SLES virtual machine on Google Cloud (C4A with Axion processors)
+  - Provision an Arm-based SUSE Linux Enterprise Server virtual machine on Google Cloud C4A instances with Axion processors
   - Install and configure Node.js on a SUSE Arm64 (C4A) instance
-  - Validate Node.js functionality with baseline HTTP server tests  
+  - Validate Node.js functionality with baseline HTTP server tests
   - Benchmark Node.js performance using Autocannon on Arm64 (AArch64) architecture 
 
 

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

@@ -16,6 +16,6 @@ For more information on Google Axion, see the Google blog [Introducing Google Ax
 
 ## Node.js
 
-Node.js is an open-source, cross-platform JavaScript runtime environment built on Chrome's V8 engine. It enables you to build scalable server-side applications, APIs, and backend services using JavaScript. Node.js features an event-driven, non-blocking I/O model, making it highly efficient for handling concurrent connections.
+Node.js is an open-source, cross-platform JavaScript runtime environment built on Chrome's V8 engine. It enables you to build scalable server-side applications, APIs, and backend services using JavaScript. Node.js features an event-driven, non-blocking I/O model, making it highly efficient for handling concurrent connections. Node.js is widely used for web servers, real-time applications, microservices, and cloud-native backend services. 
 
-Node.js is widely used for web servers, real-time applications, microservices, and cloud-native backend services. For more information on Node.js, see the [Node.js official website](https://nodejs.org/en) and the [Node.js documentation](https://nodejs.org/docs/latest/api/).
+For more information on Node.js, see the [Node.js website](https://nodejs.org/en) and the [Node.js documentation](https://nodejs.org/docs/latest/api/).

content/learning-paths/servers-and-cloud-computing/node-js-gcp/benchmarking.md

@@ -10,14 +10,14 @@ layout: learningpathall
 
 After validating that Node.js is installed and your HTTP server is running, you can benchmark it using **Autocannon**.
 
-### Install Autocannon
+## Install Autocannon
 **Autocannon** is a fast HTTP/1.1 benchmarking tool for Node.js, used to measure server throughput, latency, and request handling under concurrent load.
 
 ```console
 npm install -g autocannon
 ```
 
-### Start Your Node.js HTTP Server
+## Start Your Node.js HTTP Server
 
 If your sample HTTP server is not already running from the last section, you can start it by typing:
 ```console
@@ -31,7 +31,7 @@ Server should be listening on port 80 in the background:
 Server running at http://0.0.0.0:80/
 ```
 
-### Run a Basic Benchmark (Local)
+## Run a Basic Benchmark (Local)
 
 ```console
 autocannon -c 100 -d 10 http://localhost:80
@@ -65,7 +65,7 @@ Req/Bytes counts sampled once per second.
 707k requests in 10.02s, 137 MB read
 ```
 
-### Understanding Node.js benchmark metrics and results with Autocannon
+## Understanding Node.js benchmark metrics and results with Autocannon
 
 - **Avg (Average Latency)** → The mean time it took for requests to get a response.
 - **Stdev (Standard Deviation)** → How much individual request times vary around the average. Smaller numbers mean more consistent response times.
@@ -103,7 +103,7 @@ Throughput:
 | Req/Sec    | 45,279 | 45,279 | 54,719  | 55,199  | 53,798.4 | 2,863.96 | 45,257 |
 | Bytes/Sec  | 8.78 MB| 8.78 MB| 10.6 MB | 10.7 MB | 10.4 MB  | 557 kB   | 8.78 MB |
 
-### Node.js performance benchmarking comparison on Arm64 and x86_64
+## Node.js performance benchmarking comparison on Arm64 and x86_64
 When you compare the benchmarking results, you will notice that on the Google Axion C4A Arm-based instances:
 
 - Average latency is very low (~1.2 ms) with consistent response times.  

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

@@ -1,53 +1,59 @@
 ---
-title: Install Node.js Using Node Version Manager
+title: Install Node.js using Node Version Manager
 weight: 4
 
 ### FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
 
-## Install Node.js with Node Version Manager (NVM)
-This Learning Path walks you through installing **NodeJS** via the Node Version Manager (NVM).  NVM is a powerful tool that allows users to specify which version of **NodeJS** that they want to use. NVM will then download and install the requested vesion using the **NodeJS** official packages. 
+## Overview
+This section shows you how to install Node.js using Node Version Manager (NVM). NVM lets you choose which Node.js version to use and handles the download and installation for you. You’ll use official Node.js packages, making setup simple and reliable.
 
-### 1. Install Node Version Manager (NVM)
-First, we will run this command to download and install NVM into our VM instance:
+## Install Node Version Manager (NVM)
+First, use this command to download and install NVM into your VM instance:
 
 ```console
 curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
 ```
 
-Next, we have to activate NVM in our terminal shell.  We can manually activate our current shell via copy and paste of the following into the shell:
+Next, activate Node Version Manager (NVM) in your current terminal session. Copy and paste the following commands into your shell to load NVM and enable command completion:
+
+```console
+export NVM_DIR="$HOME/.nvm"
+[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
+[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"
+```
+
+This step ensures that NVM commands are available in your shell. If you open a new terminal, repeat these commands or add them to your `~/.bashrc` file for automatic activation:
 
 ```console
 export NVM_DIR="$HOME/.nvm"
 [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
 [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
 ```
 
-You should be able to confirm that NVM is available by typing:
+Confirm that NVM is available by typing:
 
 ```console
 nvm --version
 ```
 
-### 2. Install NodeJS
-Now that NVM is installed, we simply type the following commands in our shell to download and install **NodeJS**: 
+## Install Node.js
+Now that NVM is installed, download and install Node.js: 
 
 ```console
 nvm install v24
 nvm use v24
 ```
 
-Additionally, we can add this command to the bottom of our $HOME/.bashrc file:
+Next, add this command to the bottom of your $HOME/.bashrc file:
 
 ```console
 echo 'nvm use v24' >> ~/.bashrc
 ```
 
-### 3. Verify Installation
-Check that Node.js and npm (Node’s package manager) are installed correctly.
-
-You should be able to confirm that **NodeJS** is now installed and available!
+## Verify installation
+Check that Node.js and npm (Node.js package manager) are installed correctly by using this command that confirms that **NodeJS** is installed and available:
 
 ```console
 node --version
@@ -60,4 +66,10 @@ v24.10.0
 11.6.1
 ```
 
-Node.js installation is complete. You can now proceed with the baseline testing.
+This shows you that Node.js installation is complete. You can now proceed with the baseline testing.
+
+## What you've accomplished
+
+You've successfully provisioned a Google Axion C4A Arm virtual machine running SUSE Linux Enterprise Server. You're now ready to install Node.js and deploy your workloads on Arm.
+
+

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

@@ -16,25 +16,48 @@ For support on GCP setup, see the Learning Path [Getting started with Google Clo
 
 ## Provision a Google Axion C4A Arm VM in Google Cloud Console
 
-To create a virtual machine based on the C4A instance type:
-- Navigate to [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**.
+To create a virtual machine using the C4A instance type in Google Cloud Platform:
+
+- Open [Google Cloud Console](https://console.cloud.google.com/).
+- In the left menu, select **Compute Engine**, then select **VM Instances**.
+- Select **Create Instance**.
+- In the **Machine configuration** section:
+   - Enter a unique **Instance name**.
+   - Choose your preferred **Region** and **Zone**.
    - Set **Series** to `C4A`.
-   - Select `c4a-standard-4` for machine type.
+   - Select `c4a-standard-4` for the 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")
 
+This configuration gives you four Arm vCPUs and 16 GB memory, optimized for Arm workloads.
+
+## Select OS and finalize VM settings
+
+After configuring the machine type, you'll need to select the operating system and finalize your VM settings. Follow the steps below to select an Arm64-based OS image, configure networking, and launch your instance. This ensures your VM is ready for Arm-native development and accessible for further setup.
+
+
+- In the **OS and Storage** section, select **Change**:
+   - Choose an Arm64-based OS image. For this Learning Path, select **SUSE Linux Enterprise Server**.
+   - For **License type**, select **Pay as you go**.
+   - Select **Select** to confirm your choices.
+
+- In the **Networking** section, enable **Allow HTTP traffic**.
+
+- Select **Review and create** to review your configuration.
+
+- Select **Create** to launch your VM instance.
+
+- After the VM is created, locate your instance in the **VM Instances** list.
+   - Select the **SSH** button next to your instance to open a browser-based SSH shell.
+
+{{% notice Note %}}
+If you don't see the **SSH** option, refresh the page or check that your VM is running. The SSH shell opens in a new browser window, giving you direct access to your Arm-based VM.
+{{% /notice %}}
 
-- Under **OS and Storage**, select **Change**, then choose an Arm64-based OS image. For this Learning Path, use **SUSE Linux Enterprise Server**. Select "Pay As You Go" for the license type. Click **Select**.
-- Under **Networking**, enable **Allow HTTP traffic**.
-- Click **Create** to launch the instance.
-- Once created, you should see a "SSH" option to the right in your list of VM instances.  Click on this to launch a SSH shell into your VM instance:
 
 ![Invoke a SSH session via your browser alt-text#center](images/gcp-ssh.png "Invoke a SSH session into your running VM instance")
 
-- A window from your browser should come up and you should now see a shell into your VM instance:
+A window from your browser should come up and you should now see a shell into your VM instance:
 
 ![Terminal Shell in your VM instance alt-text#center](images/gcp-shell.png "Terminal shell in your VM instance")