Apply suggestions from code review

Co-Authored-By: Sneha Gunda <[email protected]>

Author: markjbrown

articles/cosmos-db/TOC.yml

@@ -867,7 +867,7 @@
       - name: Find request unit charge
         displayName: request units, RUs, RU, charge, consumption
         href: find-request-unit-charge.md
-      - name: Scale up-down using Azure Functions Timer
+      - name: Scale using Azure Functions timer
         displayName: request units, RUs, RU, timer
         href: scale-on-schedule.md
     - name: Work with containers and items

articles/cosmos-db/index.yml

@@ -152,7 +152,7 @@ landingContent:
             url: how-to-provision-container-throughput.md
           - text: Get the request unit charges 
             url: find-request-unit-charge.md
-          - text: Scale using Azure Functions Timer
+          - text: Scale using Azure Functions timer
             url: scale-on-schedule.md
 
   # Card

articles/cosmos-db/scale-on-schedule.md

@@ -1,5 +1,5 @@
 ---
-title: Scale Azure Cosmos DB on a schedule
+title: Scale Azure Cosmos DB on a schedule by using Azure Functions timer
 description: Learn how to scale changes in throughput in Azure Cosmos DB using PowerShell and Azure Functions.
 author: markjbrown
 ms.service: cosmos-db
@@ -8,18 +8,19 @@ ms.date: 01/07/2020
 ms.author: mjbrown
 ---
 
-# Scale Azure Cosmos DB using Azure Functions Timer Trigger
+# Scale Azure Cosmos DB throughput by using Azure Functions Timer trigger
 
-Azure Cosmos DB performance is based on the amount of provisioned throughput expressed in Request Units per second (RU/s). The provisioning is at a second granularity and is billed based upon the highest RU/s per hour. This provisioned capacity model enables the service to provide a predictable and consistent throughput, guaranteed low latency, and high availability. In most production workloads this is necessary. However, in development and testing environments where Cosmos is only used during working hours, Cosmos can be scaled up in the morning and scaled back down in the evening after working hours.
 
-Throughput can be set via [Azure Resource Manager (ARM) Templates](resource-manager-samples.md), [Azure CLI](cli-samples.md), [PowerShell](powershell-samples-sql.md), or for Core (SQL) API accounts, using the Cosmos SDK. The benefit for using ARM Templates, Azure CLI or PowerShell is they support all Cosmos DB model APIs.
+The performance of an Azure Cosmos account is based on the amount of provisioned throughput expressed in Request Units per second (RU/s). The provisioning is at a second granularity and is billed based upon the highest RU/s per hour. This provisioned capacity model enables the service to provide a predictable and consistent throughput, guaranteed low latency, and high availability. Most production workloads these features. However, in development and testing environments where Azure Cosmos DB is only used during working hours, you can scale up the throughput in the morning and scale back down in the evening after working hours.
 
-## Azure Cosmos DB throughput scheduler sample project
+You can set the throughput via [Azure Resource Manager (ARM) Templates](resource-manager-samples.md), [Azure CLI](cli-samples.md), and [PowerShell](powershell-samples-sql.md), for Core (SQL) API accounts, or by using the language-specific Azure Cosmos DB SDKs. The benefit of using ARM Templates, Azure CLI or PowerShell is that they support all Azure Cosmos DB model APIs.
 
-To simplify the process for scaling Azure Cosmos DB on a schedule we've created a sample project, [Azure Cosmos Throughput Scheduler](https://github.com/Azure-Samples/azure-cosmos-throughput-scheduler). This project is an Azure Functions app with two Timer Triggers, ScaleUpTrigger and ScaleDownTrigger. The triggers run a PowerShell script that set the throughput on each resource defined in the `scale.json` file in each trigger. The ScaleUpTrigger is configured to run at 8am UTC and the ScaleDownTrigger is configured to run at 6pm UTC and can be easily changed in the `function.json` for each trigger.
+## Throughput scheduler sample project
 
-This project can be cloned locally, modified to specify the Azure Cosmos DB resources to scale up and down and the schedule to run. Then deployed in an Azure subscription and secured using Managed Service Identity with [Role-based Access Control](role-based-access-control.md) (RBAC) permissions using the Cosmos DB Operator role to set throughput on your Azure Cosmos accounts.
+To simplify the process to scale Azure Cosmos DB on a schedule we've created a sample project called [Azure Cosmos throughput scheduler](https://github.com/Azure-Samples/azure-cosmos-throughput-scheduler). This project is an Azure Functions app with two timer triggers- "ScaleUpTrigger" and "ScaleDownTrigger". The triggers run a PowerShell script that sets the throughput on each resource as defined in the `scale.json` file in each trigger. The ScaleUpTrigger is configured to run at 8 AM UTC and the ScaleDownTrigger is configured to run at 6 PM UTC and these times can be easily updated within the `function.json` file for each trigger.
+
+You can clone this project locally, modify it to specify the Azure Cosmos DB resources to scale up and down and the schedule to run. Later you can deploy it in an Azure subscription and secure it using managed service identity with [Role-based Access Control](role-based-access-control.md) (RBAC) permissions with the "Azure Cosmos DB operator" role to set throughput on your Azure Cosmos accounts.
 
 ## Next Steps
 
-- Learn more and download sample, [Azure Cosmos Throughput Scheduler](https://github.com/Azure-Samples/azure-cosmos-throughput-scheduler).
+- Learn more and download the sample from [Azure Cosmos DB throughput scheduler](https://github.com/Azure-Samples/azure-cosmos-throughput-scheduler).