Complete tech review for RabbitMQ Learning Path

Author: jasonrandrews

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/baseline.md

@@ -58,16 +58,21 @@ Interface: [::], port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0
 ```
 
 ### Download RabbitMQ admin CLI tool
-Download the rabbitmqadmin CLI tool from the local management endpoint.
+
+The `rabbitmqadmin` command is a Python script to manage and monitor RabbitMQ.
+
+Download the CLI tool from the local management endpoint to the virtual machine. You can also download and run `rabbitmqadmin` on your local computer, but you need to have `python3` installed, including `pip3`. 
 
 ```console
 curl -u guest:guest http://localhost:15672/cli/rabbitmqadmin -o rabbitmqadmin
 ```
-**Make the tool executable:**
+
+Make the tool executable:
 
 ```console
 chmod +x rabbitmqadmin
 ```
+
 ### Validate queue creation
 Create a test queue to validate write operations:
 
@@ -117,12 +122,11 @@ Confirm that the queue is empty after consumption:
 
 The output is similar to:
 ```output
-+--------------+----------+
-|     name     | messages |
-+--------------+----------+
-| jobs         | 0        |
-| order.events | 1        |
-| testqueue    | 1        |
++-----------+----------+
+|   name    | messages |
++-----------+----------+
+| testqueue | 1        |
++-----------+----------+
 ```
 
 ## What you've accomplished and what's next

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/installation.md

@@ -85,6 +85,22 @@ sudo systemctl status rabbitmq-server
 
 The service should be in an active (running) state.
 
+```output
+● rabbitmq-server.service - Open source RabbitMQ server
+     Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
+     Active: active (running) since Fri 2026-01-09 14:50:52 UTC; 3s ago
+   Main PID: 3953 (beam.smp)
+      Tasks: 53
+        CPU: 2.432s
+     CGroup: /system.slice/rabbitmq-server.service
+             ├─ 3953 /usr/lib64/erlang/erts-14.2.5/bin/beam.smp -W w -MBas ageffcbf -MHas ageffcbf -MBlmbcs 512 -MHlmbcs 512 -MMmcs 30 -pc unicode -P 1048576 -t 5000000 -stbt db -zdbbl >
+             ├─ 3967 erl_child_setup 32768
+             ├─ 4014 /usr/lib64/erlang/erts-14.2.5/bin/inet_gethost 4
+             ├─ 4015 /usr/lib64/erlang/erts-14.2.5/bin/inet_gethost 4
+             ├─ 4024 /usr/lib64/erlang/erts-14.2.5/bin/epmd -daemon
+             └─ 4077 /bin/sh -s rabbit_disk_monitor
+```
+
 ### Enable RabbitMQ management plugin
 Enable the RabbitMQ management plugin to access the web-based dashboard.
 

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/use-case1.md

@@ -95,23 +95,31 @@ These commands verify that the `events` exchange exists (type: `topic`), the `or
 The output is similar to:
 
 ```output
-+--------+-------+
-| name   | type  |
-+--------+-------+
-| events | topic |
-+--------+-------+
-
++--------------------+---------+
+|        name        |  type   |
++--------------------+---------+
+|                    | direct  |
+| amq.direct         | direct  |
+| amq.fanout         | fanout  |
+| amq.headers        | headers |
+| amq.match          | headers |
+| amq.rabbitmq.trace | topic   |
+| amq.topic          | topic   |
+| events             | topic   |
++--------------------+---------+
 +--------------+----------+
-| name         | messages |
+|     name     | messages |
 +--------------+----------+
 | order.events | 0        |
+| testqueue    | 1        |
 +--------------+----------+
-
-+--------+--------------+-------------+
-| source | destination  | routing_key |
-+--------+--------------+-------------+
-| events | order.events | order.*     |
-+--------+--------------+-------------+
++--------+--------------+--------------+
+| source | destination  | routing_key  |
++--------+--------------+--------------+
+|        | order.events | order.events |
+|        | testqueue    | testqueue    |
+| events | order.events | order.*      |
++--------+--------------+--------------+
 ```
 
 ### Install Python dependencies
@@ -226,7 +234,9 @@ When you're done testing, press Ctrl+C in the worker terminal to exit the applic
 
 ## What you've accomplished and what's next
 
-You've implemented an event-driven system using RabbitMQ with topic exchange routing, durable queues, manual acknowledgments, and fair dispatch. The Python worker processes order events asynchronously, and the wildcard routing pattern (`order.*`) allows multiple related event types to flow to the same consumer.
+You've implemented an event-driven system using RabbitMQ with topic exchange routing, durable queues, manual acknowledgments, and fair dispatch. 
+
+The Python worker processes order events asynchronously, and the wildcard routing pattern (`order.*`) allows multiple related event types to flow to the same consumer.
 
 This pattern works well for event streams where you want flexibility to add new event types without reconfiguring consumers.
 

content/learning-paths/servers-and-cloud-computing/rabbitmq-gcp/use-case2.md

@@ -7,7 +7,7 @@ layout: learningpathall
 ---
 ## WhatsApp notification with direct exchange routing
 
-In this use case, you implement an asynchronous notification workflow where RabbitMQ routes WhatsApp notification messages using a **direct exchange** with exact-match routing. A Python worker consumes and processes these messages reliably.
+In this use case, you implement an asynchronous notification workflow where RabbitMQ routes WhatsApp notification messages using a direct exchange with exact-match routing. A Python worker consumes and processes these messages reliably.
 
 ### Use case overview
 
@@ -266,14 +266,9 @@ This pattern works well for targeted notifications (email, SMS, WhatsApp, push n
 
 The key difference from Use Case 1 is the routing approach: Use Case 1 uses topic exchange with wildcard routing (`order.*`) for flexible event streams, while Use Case 2 uses direct exchange with exact routing (`whatsapp`) for targeted notifications.
 
-## Cleanup resources
+## Delete RabbitMQ resources
 
-When you're finished with this Learning Path, clean up your resources to avoid unnecessary charges:
-
-**Stop RabbitMQ workers:**
-Press Ctrl+C in each terminal running a Python worker.
-
-**Delete RabbitMQ resources:**
+When you're finished, stop the RabbitMQ workers and delete the resources. 
 
 ```console
 ./rabbitmqadmin delete queue name=order.events
@@ -283,10 +278,5 @@ Press Ctrl+C in each terminal running a Python worker.
 ./rabbitmqadmin delete exchange name=notifications
 ```
 
-**Delete the Google Cloud VM:**
-
-Navigate to **Compute Engine > VM Instances** in the Google Cloud Console, select your VM, and select **Delete**.
-
-**Delete the firewall rule:**
+When you are done, be sure to delete the Google Cloud VM and the firewall rule. 
 
-Navigate to **VPC Network > Firewall**, find the `allow-tcp-15672` rule, and select **Delete**.