Fixing typos and missing context

Deploy-ServiceProvider.md

@@ -46,7 +46,7 @@ What's needed to setup the service provider components of zMontior.
     * Scale according to number of tenants, a starting scale on a single partition is 2000 RUs. 
 * Stream Analytics
   * Configure input : storage account main logs containers
-  * Configure output : CosmosDB collection
+  * Configure output : Cosmos DB collection
   * Define the query:
     ```SQL
     SELECT

Deploy-Tenant.md

@@ -1,8 +1,8 @@
 # zMonitor
 
-## Tenant Deployment
+## Tenant \ Subscription Deployment
 
-Tenant operations monitoring is enabled through Operations Management Suite (OMS). What you monitor and report on is dependent on the solutions and agents deployed and how monitoring is configured per workload in each tenant.
+Tenant \ subscription operations monitoring is enabled through Operations Management Suite (OMS). What you monitor and report on is dependent on the solutions and agents deployed and how monitoring is configured per workload in each tenant.
 
 Monitoring is enabled using two core Azure components:
 
@@ -39,7 +39,7 @@ The overall process for tenant monitoring is:
     azureadmin: <whatever>
     azureAdminPwd: <whatever>
     ```
-    NOTE: Ensure that the omsWorkspaceName is the same as the tenant name, for example, if registered tenant name is tenant1.onmicrosoft.com, then make the omsWorkspaceName "tenant1".
+    NOTE: Ensure that the omsWorkspaceName is the same as the tenant name, for example, if registered tenant name is tenant1.onmicrosoft.com, then make the omsWorkspaceName "tenant1". The omsWorkspace name is how you uniquely identify subscriptions or tenants.
 
     1. Wait for script execution to complete (takes about 10 minutes).
 

README.md

@@ -4,7 +4,7 @@
 
 An Azure platform native monitoring solution that enables monitoring across multiple tenants or subscriptions.
 
-The primary goal is to utilize Azure native components, and deliver an as simple as possible, highly configurable and scalable, cost-effective monitoring solution. The driving force behind this solution was the need to be able to monitor Azure resources across tenants (for service providers), using Azure native tools. WHile there are many metrics and logs generated in Azure, surfacing this information across subscriptions/tenants proved challenging.
+The primary goal is to utilize Azure native components, and deliver an as simple as possible, highly configurable and scalable, cost-effective monitoring solution. The driving force behind this solution was the need to be able to monitor Azure resources across tenants (for service providers), using Azure native tools. While there are many metrics and logs generated in Azure, surfacing this information across subscriptions/tenants proved challenging.
 
 ## Solution