Merge pull request #2735 from madeline-underwood/rabbit100

Rabbit100_final

Author: jasonrandrews

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

@@ -7,7 +7,8 @@ layout: learningpathall
 ---
 
 ## RabbitMQ baseline validation on GCP SUSE Arm64 VM
-This section validates your RabbitMQ installation on the Google Cloud SUSE Linux Arm64 virtual machine by confirming:
+
+In this section you'll validate your RabbitMQ installation on the Google Cloud SUSE Linux Arm64 virtual machine by confirming:
 
 - RabbitMQ service health
 - Management plugin availability
@@ -20,6 +21,9 @@ Verify that the RabbitMQ node is operational and healthy.
 ```console
 sudo rabbitmqctl status
 ```
+
+The command returns detailed status information. Verify that:
+
 - Node status reports RabbitMQ is running
 - No active alarms
 - Listeners are active on ports 5672 and 15672

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

@@ -7,7 +7,8 @@ layout: learningpathall
 ---
 
 ## Install RabbitMQ on GCP SUSE Arm64 VM
-This guide describes the installation of RabbitMQ on a Google Cloud Platform SUSE Linux Arm64 virtual machine using RPM packages for both Erlang and RabbitMQ Server.
+
+In this section you'll install RabbitMQ on a Google Cloud Platform SUSE Linux Arm64 virtual machine using RPM packages for both Erlang and RabbitMQ Server.
 
 RabbitMQ needs Erlang to be installed before setting up the server.
 
@@ -155,7 +156,16 @@ Replace `<VM_IP>` with the public IP of your GCP VM.
 
 If everything is configured correctly, you see a RabbitMQ login page in your browser that looks like this:
 
-![Screenshot showing the RabbitMQ management UI login interface with username and password input fields and a login button alt-txt#center](images/rabbitmq.png "RabbitMQ Login page")
+![Screenshot showing the RabbitMQ management UI login interface with username and password input fields and a login button#center](images/rabbitmq.png "RabbitMQ Login page")
+
+## What you've accomplished and what's next
+
+You've successfully installed RabbitMQ on your Google Cloud Arm64 VM with:
+- Erlang and RabbitMQ Server installed via RPM packages
+- RabbitMQ Management UI enabled and accessible
+- Administrative user configured for UI access
+
+Next, you'll validate your RabbitMQ installation and verify it's functioning correctly.
 
 This confirms that your RabbitMQ management dashboard is operational.
 

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

@@ -17,7 +17,7 @@ This pattern is useful when you need flexible, wildcard-based routing (such as `
 **Scenario:**  
 An application publishes order-related events (`order.created`, `order.updated`, etc.) to RabbitMQ. A background worker consumes these events from a queue and processes them independently.
 
-This use case shows how order-related events can be published to RabbitMQ and processed asynchronously by background workers without tightly coupling producers and consumers.
+Order-related events are published to RabbitMQ and processed asynchronously by background workers without tightly coupling producers and consumers.
 
 **Typical events include:**
 
@@ -45,7 +45,7 @@ Create a durable topic exchange to route events based on routing keys:
 
 This creates a durable topic exchange named `events` that routes messages using wildcard-based routing keys (for example, `order.*`) and survives broker restarts.
 
-You should see:
+The output is similar to:
 ```output
 exchange declared
 ```
@@ -60,7 +60,7 @@ Create a durable queue to store order-related events.
 
 This creates a durable queue for order events that guarantees messages are persisted until consumed, ensuring reliability in case of worker or broker restarts.
 
-You should see:
+The output is similar to:
 ```output
 queue declared
 ```

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

@@ -27,7 +27,7 @@ The application publishes a WhatsApp notification message to the `notifications`
 
 ### RabbitMQ topology
 
-This use case uses a direct exchange topology for exact-match routing. The `notifications` exchange (type: `direct`) routes notification messages based on exact routing key matches. The `whatsapp.notifications` queue is durable, which means it persists messages across broker restarts. The binding connects the exchange to the queue using the `whatsapp` routing key, ensuring only messages published with this exact key are routed to the queue.
+A direct exchange topology is used for exact-match routing. The `notifications` exchange (type: `direct`) routes notification messages based on exact routing key matches. The `whatsapp.notifications` queue is durable, which means it persists messages across broker restarts. The binding connects the exchange to the queue using the `whatsapp` routing key, ensuring only messages published with this exact key are routed to the queue.
 
 ### Declare RabbitMQ resources
 
@@ -44,7 +44,7 @@ Create the required exchange, queue, and binding for WhatsApp notifications.
 
 This creates a durable direct exchange named `notifications` that routes messages using exact routing keys.
 
-You should see:
+The output is similar to:
 ```output
 exchange declared
 ```
@@ -59,7 +59,7 @@ exchange declared
 
 This creates a durable queue to persist WhatsApp notification messages until consumed.
 
-You should see:
+The output is similar to:
 ```output
 queue declared
 ```