Replace 'nginx_util.sh get' with 'nginx_util.sh curl' throughout tutorial

Author: geremyCohen

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

@@ -125,13 +125,13 @@ With the pods in a `Ready` state and the service showing a valid `External IP`,
 4. Run the following to make an HTTP request to the Intel nginx service:
 
 ```bash
-./nginx_util.sh get intel
+./nginx_util.sh curl intel
 ```
 
 You get back the HTTP response, as well as information about which pod served it:
 
 ```output
-Using service endpoint 20.3.71.69 for get on intel service
+Using service endpoint 20.3.71.69 for curl on intel service
 Response:
 {
   "message": "nginx response",

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

@@ -14,7 +14,7 @@ Now that you have your Intel nginx deployment running, you'll create a utility s
 
 The `nginx_util.sh` script provides three main functions:
 
-- **`get intel|arm|multiarch`** - Test nginx services and show which pod served the request
+- **`curl intel|arm|multiarch`** - Test nginx services and show which pod served the request
 - **`put btop`** - Install btop monitoring tool on all pods
 - **`login intel|arm`** - Interactive bash access to architecture-specific pods
 

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

@@ -95,13 +95,13 @@ When the pods show `Running` and the service shows a valid `External IP`, you're
 2. Run the following to make an HTTP request to the ARM nginx service using the script you created earlier:
 
 ```bash
-./nginx_util.sh get arm
+./nginx_util.sh curl arm
 ```
 
 You get back the HTTP response, as well as information about which pod served it:
 
 ```output
-Using service endpoint 48.192.64.197 for get on arm service
+Using service endpoint 48.192.64.197 for curl on arm service
 Response:
 {
   "message": "nginx response",
@@ -119,8 +119,8 @@ If you see output similar to above, you have successfully added ARM nodes to you
 Now you can test both architectures and compare their responses:
 
 ```bash
-./nginx_util.sh get intel
-./nginx_util.sh get arm
+./nginx_util.sh curl intel
+./nginx_util.sh curl arm
 ```
 
 Each command will route to its respective architecture-specific service, allowing you to compare performance and verify that your multi-architecture cluster is working correctly.

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

@@ -60,13 +60,13 @@ nginx-multiarch-svc   10.244.0.21:80,10.244.1.1:80   47s
 4. Run the following to make HTTP requests to the multiarch nginx service:
 
 ```bash
-./nginx_util.sh get multiarch
+./nginx_util.sh curl multiarch
 ```
 
 You get back the HTTP response from one of the available pods:
 
 ```output
-Using service endpoint 20.99.208.140 for get on multiarch service
+Using service endpoint 20.99.208.140 for curl on multiarch service
 Response:
 {
   "message": "nginx response",
@@ -80,9 +80,9 @@ Served by: nginx-arm-deployment-5bf8df95db-wznff
 5. Run the command multiple times to see load balancing across architectures:
 
 ```bash
-./nginx_util.sh get multiarch
-./nginx_util.sh get multiarch
-./nginx_util.sh get multiarch
+./nginx_util.sh curl multiarch
+./nginx_util.sh curl multiarch
+./nginx_util.sh curl multiarch
 ```
 
 The responses will show requests being served by different architecture deployments (intel or arm), demonstrating that the multiarch service distributes load across all available pods.
@@ -91,8 +91,8 @@ The responses will show requests being served by different architecture deployme
 
 Now you can compare the behavior:
 
-- **Architecture-specific**: `./nginx_util.sh get intel` always routes to Intel pods
-- **Architecture-specific**: `./nginx_util.sh get arm` always routes to ARM pods
-- **Multiarch**: `./nginx_util.sh get multiarch` routes to any available pod
+- **Architecture-specific**: `./nginx_util.sh curl intel` always routes to Intel pods
+- **Architecture-specific**: `./nginx_util.sh curl arm` always routes to ARM pods
+- **Multiarch**: `./nginx_util.sh curl multiarch` routes to any available pod
 
 This multiarch service provides high availability and load distribution across your entire multi-architecture cluster.