updating transitions

Author: anupras-mohapatra-arm

content/learning-paths/servers-and-cloud-computing/nginx_tune/before_and_after.md

@@ -31,4 +31,4 @@ This result is an example, not a guaranteed improvement for every workload. Your
 
 You've now learned why tuning NGINX is useful and reviewed an example benchmark demonstrating improvement in `wrk` throughput after tuning. 
 
-Next, you'll learn about kernel, compiler, and library optimizations. 
+Next, you'll learn about Linux network settings, compiler options, and supporting libraries that can affect NGINX performance.

content/learning-paths/servers-and-cloud-computing/nginx_tune/kernel_comp_lib.md

@@ -87,6 +87,6 @@ NGINX relies on [zlib](https://zlib.net/) for HTTP response compression when the
 
 ## What you've learned and what's next
 
-You've now learned about different kernel, compiler, and library optimizations that you can make to tune NGINX performance.
+You've now learned how Linux network settings, compiler options, and supporting libraries can affect NGINX throughput and latency.
 
 Next, you'll review the configuration for a static file server and learn about optimizations that you can make.

content/learning-paths/servers-and-cloud-computing/nginx_tune/test_optimizations.md

@@ -44,7 +44,7 @@ The following diagram shows a typical multi-node test setup. The load generator
 
 You can also run `wrk` directly against NGINX file servers, or run `wrk` on the same node as NGINX. Choose a setup that reflects your deployment and avoids making the load generator the bottleneck.
 
-![Diagram showing a load generator running wrk against an NGINX reverse proxy with upstream NGINX file servers.#center](exampletestsetup.png "Example NGINX load test setup")
+![Diagram showing a load generator client sending HTTPS requests to an NGINX reverse proxy instance under test, which forwards HTTP traffic to upstream NGINX file servers.#center](exampletestsetup.png "Example NGINX load test setup")
 
 ### Run a wrk test
 
@@ -88,6 +88,6 @@ The API gateway shown in [Tune a reverse proxy or API gateway](/learning-paths/s
 
 ## What you've accomplished 
 
-You've now used `wrk` to run an NGINX performance test.
+You've now built `wrk`, created sample files, and run repeatable load tests against an NGINX workload.
 
-You can use the guidance in this Learning Path to optimize the performance of your NGINX workloads on Arm-based platforms.  
+You can use the guidance in this Learning Path to optimize and compare the performance of your NGINX workloads on Arm-based platforms.  

content/learning-paths/servers-and-cloud-computing/nginx_tune/tune_revprox_and_apigw.md

@@ -83,6 +83,7 @@ The following are performance-relevant directives that weren't discussed in the
 
 ## What you've learned and what's next
 
-You've seen an example reverse proxy and API gateway configuration and learned about performance-relevant directives that you can optimize to tune NGINX performance. 
+You've now reviewed reverse proxy and API gateway directives that affect upstream connection reuse, request rewriting, access control, and caching decisions.
+
+Next, you'll test NGINX optimizations with a repeatable `wrk` workload.
 
-Next, you'll learn how to test NGINX optimizations using `wrk`.

content/learning-paths/servers-and-cloud-computing/nginx_tune/tune_static_file_server.md

@@ -114,6 +114,6 @@ The following are performance-relevant directives:
 
 ## What you've learned and what's next
 
-You've now seen example top-level and file server configurations and learned about performance-relevant directives that you can optimize to tune NGINX performance. 
+You've now reviewed optimizable top-level and static file server directives that affect worker limits, keepalive behavior, file serving, logging, and TLS choices.
 
-Next, you'll learn about tuning a reverse proxy and API gateway configuration.
+Next, you'll apply the same top-level NGINX settings to a reverse proxy and API gateway configuration, and review directives specific to such workloads.