Final tweaks

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/envoy-gcp/baseline-testing.md

@@ -26,9 +26,6 @@ The test confirms the following:
 
 Using a text editor, create a file named `envoy_config.yaml` and add the following content as shown below. 
 
-This configures Envoy to listen on port **10000** and forward all traffic to `http://httpbin.org`. The `host_rewrite_literal` is required to prevent `404 Not Found` from the upstream server.
-
-
 ```yaml
 static_resources:
   listeners:
@@ -75,6 +72,11 @@ static_resources:
                 address: httpbin.org
                 port_value: 80
 ```
+
+## Explanatory notes on the configuration
+
+This configures Envoy to listen on port **10000** and forward all traffic to `http://httpbin.org`. The `host_rewrite_literal` is required to prevent `404 Not Found` from the upstream server.
+
 - **Listeners:** Envoy accepts incoming HTTP requests on port **10000** of your VM.
 - **HTTP Connection Manager:** Processes incoming requests, and applies routing.
 - **Routing:** All traffic is routed to the `service_httpbin` cluster, with the `Host` header rewritten to  `httpbin.org`.

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

@@ -8,20 +8,20 @@ layout: learningpathall
 
 ## How to run Envoy benchmarks with Siege on Arm64 in GCP
 
-**Siege** is a lightweight HTTP load testing and benchmarking tool that simulates concurrent users making requests to a target service. It is useful for Envoy benchmarking because it measures availability, throughput, response time, and failure rates under load, thus helping evaluate Envoy’s performance as a proxy under real-world traffic conditions.
+Siege is a lightweight HTTP load testing and benchmarking tool that simulates concurrent users making requests to a target service. It is useful for Envoy benchmarking because it measures availability, throughput, response time, and failure rates under load, thus helping evaluate Envoy’s performance as a proxy under real-world traffic conditions.
 
 Follow the steps outlined to run Envoy benchmarks using Siege.
 
 ## Install Siege (build from source)
 
 
-1. Install required build tools
+Install required build tools:
 
 ```console
 sudo dnf groupinstall -y "Development Tools"
 sudo dnf install -y wget make gcc
 ```
-2. Download, extract and build Siege source
+Download, extract and build Siege source:
 
 ```console
 wget http://download.joedog.org/siege/siege-4.1.6.tar.gz
@@ -33,13 +33,12 @@ sudo make install
 ```
 You have now successfully built and installed Siege on your Arm-based machine.
 
-
-3. Verify installation
+Verify installation:
 
 ```console
 siege --version
 ```
-This checks if Siege is installed properly and shows the version number.
+This checks if Siege is installed properly and shows the version number:
 ```output
 SIEGE 4.1.6
 
@@ -51,15 +50,15 @@ FOR A PARTICULAR PURPOSE.
 ## Envoy benchmarking
 
 
-1. To start, make sure Envoy is up and running with your config file (listening on port 10000):
+To start, make sure Envoy is up and running with your config file (listening on port 10000):
 
 
 ```console
 envoy -c envoy_config.yaml --base-id 1
 ```
 This runs the Envoy proxy with your configuration file (envoy_config.yaml) so it can start listening for requests.
 
-2. On another terminal, verify that Envoy is running as expected with curl:
+On another terminal, verify that Envoy is running as expected with curl:
 
 
 ```
@@ -150,7 +149,7 @@ Results from the earlier run on the `c4a-standard-4` (4 vCPU, 16 GB memory) Arm6
 ### Envoy performance benchmarking comparison on Arm64 and x86_64
 When you compare the benchmarking performance results between the two instance types with the same vCPUs, you will notice that on the Google Axion C4A Arm-based instances:
 
-- You have more successful transactions, fewer failures.
-- Lower response times, higher transaction rate, better throughput.
+- You have more successful transactions, fewer failures
+- Lower response times, higher transaction rate, better throughput
 
-You have successfully learned how to use Siege to benchmark Envoy on your Arm-based Axion Google cloud instance, validating both performance and reliability against similar x86 instances.
+You have successfully learned how to use Siege to benchmark Envoy on your Arm-based Axion Google cloud instance, validating both performance and reliability against similar x86_64 instances.

content/learning-paths/servers-and-cloud-computing/envoy-gcp/deploy.md

@@ -27,7 +27,7 @@ pip3 install virtualenv
 
 ## Install Envoy (static Arm64 binary)
 
-Download the Envoy binary; `-L` follows redirects:
+Download the Envoy binary. `-L` follows redirects:
 
 ```console
 sudo curl -L \

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

@@ -17,16 +17,15 @@ 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:
-1. Navigate to the [Google Cloud Console](https://console.cloud.google.com/).
-2. Go to **Compute Engine > VM Instances** and select **Create Instance**. 
-3. Under **Machine configuration**:
-   - Enter details such as **Instance name**, **Region**, and **Zone**.
+- 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 a machine type such as `c4a-standard-4`.
+   - 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](./image1.png "Google Cloud Console – creating a Google Axion C4A Arm virtual machine")
+   ![Create a Google Axion C4A Arm virtual machine in the Google Cloud Console with c4a-standard-4 selected alt-text#center](./image1.png "Creating a Google Axion C4A Arm virtual machine in Google Cloud Console")
 
-4. Under **OS and Storage**, select **Change**, then choose an Arm64-based OS image.  
-   For this Learning Path, use **Red Hat Enterprise Linux 9**. Ensure you select the **Arm image** variant. Click **Select**.
-5. Under **Networking**, enable **Allow HTTP traffic**.
-6. Click **Create** to launch the instance.
+- Under **OS and Storage**, select **Change**, then choose an Arm64-based OS image. For this Learning Path, use **Red Hat Enterprise Linux 9**. Ensure you select the **Arm image** variant. Click **Select**.
+- Under **Networking**, enable **Allow HTTP traffic**.
+- Click **Create** to launch the instance.