Updated readme for accelerator name to be consistent accross (#6)

* Update README.md

* Update README.md

* Update README.md

README.md

@@ -1,6 +1,6 @@
-# Multi-Agent -Custom Automation Engine Solution Accelerator
+# Multi-Agent: Custom Automation Engine – Solution Accelerator
 
-MENU: [**USER STORY**](#user-story) \| [**SIMPLE DEPLOY**](#quick-deploy)  \| [**SUPPORTING DOCUMENTATION**](#supporting-documentation) \|
+MENU: [**USER STORY**](#user-story) \| [**QUICK DEPLOY**](#quick-deploy)  \| [**SUPPORTING DOCUMENTATION**](#supporting-documentation) \|
 
 <h2><img src="./documentation/images/readme/userStory.png" width="64">
 <br/>
@@ -96,7 +96,7 @@ Manual Deployment differs from the ‘Quick Deploy’ option in that it will ins
 All of the necessary Azure services can be deployed using the /deploy/macae.bicep script.  This script will require the following parameters:
 
 ```
-Az login
+az login
 az account set --subscription <SUBSCRIPTION_ID>
 az group create --name <RG_NAME> --location <RG_LOCATION>
 ```
@@ -194,7 +194,7 @@ To add the identity provider, please follow the steps outlined in [Set Up Authen
 
 ### Run locally and debug
 
-To debug the solution, you can use the Cosmos and OpenAI services you have manually deployed.  To do this, you need to ensure that your Azure identity has the required permissions on the Cosmos and Open AI services. 
+To debug the solution, you can use the Cosmos and OpenAI services you have manually deployed.  To do this, you need to ensure that your Azure identity has the required permissions on the Cosmos and OpenAI services. 
 
 - For OpeAI service, you can add yourself to the ‘Cognitive Services OpenAI User’ permission in the Access Control (IAM) pane of the Azure portal.  
 - Cosmos is a little more difficult as it requires permissions be added through script.  See these examples for more information: