edit pass: sql-database-batch1

Author: paulth1

articles/azure-sql/database/active-geo-replication-configure-portal.md

@@ -1,6 +1,6 @@
 ---
 title: "Tutorial: Geo-replication & failover in portal"
-description: Configure geo-replication for an Azure SQL Database using the Azure portal and initiate failover.
+description: Configure geo-replication for a database using the Azure portal and initiate failover.
 services: sql-database
 ms.service: sql-database
 ms.subservice: high-availability
@@ -12,7 +12,7 @@ ms.author: sashan
 ms.reviewer: mathoma, carlrab
 ms.date: 02/13/2019
 ---
-# Tutorial: Configure active geo-replication & failover in portal (Azure SQL Database)
+# Tutorial: Configure active geo-replication and failover in the Azure portal (Azure SQL Database)
 
 This article shows you how to configure [active geo-replication for Azure SQL Database](active-geo-replication-overview.md#active-geo-replication-terminology-and-capabilities) using the [Azure portal](https://portal.azure.com) and to initiate failover.
 
@@ -27,7 +27,7 @@ To configure active geo-replication by using the Azure portal, you need the foll
 * A database in Azure SQL Database: The primary database that you want to replicate to a different geographical region.
 
 > [!Note]
-> When using Azure portal, you can only create a secondary database within the same subscription as the primary. If secondary database is required to be in a different subscription, use  [Create Database REST API](https://docs.microsoft.com/rest/api/sql/databases/createorupdate) or [ALTER DATABASE Transact-SQL API](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql).
+> When using Azure portal, you can only create a secondary database within the same subscription as the primary. If a secondary database is required to be in a different subscription, use [Create Database REST API](https://docs.microsoft.com/rest/api/sql/databases/createorupdate) or [ALTER DATABASE Transact-SQL API](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql).
 
 ## Add a secondary database
 

articles/azure-sql/database/automatic-tuning-email-notifications-configure.md

@@ -14,7 +14,7 @@ ms.date: 06/03/2019
 ---
 # Email notifications for automatic tuning
 
-Azure SQL Database tuning recommendations are generated by Azure SQL Database [Automatic tuning](automatic-tuning-overview.md). This solution continuously monitors and analyzes workloads of Azure SQL Databases providing customized tuning recommendations for each individual database related to index creation, index deletion, and optimization of query execution plans.
+Azure SQL Database tuning recommendations are generated by Azure SQL Database [Automatic tuning](automatic-tuning-overview.md). This solution continuously monitors and analyzes workloads of databases providing customized tuning recommendations for each individual database related to index creation, index deletion, and optimization of query execution plans.
 
 Azure SQL Database automatic tuning recommendations can be viewed in the [Azure portal](database-advisor-find-recommendations-portal.md), retrieved with [REST API](https://docs.microsoft.com/rest/api/sql/databaserecommendedactions/listbydatabaseadvisor) calls, or by using [T-SQL](https://azure.microsoft.com/blog/automatic-tuning-introduces-automatic-plan-correction-and-t-sql-management/) and [PowerShell](https://docs.microsoft.com/powershell/module/az.sql/get-azsqldatabaserecommendedaction) commands. This article is based on using a PowerShell script to retrieve automatic tuning recommendations.
 
@@ -30,7 +30,7 @@ The following solution automates the sending of email notifications containing A
 
 To use Azure Automation, the first step is to create an automation account and to configure it with Azure resources to use for execution of the PowerShell script. To learn more about Azure Automation and its capabilities, see [Getting started with Azure automation](https://docs.microsoft.com/azure/automation/automation-offering-get-started).
 
-Follow these steps to create Azure Automation Account through the method of selecting and configuring Automation app from the Marketplace:
+Follow these steps to create an Azure Automation Account through the method of selecting and configuring an Automation app from Azure Marketplace:
 
 1. Log into the Azure portal.
 1. Click on "**+ Create a resource**" in the upper left corner.
@@ -76,7 +76,7 @@ Follow these steps to load a PowerShell script inside the runbook created:
 
 In the header of the provided PowerShell script, you need to replace `<SUBSCRIPTION_ID_WITH_DATABASES>` with your Azure subscription ID. To learn how to retrieve your Azure subscription ID, see [Getting your Azure Subscription GUID](https://blogs.msdn.microsoft.com/mschray/20../../getting-your-azure-subscription-guid-new-portal/).
 
-In case of several subscriptions, you can add them as comma-delimited to the "$subscriptions" property in the header of the script.
+In the case of several subscriptions, you can add them as comma-delimited to the "$subscriptions" property in the header of the script.
 
 ```powershell
 # PowerShell script to retrieve Azure SQL Database Automatic tuning recommendations.
@@ -183,7 +183,7 @@ To complete the solution, as the final step, create an automation flow in Micros
 
 To learn more about Microsoft Flow capabilities, see [Getting started with Microsoft Flow](https://docs.microsoft.com/flow/getting-started).
 
-Prerequisite for this step is to sign up for [Microsoft Flow](https://flow.microsoft.com) account and to log in. Once inside the solution, follow these steps to set up a **new flow**:
+Prerequisite for this step is to sign up for a [Microsoft Flow](https://flow.microsoft.com) account and to log in. Once inside the solution, follow these steps to set up a **new flow**:
 
 1. Access "**My flows**" menu item.
 1. Inside My flows, select the "**+Create from blank**" link at the top of the page.
@@ -200,25 +200,25 @@ The next step is to add three jobs (create, get output and send email) to the ne
    - In the Create job pane, configure the job properties. For this configuration, you will need details of your Azure subscription ID, Resource Group and Automation Account **previously recorded** at the **Automation Account pane**. To learn more about options available in this section, see [Azure Automation - Create Job](https://docs.microsoft.com/connectors/azureautomation/#create-job).
    - Complete creating this action by clicking on "**Save flow**".
 
-2. Create action to retrieve output from the executed PowerShell script
+2. Create an action to retrieve output from the executed PowerShell script
 
    - Select "**+New step**", followed by "**Add an action**" inside the Recurrence flow pane
-   - In the search filed type "**automation**" and select "**Azure Automation – Get job output**" from the search results. To learn more about options available in this section, see [Azure Automation – Get job output](https://docs.microsoft.com/connectors/azureautomation/#get-job-output).
+   - In the search field type "**automation**" and select "**Azure Automation – Get job output**" from the search results. To learn more about options available in this section, see [Azure Automation – Get job output](https://docs.microsoft.com/connectors/azureautomation/#get-job-output).
    - Populate fields required (similar to creating the previous job) - populate your Azure subscription ID, Resource Group, and Automation Account (as entered in the Automation Account pane).
    - Click inside the field "**Job ID**" for the "**Dynamic content**" menu to show up. From within this menu, select the option "**Job ID**".
    - Complete creating this action by clicking on "**Save flow**".
 
-3. Create action to send out email using Office 365 integration
+3. Create an action to send out email using Office 365 integration
 
    - Select "**+New step**", followed by "**Add an action**" inside the Recurrence flow pane.
-   - In the search filed type "**send an email**" and select "**Office 365 Outlook – Send an email**" from the search results.
+   - In the search field type "**send an email**" and select "**Office 365 Outlook – Send an email**" from the search results.
    - In the "**To**" field type in the email address to which you need to send the notification email.
    - In the "**Subject**" field type in the subject of your email, for example "Automatic tuning recommendations email notification".
    - Click inside the field "**Body**" for the "**Dynamic content**" menu to show up. From within this menu, under "**Get job output**", select "**Content**".
    - Complete creating this action by clicking on "**Save flow**".
 
 > [!TIP]
-> To send automated emails to different recipients, create separate flows. In these additional flows, change the recipient email address in the "To" field, and the email subject line in the "Subject" field. Creating new runbooks in Azure Automation with customized PowerShell scripts (such as with change of Azure subscription ID) enables further customization of automated scenarios, such is for example emailing separate recipients on Automated tuning recommendations for separate subscriptions.
+> To send automated emails to different recipients, create separate flows. In these additional flows, change the recipient email address in the "To" field, and the email subject line in the "Subject" field. Creating new runbooks in Azure Automation with customized PowerShell scripts (such as with change of Azure subscription ID) enables further customization of automated scenarios, such as for example emailing separate recipients on Automated tuning recommendations for separate subscriptions.
 
 The above concludes steps required to configure the email delivery job workflow. The entire flow consisting of three actions built is shown in the following image.
 
@@ -230,7 +230,7 @@ Statistics of running the automated jobs, showing success of email notifications
 
 ![Running flow for automatic tuning email notifications](./media/automatic-tuning-email-notifications-configure/howto-email-06.png)
 
-The Flow analytics is helpful for monitoring the success of job executions, and if required for troubleshooting.  In the case of troubleshooting, you also might want to examine the PowerShell script execution log accessible through Azure Automation app.
+The Flow analytics pane is helpful for monitoring the success of job executions, and if required for troubleshooting.  In the case of troubleshooting, you also might want to examine the PowerShell script execution log accessible through the Azure Automation app.
 
 The final output of the automated email looks similar to the following email received after building and running this solution: