Updates

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/nginx-on-azure/deploy.md

@@ -1,18 +1,16 @@
 ---
-title: Install NGINX
+title: "Install NGINX"
 weight: 4
 
 ### FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
 
+# Install NGINX on Ubuntu Pro 24.04 LTS
 
+In this section, you install and configure NGINX, a high-performance web server and reverse proxy, on your Arm-based Azure instance. NGINX is widely used to serve static content, handle large volumes of connections efficiently, and act as a load balancer. Running it on your Azure Cobalt 100 virtual machine allows you to serve web traffic securely and reliably.
 
-## NGINX Installation on Ubuntu Pro 24.04 LTS
-
-In this section, you will install and configure NGINX, a high-performance web server and reverse proxy on your Arm-based Azure instance. NGINX is widely used to serve static content, handle large volumes of connections efficiently, and act as a load balancer. Running it on your Azure Cobalt-100 virtual machine will allow you to serve web traffic securely and reliably.
-
-### Install NGINX
+## Install NGINX
 
 Run the following commands to install and enable NGINX:
 
@@ -23,29 +21,31 @@ sudo systemctl enable nginx
 sudo systemctl start nginx
 ```
 
-### Verify NGINX
+## Verify NGINX installation
 
 Check the installed version of NGINX:
 
 ```console
 nginx -v
 ```
-The output should look like:
+
+Expected output:
 
 ```output
 nginx version: nginx/1.24.0 (Ubuntu)
 ```
-{{% notice Note %}}
-
-The [Arm Ecosystem Dashboard](https://developer.arm.com/ecosystem-dashboard/) recommends NGINX version 1.20.1 as the minimum recommended on the Arm platforms.
 
+{{% notice Note %}}
+The [Arm Ecosystem Dashboard](https://developer.arm.com/ecosystem-dashboard/) recommends NGINX version 1.20.1 or later for Arm platforms.
 {{% /notice %}}
 
-You can confirm that NGINX is running correctly by checking its systemd service status:
+You can also confirm that NGINX is running correctly by checking its systemd service status:
+
 ```console
 sudo systemctl status nginx
 ```
-You should see output similar to:
+
+Expected output:
 
 ```output
 ● nginx.service - A high performance web server and a reverse proxy server
@@ -63,19 +63,20 @@ You should see output similar to:
              ├─1944 "nginx: worker process"
              └─1945 "nginx: worker process"
 ```
-If you see Active: active (running), NGINX is successfully installed and running.
 
+If you see `Active: active (running)`, NGINX is successfully installed and running.
+
+## Validate with curl
 
-### Validation with curl
-Validation with `curl` confirms that NGINX is correctly installed, running, and serving **HTTP** responses.
+You can validate that NGINX is serving HTTP responses using `curl`:
 
-Run the following command to send a HEAD request to the local NGINX server:
 ```console
 curl -I http://localhost/
 ```
-The -I option tells curl to request only the HTTP response headers, without downloading the page body.
 
-You should see output similar to:
+The **-I** option requests only the HTTP response headers without downloading the page body.
+
+Expected output:
 
 ```output
 HTTP/1.1 200 OK
@@ -94,19 +95,18 @@ Output summary:
 - Server: nginx/1.24.0: Shows that the server is powered by NGINX.
 - Content-Type, Content-Length, Last-Modified, ETag: Provide details about the served file and its metadata.
 
-This step verifies that your NGINX installation is functional at the system level, even before exposing it to external traffic. It’s a quick diagnostic check that is useful when troubleshooting connectivity issues.
-
-### Allowing HTTP Traffic
+This confirms that NGINX is functional at the system level, even before exposing it to external traffic.
 
-When you created your VM instance earlier, you configured the Azure Network Security Group (NSG) to allow inbound HTTP (port 80) traffic. This means the Azure-side firewall is already open for web requests.
-On the VM itself, you still need to make sure that the Uncomplicated firewall (UFW) which is used to manage firewall rules on Ubuntu allows web traffic. Run:
+## Allow HTTP traffic
 
+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:
 
 ```console
 sudo ufw allow 80/tcp
 sudo ufw enable
 ```
-The output from this command should look like:
+
+Expected output:
 
 ```output
 sudo ufw enable
@@ -115,12 +115,15 @@ Rules updated (v6)
 Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
 Firewall is active and enabled on system startup
 ```
-You can verify that HTTP is now allowed with:
+
+Verify that HTTP is allowed with:
 
 ```console
 sudo ufw status
 ```
-You should see an output similar to: 
+
+Expected output:
+
 ```output
 Status: active
 
@@ -131,17 +134,19 @@ To                         Action      From
 8080/tcp (v6)              ALLOW       Anywhere (v6)
 80/tcp (v6)                ALLOW       Anywhere (v6)
 ```
-This ensures that both Azure and the VM-level firewalls are aligned to permit HTTP requests.
 
-### Accessing the NGINX Default Page
+This ensures that both Azure and the VM-level firewalls permit HTTP requests.
 
-You can now access the NGINX default page from your Virtual machine’s public IP address. Run the following command to display your public URL:
+## Access the NGINX default page
+
+You can now access the NGINX default page from your VM’s public IP address. Run:
 
 ```console
 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 a successful installation and that HTTP traffic is reaching your VM.
 
-![NGINX](images/nginx-browser.png)
+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.
+
+![NGINX default welcome page in a web browser on an Azure VM alt-text#center](images/nginx-browser.png)
 
-At this stage, your NGINX installation is complete. You are now ready to proceed with baseline testing and further configuration.
+At this stage, your NGINX installation is complete. You are ready to begin baseline testing and further configuration.