From 190d87f31cbd8553938fc6fa2cfcfb875a06d0d3 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 14:09:50 +0200
Subject: [PATCH 01/10] Remove mention of ServicePulse

---
 src/frontend/src/components/BillingEndpoint.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/components/BillingEndpoint.vue b/src/frontend/src/components/BillingEndpoint.vue
index ff08e99..7705b5e 100644
--- a/src/frontend/src/components/BillingEndpoint.vue
+++ b/src/frontend/src/components/BillingEndpoint.vue
@@ -128,7 +128,7 @@ function toggleFailOnRetries() {
         target="_blank"
         :href="`http://localhost:9090/#/failed-messages/message/${message.messageViewId}`"
       >
-        View failure in ServicePulse
+        View failure details
       </a>
     </template>
     <template v-else-if="isOrderBilled(message.message)">

From b12f9b33495bc64338974b1d2fc68bdd4d4bff45 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 14:12:45 +0200
Subject: [PATCH 02/10] Update SalesEndpoint.vue

---
 src/frontend/src/components/SalesEndpoint.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/components/SalesEndpoint.vue b/src/frontend/src/components/SalesEndpoint.vue
index 25037c3..06eb9fe 100644
--- a/src/frontend/src/components/SalesEndpoint.vue
+++ b/src/frontend/src/components/SalesEndpoint.vue
@@ -112,7 +112,7 @@ function toggleFailOnRetries() {
       <a
         target="_blank"
         :href="`http://localhost:9090/#/failed-messages/message/${message.messageViewId}`"
-        >View failure in ServicePulse</a
+        >View failure details</a
       >
     </template>
     <template v-else-if="isOrderPlaced(message.message)">

From d6fcb59e4b2985f5e1c1cf13a96c2bc6f9f6304c Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 14:13:20 +0200
Subject: [PATCH 03/10] Update ShippingEndpoint.vue

---
 src/frontend/src/components/ShippingEndpoint.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/components/ShippingEndpoint.vue b/src/frontend/src/components/ShippingEndpoint.vue
index 7d14d2a..36abacf 100644
--- a/src/frontend/src/components/ShippingEndpoint.vue
+++ b/src/frontend/src/components/ShippingEndpoint.vue
@@ -149,7 +149,7 @@ function toggleFailOnRetries() {
         target="_blank"
         :href="`http://localhost:9090/#/failed-messages/message/${message.messageViewId}`"
       >
-        View failure in ServicePulse
+        View failure details
       </a>
     </template>
     <template v-else>

From 0679b6b4528ded66ffe910ea7b9df0424032fcc9 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 16:53:49 +0200
Subject: [PATCH 04/10] The detailed list of containers probably isn't needed
 in the Readme

---
 README.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/README.md b/README.md
index f8169d3..0453e6c 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,6 @@ This showcase consists of 4 processes hosting MassTransit message producers and
 
 ## Launching the Showcase in Docker
 
-The showcase requires a connection to a broker (by default RabbitMQ), [ServiceControl](https://hub.docker.com/r/particular/servicecontrol) container, [ServicePulse](https://hub.docker.com/r/particular/servicepulse) container and the [MassTransit Connector for ServiceControl](https://hub.docker.com/r/particular/servicecontrol-masstransit-connector) container.  
 To help getting started we have created a few docker compose files that orchestrate all this setup for you.
 
 Run the docker command below from the `src` folder in a terminal.

From 82f7cf5a86aee296cc3c5af251568e905ef41c12 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 17:02:58 +0200
Subject: [PATCH 05/10] Update README.md

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0453e6c..f1236de 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,9 @@ This showcase consists of 4 processes hosting MassTransit message producers and
 
 To help getting started we have created a few docker compose files that orchestrate all this setup for you.
 
-Run the docker command below from the `src` folder in a terminal.
+* First, make sure you've pulled down the repository to your machine.
+* Second, open a terminal and navigate to the `src` folder in your local copy of the repository.
+* Third, run the following command:
 
 ```cmd
 docker compose -p particular-platform-showcase -f docker-compose-base.yml -f compose-rabbitmq.yml --env-file rabbit.env up -d

From b9421c80aab197547217a0b5da6badb14e8bca09 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 17:04:32 +0200
Subject: [PATCH 06/10] Update README.md

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f1236de..8d7c86d 100644
--- a/README.md
+++ b/README.md
@@ -69,7 +69,9 @@ Run the solution to start the demo.
 
 ## Opening the showcase UI
 
-Navigate to http://localhost:61335/ to see the UI. Click `Run Scenario` to start the showcase scenario and generate some simulated message handling failures.
+Navigate to http://localhost:61335/ to see the UI.
+
+Click `Run Scenario` to send some messages and generate some simulated failures.
 
 ## Handling failures with the Particular Platform
 

From 5c90e2e52fc592d18db9354f3590ed5322896001 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 17:07:12 +0200
Subject: [PATCH 07/10] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8d7c86d..0aa0df6 100644
--- a/README.md
+++ b/README.md
@@ -77,7 +77,7 @@ Click `Run Scenario` to send some messages and generate some simulated failures.
 
 ### Inspecting failures
 
-Navigate to [http://localhost:9090](http://localhost:9090) in a new tab, or click the `View in ServicePulse` button, to see the details on failures ingested by the platform.
+Navigate to [http://localhost:9090](http://localhost:9090) in a new tab, or click the `View Failures` button, to see the details on failures ingested by the platform.
 
 ![Service Pulse Dashboard](docs/service-pulse-dashboard-failed-messages.png "Message processing errors summary view")
 

From cedf7fbb37ca0fdf504cc3521dac372e6968659a Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 17:08:13 +0200
Subject: [PATCH 08/10] Remove unnecessary mention of ServicePulse

---
 src/frontend/src/components/ClientEndpoint.vue | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/components/ClientEndpoint.vue b/src/frontend/src/components/ClientEndpoint.vue
index 2029ca9..9f117bb 100644
--- a/src/frontend/src/components/ClientEndpoint.vue
+++ b/src/frontend/src/components/ClientEndpoint.vue
@@ -71,7 +71,7 @@ async function runScenario() {
       </button>
       <a target="_blank" href="http://localhost:9090/#/failed-messages/">
         <button type="button" class="secondary view-servicepulse">
-          View Failures in ServicePulse
+          View Failures
         </button>
       </a>
       <span class="note">

From 44081d78dfaee91dbce95e41af37953da7d6e991 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Sun, 2 Feb 2025 17:13:28 +0200
Subject: [PATCH 09/10] Update README.md

---
 README.md | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 0aa0df6..754bfae 100644
--- a/README.md
+++ b/README.md
@@ -73,19 +73,17 @@ Navigate to http://localhost:61335/ to see the UI.
 
 Click `Run Scenario` to send some messages and generate some simulated failures.
 
-## Handling failures with the Particular Platform
-
-### Inspecting failures
+## Managing errors
 
 Navigate to [http://localhost:9090](http://localhost:9090) in a new tab, or click the `View Failures` button, to see the details on failures ingested by the platform.
 
-![Service Pulse Dashboard](docs/service-pulse-dashboard-failed-messages.png "Message processing errors summary view")
+![Dashboard](docs/service-pulse-dashboard-failed-messages.png "Message processing errors summary view")
 
 ### Scheduling message reprocessing
 
 Click on the "Failed Messages" button at the top of the page to see all failed messages ingested by the platform, grouped by the exception type and stack trace.
 
-![Service Pulse Failed Messages](docs/service-pulse-dashboard-failed-messages-groups.png "Failed messages grouping")
+![Failed Messages](docs/service-pulse-dashboard-failed-messages-groups.png "Failed messages grouping")
 
 Drill into an existing group to see the list of individual processing failures. Clicking on any of the rows in the list shows detailed information of a given failed message in the headers and message body tabs.
 
@@ -94,7 +92,7 @@ A failed message can be scheduled for reprocessing by clicking the `Retry messag
 > [!NOTE]
 > It may take several seconds after retrying a message for it to appear again in the consumer's input queue
 
-![Service Pulse Failed Message View](docs/service-pulse-failed-message-view.png "Failed message details view")
+![Failed Message View](docs/service-pulse-failed-message-view.png "Failed message details view")
 
 ### Editing messages before reprocessing
 
@@ -109,11 +107,11 @@ Navigate to the `Message Body` tab and change some of the contents of the messag
 
 ### Viewing retries
 
-Return to the showcase UI to see that the retries have now been successfully handled.
+Return to the Showcase UI to see that the retries have now been successfully handled.
 
 ### Troubleshooting
 
 Having issues?
 
 - Check logs in docker. Ensure that there are no port clashes with existing containers or services on your machine.
-- Ask any questions on [our forum](https://discuss.particular.net/tag/masstransit)
+- Ask any questions you may have on [our forum](https://discuss.particular.net/tag/masstransit)

From 84641a353d3f1c6a978431b516daadb5319faee4 Mon Sep 17 00:00:00 2001
From: Udi Dahan <udidahan@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:09:10 +0200
Subject: [PATCH 10/10] Put the list of the containers at the bottom under the
 troubleshooting section

---
 README.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/README.md b/README.md
index 754bfae..70377c6 100644
--- a/README.md
+++ b/README.md
@@ -114,4 +114,9 @@ Return to the Showcase UI to see that the retries have now been successfully han
 Having issues?
 
 - Check logs in docker. Ensure that there are no port clashes with existing containers or services on your machine.
+- Check that all containers are running:
+  - RabbitMQ
+  - [ServicePulse](https://hub.docker.com/r/particular/servicepulse)
+  - [ServiceControl](https://hub.docker.com/r/particular/servicecontrol)
+  - [MassTransit Connector for ServiceControl](https://hub.docker.com/r/particular/servicecontrol-masstransit-connector)
 - Ask any questions you may have on [our forum](https://discuss.particular.net/tag/masstransit)