fixes per reviewer

Author: Ja-Dunn

articles/azure-sql/database/develop-overview.md

@@ -14,7 +14,7 @@ ms.custom: sqldbrb=2
 # Application development overview - SQL Database & SQL Managed Instance 
 [!INCLUDE[appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
 
-This article walks through the basic considerations that a developer should be aware of when writing code to connect to your database in Azure. This article applies to Azure SQL Database, and Azure SQL Managed Instance
+This article walks through the basic considerations that a developer should be aware of when writing code to connect to your database in Azure. This article applies to Azure SQL Database, and Azure SQL Managed Instance.
 
 ## Language and platform
 
@@ -24,7 +24,7 @@ You can leverage open-source tools like [cheetah](https://github.com/wunderlist/
 
 ## Authentication
 
-Access to Azure SQL Database is protected with logins and firewalls. Azure SQL Database supports both SQL Server and [Azure Active Directory (AAD) authentication](authentication-aad-overview.md) users and logins. AAD logins are available only in SQL Managed Instance. 
+Access to Azure SQL Database is protected with logins and firewalls. Azure SQL Database supports both SQL Server and [Azure Active Directory authentication](authentication-aad-overview.md) users and logins. Azure Active Directory logins are available only in SQL Managed Instance. 
 
 Learn more about [managing database access and login](logins-create-manage.md).
 
@@ -40,7 +40,7 @@ Avoid long-running transactions because any infrastructure or connection failure
 
 Azure SQL Database is a cloud service where you might expect transient errors that happen in the underlying infrastructure or in the communication between cloud entities. Although Azure SQL Database is resilient on the transitive infrastructure failures, these failures might affect your connectivity. When a transient error occurs while connecting to SQL Database, your code should [retry the call](troubleshoot-common-connectivity-issues.md). We recommend that retry logic use backoff logic, so that it does not overwhelm the SQL database with multiple clients retrying simultaneously. Retry logic depends on the [error messages for SQL Database client programs](troubleshoot-common-errors-issues.md).
 
-For more information about how to prepare for planned maintenance events on your Azure SQL database, see [planning for Azure maintenance events in Azure SQL Database](planned-maintenance.md).
+For more information about how to prepare for planned maintenance events on your Azure SQL Database, see [planning for Azure maintenance events in Azure SQL Database](planned-maintenance.md).
 
 ## Network considerations
 

articles/azure-sql/database/disaster-recovery-guidance.md

@@ -12,7 +12,7 @@ ms.author: sashan
 ms.reviewer: mathoma, carlrab
 ms.date: 06/21/2019
 ---
-# Restore an Azure SQL database or failover to a secondary
+# Restore your Azure SQL Database or failover to a secondary
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
 Azure SQL Database offers the following capabilities for recovering from an outage:

articles/azure-sql/database/vnet-service-endpoint-rule-overview.md

@@ -58,7 +58,7 @@ The roles of Network Admin and Database Admin have more capabilities than are ne
 You have the option of using [role-based access control (RBAC)][rbac-what-is-813s] in Azure to create a single custom role that has only the necessary subset of capabilities. The custom role could be used instead of involving either the Network Admin or the Database Admin. The surface area of your security exposure is lower if you add a user to a custom role, versus adding the user to the other two major administrator roles.
 
 > [!NOTE]
-> In some cases the Azure SQL database and the VNet-subnet are in different subscriptions. In these cases you must ensure the following configurations:
+> In some cases the database in Azure SQL Database and the VNet-subnet are in different subscriptions. In these cases you must ensure the following configurations:
 >
 > - Both subscriptions must be in the same Azure Active Directory tenant.
 > - The user has the required permissions to initiate operations, such as enabling service endpoints and adding a VNet-subnet to the given Server.
@@ -68,7 +68,7 @@ You have the option of using [role-based access control (RBAC)][rbac-what-is-813
 
 For Azure SQL Database, the virtual network rules feature has the following limitations:
 
-- In the firewall for your Azure SQL database, each virtual network rule references a subnet. All these referenced subnets must be hosted in the same geographic region that hosts the Azure SQL database.
+- In the firewall for your database in Azure SQL Database, each virtual network rule references a subnet. All these referenced subnets must be hosted in the same geographic region that hosts the Azure SQL database.
 
 - Each server can have up to 128 ACL entries for any given virtual network.
 
@@ -176,7 +176,7 @@ Blob auditing pushes audit logs to your own storage account. If this storage acc
 
 ## Adding a VNet Firewall rule to your server without turning On VNet Service Endpoints
 
-Long ago, before this feature was enhanced, you were required to turn VNet service endpoints On before you could implement a live VNet rule in the Firewall. The endpoints related a given VNet-subnet to an Azure SQL database. But now as of January 2018, you can circumvent this requirement by setting the **IgnoreMissingVNetServiceEndpoint** flag.
+Long ago, before this feature was enhanced, you were required to turn VNet service endpoints On before you could implement a live VNet rule in the Firewall. The endpoints related a given VNet-subnet to a database in Azure SQL Database. But now as of January 2018, you can circumvent this requirement by setting the **IgnoreMissingVNetServiceEndpoint** flag.
 
 Merely setting a Firewall rule does not help secure the server. You must also turn VNet service endpoints On for the security to take effect. When you turn service endpoints On, your VNet-subnet experiences downtime until it completes the transition from Off to On. This is especially true in the context of large VNets. You can use the **IgnoreMissingVNetServiceEndpoint** flag to reduce or eliminate the downtime during transition.
 
@@ -206,7 +206,7 @@ Connection error 40914 relates to *virtual network rules*, as specified on the F
 
 ## Portal can create a virtual network rule
 
-This section illustrates how you can use the [Azure portal][http-azure-portal-link-ref-477t] to create a *virtual network rule* in your Azure SQL database. The rule tells your database to accept communication from a particular subnet that has been tagged as being a *Virtual Network service endpoint*.
+This section illustrates how you can use the [Azure portal][http-azure-portal-link-ref-477t] to create a *virtual network rule* in your database in Azure SQL Database. The rule tells your database to accept communication from a particular subnet that has been tagged as being a *Virtual Network service endpoint*.
 
 > [!NOTE]
 > If you intend to add a service endpoint to the VNet firewall rules of your server, first ensure that service endpoints are turned On for the subnet.

articles/azure-sql/database/xevent-code-event-file.md

@@ -237,7 +237,7 @@ The script starts with commands to clean up after a possible previous run, and i
 The PowerShell script printed a few named values when it ended. You must edit the Transact-SQL script to use those values. Find **TODO** in the Transact-SQL script to locate the edit points.
 
 1. Open SQL Server Management Studio (ssms.exe).
-2. Connect to your Azure SQL database.
+2. Connect to your database in Azure SQL Database.
 3. Click to open a new query pane.
 4. Paste the following Transact-SQL script into the query pane.
 5. Find every **TODO** in the script and make the appropriate edits.