Fix 5 documentation issues for shared ConfigMap architecture

- Update error message to show 'curl', 'wrk', 'put', 'login'
- Change ConfigMap name from nginx-intel-config to nginx-config
- Remove ConfigMap from ARM deployment output
- Remove ARM-specific optimization bullet point
- Update ConfigMap verification to show only nginx-config

Author: geremyCohen

content/learning-paths/servers-and-cloud-computing/multiarch_nginx_on_aks/create-test-utility.md

@@ -44,7 +44,7 @@ In the folder you ran the curl command, you should now see the `nginx_util.sh` s
 
 The output should include usage instructions:
 ```output
-Invalid first argument. Use 'get', 'put', or 'login'.
+Invalid first argument. Use 'curl', 'wrk', 'put', or 'login'.
 ```
 
 With it working, you're now ready to deploy nginx to the Intel nodes in the cluster.

content/learning-paths/servers-and-cloud-computing/multiarch_nginx_on_aks/deploy-arm.md

@@ -24,7 +24,6 @@ kubectl apply -f arm_nginx.yaml
 You will see output similar to:
 
 ```output
-configmap/nginx-arm-config created
 deployment.apps/nginx-arm-deployment created
 service/nginx-arm-svc created
 ```
@@ -49,8 +48,6 @@ Taking a closer look at the `arm_nginx.yaml` deployment file, you'll see setting
     arch: arm
 ```
 
-* The ARM ConfigMap includes performance optimizations specific to ARM architecture, such as `worker_processes 2` and `worker_cpu_affinity 01 10` for optimal CPU core utilization.
-
 ### Verify the deployment
 
 1. Get the status of nodes, pods and services by running:
@@ -75,16 +72,15 @@ service/nginx-arm-svc     LoadBalancer   10.0.241.154   48.192.64.197   80:30082
 service/nginx-intel-svc   LoadBalancer   10.0.226.250   20.80.128.191   80:30080/TCP   9m22s
 ```
 
-You can also verify the ConfigMap was created:
+You can also verify the shared ConfigMap is available:
 
 ```bash
 kubectl get configmap -nnginx
 ```
 
 ```output
-NAME                 DATA   AGE
-nginx-arm-config     1      51s
-nginx-intel-config   1      10m
+NAME               DATA   AGE
+nginx-config       1      10m
 ```
 
 When the pods show `Running` and the service shows a valid `External IP`, you're ready to test the nginx ARM service.

content/learning-paths/servers-and-cloud-computing/multiarch_nginx_on_aks/deploy-intel.md

@@ -118,8 +118,8 @@ kubectl get configmap -nnginx
 ```
 
 ```output
-NAME                 DATA   AGE
-nginx-intel-config   1      51s
+NAME               DATA   AGE
+nginx-config       1      51s
 ```
 
 With the pods in a `Ready` state and the service showing a valid `External IP`, you're now ready to test the nginx Intel service.