Tweaks

madeline-underwood · madeline-underwood · commit ad2c1bd1a8ee · 2025-09-29T13:22:34.000+01:00
diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/baseline.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/baseline.md
@@ -6,7 +6,7 @@ weight: 5
 layout: learningpathall
 ---
 
-# Baseline test NGINX with a static website
+## Baseline test NGINX with a static website
 
 Once NGINX is installed and serving the default welcome page, verify that it can serve your own content. A baseline test with a simple static HTML site confirms that NGINX is correctly configured and working as expected on your Ubuntu Pro 24.04 LTS virtual machine.
 
@@ -19,7 +19,7 @@ cd /var/www/my-static-site
 
 ## Create an HTML file
 
-Create a simple HTML page to replace the default NGINX welcome page. Using a file editor of your choice, create **index.html** with the following content:
+Create a simple HTML page to replace the default NGINX welcome page. Using a file editor of your choice, create `index.html` with the following content:
 ```html
 <!DOCTYPE html>
 <html lang="en">
@@ -63,13 +63,13 @@ Create a simple HTML page to replace the default NGINX welcome page. Using a fil
 ```
 
 ## Adjust permissions  
-Ensure that NGINX (running as the **www-data** user) can read the files in your custom site directory:
+Ensure that NGINX (running as the `www-data` user) can read the files in your custom site directory:
 ```console
 sudo chown -R www-data:www-data /var/www/my-static-site
 ```
 
 ## Update NGINX configuration
-Point NGINX to serve files from your new directory by creating a dedicated configuration file under **/etc/nginx/conf.d/**:
+Point NGINX to serve files from your new directory by creating a dedicated configuration file under `/etc/nginx/conf.d/`:
 ```console
 sudo nano /etc/nginx/conf.d/static-site.conf
 ```
@@ -91,14 +91,11 @@ server {
     error_log  /var/log/nginx/static-error.log;
 }
 ```
-This configuration tells NGINX to:
-
-- listen on port 80 (IPv4 and IPv6)
-- serve files from `/var/www/my-static-site/`
-- use `index.html` as the default page
-- log access and errors to dedicated log files for easier troubleshooting
+This server block listens on port 80 for both IPv4 and IPv6, serves files from `/var/www/my-static-site/`, and uses `index.html` as the default page. It also writes access and error events to dedicated log files to simplify troubleshooting.
 
+{{% notice Note %}}
 Make sure the path to your `index.html` file is correct before saving.
+{{% /notice %}}
 
 ## Disable the default site  
 NGINX ships with a packaged default site configuration. Since you created a custom config, disable the default to avoid conflicts:
@@ -132,6 +129,6 @@ http://<your-vm-public-ip>/
 
 ## Verify the page renders  
 You should see your custom page instead of the default welcome page:
-![Custom static website served by NGINX on Azure VM alt-text#center](images/nginx-web.png)
+![Custom static website served by NGINX on Azure VM alt-text#center](images/nginx-web.png "Custom static website served by NGINX on an Azure Arm64 VM")
 
 This verifies the basic functionality of the NGINX installation. You can now proceed to benchmarking NGINX performance on your Arm-based Azure VM.
diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/benchmarking.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/benchmarking.md
@@ -6,7 +6,7 @@ weight: 6
 layout: learningpathall
 ---
 
-# Benchmark NGINX with ApacheBench (ab) on Ubuntu Pro 24.04 LTS
+## Benchmark NGINX with ApacheBench (ab) on Ubuntu Pro 24.04 LTS
 
 Use ApacheBench (**ab**) to measure NGINX performance on your Arm64 Azure VM. This section shows you how to install the tool, run a basic benchmark, interpret key metrics, and review a sample result from an Azure **D4ps_v6** instance.
 
@@ -109,12 +109,7 @@ Percentage of the requests served within a certain time (ms)
 
 ## Interpret benchmark results
 
-ApacheBench outputs several metrics. Key ones to focus on include:
-
-- Requests per second: average throughput
-- Time per request (mean): latency per request
-- Failed requests: should be **0**
-- Transfer rate: effective bandwidth
+ApacheBench produces a variety of metrics, but the most useful ones highlight how well your server handles load. The requests per second value shows the average throughput, while the time per request (mean) indicates the latency experienced by each request. Ideally, the failed requests metric should remain at zero to confirm reliability. Finally, the transfer rate measures the effective bandwidth used by the responses, giving you insight into overall data flow efficiency.
 
 ## Benchmark summary on Arm64
 
@@ -146,7 +141,7 @@ The following results were collected on an Arm64 **D4ps_v6** VM running **Ubuntu
 
 These results highlight the performance characteristics of NGINX on Arm64-based Azure VMs (such as **D4ps_v6**):
 
-- High Requests Per second(31,523.86 requests/sec), demonstrating high throughput under concurrent load.
+- High Requests per second (31,523.86 requests/sec), demonstrating high throughput under concurrent load.
 - Response time per request averaged 1.586 ms, indicating efficient handling of requests with minimal delay.
 - Zero failed requests, confirming stability and reliability during testing.
 - Consistently low connection and processing times (mean ≈ 1 ms), ensuring smooth performance.
diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/deploy.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/deploy.md
@@ -108,7 +108,9 @@ This confirms that NGINX is functional at the system level, even before exposing
 
 ## Allow HTTP traffic (port 80) in UFW and NSG
 
-When you created your VM instance earlier, you configured the Azure **Network Security Group (NSG)** to allow inbound HTTP (**port 80**) traffic. On the VM itself, you must also allow traffic through the Ubuntu firewall (**UFW**). Run:
+When you created your VM instance earlier, you configured the Azure Network Security Group (NSG) to allow inbound HTTP (port 80) traffic. 
+
+On the VM itself, you must also allow traffic through the Ubuntu firewall (UFW). To do this, run:
 
 ```console
 sudo ufw allow 80/tcp
@@ -154,7 +156,7 @@ You can now access the NGINX welcome page from your VM’s public IP address. Ru
 echo "http://$(curl -s ifconfig.me)/"
 ```
 
-Copy the printed URL and open it in your browser. You should see the default NGINX welcome page, which confirms that HTTP traffic is reaching your VM.
+Copy the printed URL and open it in your browser. You should see the default NGINX welcome page as shown below, which confirms that HTTP traffic is reaching your VM:
 
 ![NGINX default welcome page in a web browser on an Azure VM alt-text#center](images/nginx-browser.png)
 
diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/instance.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/instance.md
@@ -7,15 +7,15 @@ layout: learningpathall
 ---
 ## Set up your development environment
 
-There are several ways to create an Arm-based Cobalt 100 virtual machine: 
+There is more than one way to create an Arm-based Cobalt 100 virtual machine: 
 
 - The Microsoft Azure portal
 - The Azure CLI
 - Your preferred infrastructure as code (IaC) tool
 
-In this section, you will use the Azure portal to create a virtual machine with the Arm-based Azure Cobalt 100 processor.
+In this Learning Path, you will use the Azure portal to create a virtual machine with the Arm-based Azure Cobalt 100 processor. 
 
-This Learning Path focuses on the general-purpose virtual machines in the D-series. For further information, see the Microsoft Azure guide for the [Dpsv6 size series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dpsv6-series).
+You will focus on the general-purpose virtual machines in the D-series. For further information, see the Microsoft Azure guide for the [Dpsv6 size series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dpsv6-series).
 
 While the steps to create this instance are included here for convenience, for further information on setting up Cobalt on Azure, see [Deploy a Cobalt 100 virtual machine on Azure Learning Path](/learning-paths/servers-and-cloud-computing/cobalt/).
 
@@ -40,7 +40,7 @@ To get started, launch the Azure portal and navigate to **Virtual Machines**. Th
 
 ![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance1.png "Allowing inbound port rules")
 
-Now select the **Review + create** tab and review the configuration for your virtual machine. It should look like the following:
+Now select the **Review and create** tab and review the configuration for your virtual machine. It should look like the following:
 
 ![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/ubuntu-pro.png "Reviewing and creating an Azure Cobalt 100 Arm64 VM")
 
