Updated READMEs for clarity; Updated application architecture image to show workflows

Author: rross

README.md

@@ -16,9 +16,7 @@ Scenarios currently implemented include
 * List Investments - shows a list of accounts and their current balances
 * Close Investment Account - closes an investment account
 
-There are two ways to run through the scenarios with the Temporal version
-* Using a [Web Application](src/frontend/README.md) or 
-* Using a [Console Application](src/temporal_supervisor/README.md)
+You can run through the scenarios with the Temporal version using a [Web Application](src/frontend/README.md) or
 
 ## Prerequisites
 

images/application-architecture.png

@@ -59,7 +59,7 @@ In a new terminal / shell run the following command:
 redis-server
 ```
 
-By default it expects to find Redis running locally. You can override the location of redis
+By default, the application expects to find Redis running locally. You can override the location of redis
 by setting the environment variables:
 
 ```bash
@@ -98,6 +98,9 @@ redis-server
 Note that the application assumes you only have one Redis server that is used by the application for storing the 
 conversation history and is also used if Claim Check has been enabled. 
 
+Be aware that using a claim check pattern introduces performance costs by doing remote calls to Redis for every payload. 
+Also, make sure your Redis implementation is rock solid as any downtime will directly affect your workflows. 
+
 ## Run Codec Server for Claim Check (optional)
 If you have decided to set up the Claim Check above, you will 
 most likely want to also run a Codec Server to be able to see the actual sent to