Merge pull request #87 from Particular/PhilBastian-patch-1

Grammar and wording edits

Author: irinascurtu

docs.md

@@ -9,17 +9,12 @@ The sample consists of 4 applications hosting MassTransit message producers and
 
 ![System Overview](diagram.svg "width=680")
 
-`ClientUI` application generates `PlaceOder` messages at continuous rate that trigger follow-up message flow in the other parts of the system.
+`ClientUI` application generates `PlaceOrder` messages that trigger follow-up message flows in the other parts of the system.
 
 ### Experiencing failures
 
-In the UI, press the `Run scenario` button.
-
-All consumers provide ability to change message processing failure rate by pressing <kbd>I</kbd> to increase and <kbd>D</kbd> to decrease it. Each consumer application shows a list of available commands and a summary of currently used configuration values.
-
-````
-
-For example, whenever the `Billing` consumer fails to process a message, a log entry gets printed to the command line window, and the message is moved to the `bill-order_error` queue.
+In the UI, press the `Run scenario` button. This will generate a set of `PlaceOrder` messages, configured to fail at different consumers through the showcase.
+For example, whenever the `Billing` consumer fails to process a message, the message is moved to the `bill-order_error` queue.
 
 ```code
 fail: MassTransit.ReceiveTransport[0]
@@ -30,13 +25,13 @@ fail: MassTransit.ReceiveTransport[0]
          at MassTransit.DependencyInjection.ScopeConsumerFactory`1.Send[TMessage](ConsumeContext`1 context, IPipe`1 next) in /_/src/MassTransit/DependencyInjection/DependencyInjection/ScopeConsumerFactory.cs:line 22
          at MassTransit.DependencyInjection.ScopeConsumerFactory`1.Send[TMessage](ConsumeContext`1 context, IPipe`1 next) in /_/src/MassTransit/DependencyInjection/DependencyInjection/ScopeConsumerFactory.cs:line 22
          at MassTransit.Middleware.ConsumerMessageFilter`2.MassTransit.IFilter<MassTransit.ConsumeContext<TMessage>>.Send(ConsumeContext`1 context, IPipe`1 next) in /_/src/MassTransit/Middleware/ConsumerMessageFilter.cs:line 48
-````
+```
 
 ### Handling failures with the Particular Platform
 
 #### Running the sample
 
-In order, to see how the Particular Platfrom improves the failed messages management, start the containers responsible for running the platform:
+To see how the Particular Platfrom improves failed message management, start the containers responsible for running the platform:
 
 ### **RabbitMQ**
 
@@ -63,31 +58,33 @@ Run docker command below from the `src` folder in a CLI
 docker compose -f docker-compose-base.yml -f compose-azure.yml --env-file asb.env up -d
 ```
 
-This will make the platform monitor error messages for all the consumers in the sample system. Upon failure any moved by a MassTransit consumer to an error queue will be ingest and index by the platform.
+This will make the platform monitor error messages for all the consumers in the sample system. Upon failure, any message moved by a MassTransit consumer to an error queue will be ingested by the platform.
 
 #### Inspecting failures
 
-Navigate to [http://localhost:9090](http://localhost:9090), or click the `View in ServicePulse` button to see the details on the failures ingested by the platform.
+Navigate to [http://localhost:9090](http://localhost:9090), or click the `View in ServicePulse` button to see the details on failures ingested by the platform.
 
 ![Service Pulse Dashboard](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 trype and stack trace.
+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](service-pulse-dashboard-failed-messages-groups.png "Failed messages grouping")
 
-Drilling into an existing group to see the list of individual processing failures. Clicking on any
-of the rows in the list shows detailed information on a given failed message in the headers and message body tabs.
+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.
 
 A failed message can be scheduled for reprocessing by clicking the `Retry message` button.
 
 ![Service Pulse Failed Message View](service-pulse-failed-message-view.png "Failed message details view")
 
 #### Editing messages before reprocessing
 
-Go to the details page for one of the failed messages and click the `Edit & retry` button at the top. The pop-up window shows the headers collection and the message body in two separate tabs.
+Go to the details page for one of the failed messages and click the `Edit & retry` button. The pop-up window shows the headers collection and the message body in two separate tabs.
 
 Navigate to the `Message Body` tab, change the last digit of the `orderId` value, and click "Retry" to schedule the message for reprocessing.
 
+> [!WARNING]
+> Changing or deleting header values may change or cause issues with the subsequent re-processing. It is recommended that these values are not changed if you are unsure of their purpose.
+
 ![Edit Message View](service-pulse-edit-before-retry.png "Edit & Retry view showing the message body")