Updates

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/microbenchmark-network-iperf3/_index.md

@@ -1,13 +1,13 @@
 ---
-title: Microbenchmark and tune network performance with iperf3 and Linux traffic control
+title: Microbenchmark and tune network performance with iPerf3 and Linux traffic control
 
 whminutes_to_complete: 30
 
 who_is_this_for: This is an introductory topic for performance engineers, Linux system administrators, or application developers who want to microbenchmark, simulate, or tune the networking performance of distributed systems.
 
 learning_objectives: 
-    - Understand how to use iperf3 for network microbenchmarking.
-    - Use Linux traffic control (tc) to simulate different network conditions.
+    - Understand how to use iPerf3 for network microbenchmarking.
+    - Use Linux Traffic Control (TC) to simulate different network conditions.
     - Identify and apply basic runtime parameters to tune performance.
 
 prerequisites:
@@ -22,13 +22,13 @@ subjects: Performance and Architecture
 armips:
     - Neoverse
 tools_software_languages:
-    - iperf3
+    - iPerf3
 operatingsystems:
     - Linux
 
 further_reading:
     - resource:
-        title: iperf3 user manual 
+        title: iPerf3 user manual 
         link: https://iperf.fr/iperf-doc.php
         type: documentation
 

content/learning-paths/servers-and-cloud-computing/microbenchmark-network-iperf3/setup.md

@@ -1,5 +1,5 @@
 ---
-title: Prepare for network performance testing
+title: Set up Arm-Based Linux systems for network performance testing with iPerf3
 weight: 2
 
 ### FIXED, DO NOT MODIFY
@@ -8,7 +8,7 @@ layout: learningpathall
 
 ## Configure two Arm-based Linux computers
 
-To perform network performance testing, you'll need access to two Arm-based Linux systems. You can use AWS EC2 instances with Graviton processors, or Linux virtual machines from any other cloud service provider.
+To benchmark bandwidth and latency between Arm-based systems, you'll need to configure two Linux machines running on Arm. You can use AWS EC2 instances with Graviton processors, or Linux virtual machines from any other cloud service provider.
 
 This tutorial also walks you through a local-to-cloud test to compare performance between:
 
@@ -17,7 +17,7 @@ This tutorial also walks you through a local-to-cloud test to compare performanc
 
 The setup instructions below use AWS EC2 instances connected within a Virtual Private Cloud (VPC).
 
-To get started, create two Arm-based Linux instances, each instance will serve one role:
+To get started, create two Arm-based Linux instances, with each instance serving one role:
 
 * One acts as a server
 * One acts as a client
@@ -26,7 +26,7 @@ The instructions below use two `t4g.xlarge` instances running Ubuntu 24.04 LTS.
 
 ## Install software dependencies
 
-Use the commands below to install `iperf3`, a powerful open-source CLI tool for measuring maximum achievable network bandwidth. 
+Use the commands below to install iPerf3, which is a powerful open-source CLI tool for measuring maximum achievable network bandwidth. 
 
 Install `iperf3` on both the client and server systems:
 
@@ -36,10 +36,10 @@ sudo apt install iperf3 -y
 ```
 
 {{% notice Note %}}
-If you're prompted to run `iperf3` as a daemon, you can safely answer "no".
+If you're prompted to run `iperf3` as a daemon, answer "no".
 {{% /notice %}}
 
-## Update Security Rules 
+## Update security rules 
 
 If you're working in a cloud environment like AWS, you must update the default security rules to enable specific inbound and outbound protocols. 
 
@@ -53,8 +53,9 @@ From the AWS console:
 
 ![example_traffic#center](./example_traffic_rules.png "Example traffic")
 
-{{% notice Note %}}
+{{% notice Warning %}}
 For secure internal communication, set the source to your instance’s security group. This avoids exposing traffic to the internet while allowing traffic between your systems.
+
 You can restrict the range further by:
 
 * Opening only TCP port 5201
@@ -92,6 +93,14 @@ Add the client's IP address and assign it the name `CLIENT`:
 10.248.213.105  CLIENT
 ```
 
+| Instance Name | Role   | Description                        |
+|---------------|--------|------------------------------------|
+| SERVER        | Server | Runs `iperf3` in listen mode       |
+| CLIENT        | Client | Initiates performance tests        |
+
+
+
+
 ## Confirm server is reachable
 
 Finally, confirm the client can reach the server with the ping command below. As a reference you can also ping the localhost. 
@@ -100,7 +109,9 @@ Finally, confirm the client can reach the server with the ping command below. As
 ping SERVER -c 3 && ping 127.0.0.1 -c 3
 ```
 
-The output below shows that both SERVER and localhost (127.0.0.1) are reachable. Naturally, the local host response time is ~10x faster than the server. Your results will vary depending on geographic location of the systems and other networking factors. 
+The output below shows that both SERVER and localhost (127.0.0.1) are reachable. 
+
+Localhost response times are typically ~10× faster than remote systems. Actual values will vary based on system location and network conditions.
 
 ```output
 PING SERVER (10.248.213.104) 56(84) bytes of data.

content/learning-paths/servers-and-cloud-computing/microbenchmark-network-iperf3/tuning.md

@@ -10,19 +10,19 @@ layout: learningpathall
 
 You can look at ways to mitigate performance degradation due to events such as packet loss. 
 
-In this example, you will connect to the server node a local machine to demonstrate a longer response time. Check the `iperf3` [installation guide](https://iperf.fr/iperf-download.php) to install `iperf3` on other operating systems. 
+In this example, you will connect to the server node a local machine to demonstrate a longer response time. Check the iPerf3 [installation guide](https://iperf.fr/iperf-download.php) to install iPerf3 on other operating systems. 
 
 Make sure to set the server security group to accept the TCP connection from your local computer IP address. You will also need to use the public IP for the cloud instance.
 
-Running `iperf3` on the local machine and connecting to the cloud server shows a longer round trip time, in this example more than 40ms. 
+Running iPerf3 on the local machine and connecting to the cloud server shows a longer round trip time, in this example more than 40ms. 
 
 On your local computer run:
 
 ```bash
 iperf3 -c <server-public-IP> -V
 ```
 
-Running a standard TCP client connection with `iperf3` shows an average bitrate of 157 Mbps compared to over 2 Gbps when the client and server are both in AWS.
+Running a standard TCP client connection with iPerf3 shows an average bitrate of 157 Mbps compared to over 2 Gbps when the client and server are both in AWS.
 
 ```output
 Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 10 second test, tos 0
@@ -59,7 +59,7 @@ sudo sysctl net.core.rmem_max=134217728 # default = 212992
 sudo sysctl net.core.wmem_max=134217728 # default = 212992
 ```
 
-Restart the `iperf3` server.  
+Restart the iPerf3 server:  
 
 ```bash
 iperf3 -s