Added Ruben's suggestions for README.md.

Co-authored-by: Ruben Bartelink <[email protected]>

README.md

@@ -85,7 +85,7 @@ The specific behaviors carried out in reaction to incoming events often use `Equ
 
  - Specific only to Cosmos
 
- - For reactions using the same container for listening and writing to (i.e.: same source and destination)
+ - For applications where the reactions using the same Container, credentials etc as the one being Monitored by the change feed processor (simpler config wiring and less argument processing)
 
 <a name="eqxShipping"></a>
 - [`eqxShipping`](equinox-shipping/README.md) - Example demonstrating the implementation of a [Process Manager](https://www.enterpriseintegrationpatterns.com/patterns/messaging/ProcessManager.html) using [`Equinox`](https:/jet/equinox) that manages the enlistment of a set of `Shipment` Aggregate items into a separated `Container` Aggregate as an atomic operation. :pray: [@Kimserey](https:/Kimserey). _Still targets Equinox V2 atm._

propulsion-cosmos-reactor/README.md

@@ -27,11 +27,11 @@ This project was generated using:
   # default name is "($EQUINOX_COSMOS_CONTAINER)-aux"
   propulsion init -ru 400 cosmos
 
-3. To run an instance of the Projector from a CosmosDb ChangeFeed
-
-  # `-g default` defines the Projector Group identity - each id has separated state in the checkpoints store (`Sync-default` in the cited `cosmos` store)
-  # `-c $env:EQUINOX_COSMOS_CONTAINER ` specifies the source (if you have specified EQUINOX_COSMOS_* environment vars, no connection/database arguments are needed, but the monitored (source) container must be specified explicitly)
-  # `cosmos` specifies the target store for the reactions (if you have specified 3x EQUINOX_COSMOS_* environment vars, no arguments are needed)
-  dotnet run -- -g default cosmos -c $env:EQUINOX_COSMOS_CONTAINER cosmos
-
-4. To create a Consumer, use `dotnet new proConsumer` (see README therein for details)
+3. To run an instance of the Reactor from a CosmosDb ChangeFeed
+
+  # `-g default` defines the `processorName` - each processor group name has separated state in the leases store
+  # `-c MyContainer` specifies the source Container to monitor (if you have specified EQUINOX_COSMOS_* environment
+  #  vars, no connection/database/container arguments are needed.)
+  # For this template, this same container is also used to wire up the Connection used for the Reactions processing.
+  # See the `proReactor` template for a more complex variant that lets you specify them separately.
+  dotnet run -- -g default cosmos -c MyContainer