Refine RabbitMQ documentation for clarity and consistency

Author: madeline-underwood

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

@@ -22,4 +22,4 @@ RabbitMQ helps decouple application components, improve scalability, and increas
 
 RabbitMQ is widely used for **event-driven architectures**, **background job processing**, **microservices communication**, and **notification systems**. It integrates easily with many programming languages and platforms.
 
-Learn more from the [RabbitMQ official website](https://www.rabbitmq.com/) and the [official documentation](https://www.rabbitmq.com/documentation.html).
+Learn more from the [RabbitMQ website](https://www.rabbitmq.com/) and the [RabbitMQ documentation](https://www.rabbitmq.com/documentation.html).

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

@@ -7,7 +7,7 @@ layout: learningpathall
 ---
 
 ## Install RabbitMQ on GCP SUSE Arm64 VM
-This guide describes a **step-by-step installation of RabbitMQ** on a **Google Cloud Platform SUSE Linux Arm64 virtual machine**, using **RPM packages** for both **Erlang** and **RabbitMQ Server**.
+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.
 
 RabbitMQ needs Erlang to be installed before setting up the server.
 
@@ -19,14 +19,14 @@ RabbitMQ needs Erlang to be installed before setting up the server.
 - Outbound internet access
 
 ### Refresh system repositories
-This step updates the system’s package list so the operating system knows about the latest software available from its repositories.
+Update the system's package list to get the latest available software from repositories.
 
 ```console
 sudo zypper refresh
 ```
 
 ### Install required system utilities
-You can install the basic tools needed to download and manage packages.
+Install the basic tools needed to download and manage packages.
 
 ```console
 sudo zypper install -y curl wget gnupg tar socat logrotate
@@ -123,6 +123,10 @@ sudo rabbitmqctl set_user_tags admin administrator
 sudo rabbitmqctl set_permissions -p / admin ".*" ".*" ".*"
 ```
 
+{{% notice Warning %}}
+Replace `StrongPassword123` with a strong, unique password. For production environments, use environment variables or a secrets management system instead of hardcoding passwords.
+{{% /notice %}}
+
 **Log in to Management UI**
 
 Now, test it from outside the VM. Open a web browser on your local machine (Chrome, Firefox, Edge, etc.) and enter the following URL and credentials in the address bar:

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

@@ -1,5 +1,5 @@
 ---
-title: "RabbitMQ use case 2: WhatsApp Notification"
+title: "RabbitMQ use case 2: WhatsApp notification"
 weight: 8 
 
 ### FIXED, DO NOT MODIFY
@@ -59,7 +59,7 @@ exchange declared
 
 This creates a durable queue to persist WhatsApp notification messages until consumed.
 
-The output is similar to:
+You should see:
 ```output
 queue declared
 ```
@@ -265,3 +265,28 @@ You've implemented an asynchronous notification system using RabbitMQ with direc
 This pattern works well for targeted notifications (email, SMS, WhatsApp, push notifications) where routing needs to be simple and predictable. Each notification type routes to a dedicated queue using an exact-match routing key, providing reliable, guaranteed delivery.
 
 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
+
+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:**
+
+```console
+./rabbitmqadmin delete queue name=order.events
+./rabbitmqadmin delete queue name=whatsapp.notifications
+./rabbitmqadmin delete queue name=testqueue
+./rabbitmqadmin delete exchange name=events
+./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:**
+
+Navigate to **VPC Network > Firewall**, find the `allow-tcp-15672` rule, and select **Delete**.