fixing a few things

MashaMSFT · MashaMSFT · commit 95662ca2e4a0 · 2020-05-26T18:10:27.000-07:00
diff --git a/articles/azure-sql/database/az-cli-script-samples-content-guide.md b/articles/azure-sql/database/az-cli-script-samples-content-guide.md
@@ -60,7 +60,7 @@ The following table includes links to Azure CLI script examples for Azure SQL Ma
 | | |
 |---|---|
 | **Create a SQL Managed Instance**||
-| [Create a SQL Managed Instance](../../sql-database/scripts/sql-database-create-configure-managed-instance-cli.md)| Creates a SQL Managed instance. |
+| [Create a SQL Managed Instance](../../sql-database/scripts/sql-database-create-configure-managed-instance-cli.md)| Creates a SQL Managed Instance. |
 | **Configure Transparent Data Encryption (TDE)**||
 | [Manage Transparent Data Encryption in a SQL Managed Instance using Azure Key Vault](../../sql-database/scripts/transparent-data-encryption-byok-sql-managed-instance-cli.md)| Configures Transparent Data Encryption (TDE) in SQL Managed Instance using Azure Key Vault with various key scenarios. |
 |**Configure a failover group**||
diff --git a/articles/azure-sql/database/connect-query-dotnet-core.md b/articles/azure-sql/database/connect-query-dotnet-core.md
@@ -29,7 +29,7 @@ To complete this quickstart, you need:
 
 
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-dotnet-visual-studio.md b/articles/azure-sql/database/connect-query-dotnet-visual-studio.md
@@ -24,7 +24,7 @@ To complete this quickstart, you need:
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
 - An Azure SQL database. You can use one of these quickstarts to create and then configure a database in Azure SQL:
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-go.md b/articles/azure-sql/database/connect-query-go.md
@@ -24,7 +24,7 @@ To complete this quickstart, you need:
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
 - An Azure SQL database. You can use one of these quickstarts to create and then configure a database in Azure SQL:
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-java.md b/articles/azure-sql/database/connect-query-java.md
@@ -23,7 +23,7 @@ To complete this quickstart, you need:
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-nodejs.md b/articles/azure-sql/database/connect-query-nodejs.md
@@ -23,7 +23,7 @@ To complete this quickstart, you need:
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-php.md b/articles/azure-sql/database/connect-query-php.md
@@ -24,7 +24,7 @@ To complete this quickstart, you need:
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
 - An Azure SQL database. You can use one of these quickstarts to create and then configure a database in Azure SQL:
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-python.md b/articles/azure-sql/database/connect-query-python.md
@@ -23,7 +23,7 @@ To complete this quickstart, you need:
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio).
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-ruby.md b/articles/azure-sql/database/connect-query-ruby.md
@@ -23,7 +23,7 @@ To complete this quickstart, you need the following prerequisites:
 
 - An Azure SQL database. You can use one of these quickstarts to create and then configure a database in Azure SQL:
 
-  || SQL Database | SQL Managed instance | SQL Server in Azure VM |
+  || SQL Database | SQL Managed Instance | SQL Server in Azure VM |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/connect-query-vscode.md b/articles/azure-sql/database/connect-query-vscode.md
@@ -23,7 +23,7 @@ ms.date: 03/25/2019
 
 - An Azure SQL Database or SQL Managed Instance. You can use one of these quickstarts to create and then configure a database in Azure SQL Database:
 
-  || Single database | Managed instance |
+  || Azure SQL Database | SQL Managed Instance |
   |:--- |:--- |:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) |
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
diff --git a/articles/azure-sql/database/doc-changes-updates-release-notes.md b/articles/azure-sql/database/doc-changes-updates-release-notes.md
@@ -73,7 +73,7 @@ This table provides a quick comparison for the change in terminology:
 
 ## SQL Managed Instance - new features and known issues
 
-### SQL Managed instance H2 2019 updates
+### SQL Managed Instance H2 2019 updates
 
 - [Service-aided subnet configuration](https://azure.microsoft.com/updates/service-aided-subnet-configuration-for-managed-instance-in-azure-sql-database-available/) A secure and convenient way to manage subnet configuration where you control data traffic while SQL Managed Instance ensures the uninterrupted flow of management traffic
 - [Transparent data encryption (TDE) with Bring Your Own Key (BYOK)](https://azure.microsoft.com/updates/general-avilability-transparent-data-encryption-with-customer-managed-keys-for-azure-sql-database-managed-instance/) enables bring-your-own-key (BYOK) scenario for data protection at rest and allows organizations to separate management duties for keys and data.
@@ -86,7 +86,7 @@ The following features are enabled in SQL Managed Instance deployment model in H
   - Support for subscriptions with <a href="https://aka.ms/sql-mi-visual-studio-subscribers"> Azure monthly credit for Visual Studio subscribers </a> and increased [regional limits](../managed-instance/resource-limits.md#regional-resource-limitations).
   - Support for <a href="https://docs.microsoft.com/sharepoint/administration/deploy-azure-sql-managed-instance-with-sharepoint-servers-2016-2019"> SharePoint 2016 and SharePoint 2019 </a> and <a href="https://docs.microsoft.com/business-applications-release-notes/october18/dynamics365-business-central/support-for-azure-sql-database-managed-instance"> Dynamics 365 Business Central </a>
   - Create SQL Managed Instances with <a href="https://aka.ms/managed-instance-collation">instance-level collation</a> and <a href="https://azure.microsoft.com/updates/managed-instance-time-zone-ga/">time-zone</a> of your choice.
-  - SQL Managed instances are now protected with [built-in firewall](../managed-instance/management-endpoint-verify-built-in-firewall.md).
+  - SQL Managed nstances are now protected with [built-in firewall](../managed-instance/management-endpoint-verify-built-in-firewall.md).
   - Configure SQL Managed Instances to use [public endpoints](../managed-instance/public-endpoint-configure.md), [Proxy override](connectivity-architecture.md#connection-policy) connection to get better network performance, <a href="https://aka.ms/four-cores-sql-mi-update"> 4 vCores on Gen5 hardware generation</a> or <a href="https://aka.ms/managed-instance-configurable-backup-retention">Configure backup retention up to 35 days</a> for Point-in-time restore. [Long-term backup retention](long-term-retention-overview.md#managed-instance-support) (up to 10 years) is currently in limited public preview.  
   - New functionalities enable you to <a href="https://medium.com/@jocapc/geo-restore-your-databases-on-azure-sql-instances-1451480e90fa">geo-restore your database to another data center using PowerShell</a>, [rename database](https://azure.microsoft.com/updates/azure-sql-database-managed-instance-database-rename-is-supported/), [delete virtual cluster](../managed-instance/virtual-cluster-delete.md).
   - New built-in [Instance Contributor role](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#sql-managed-instance-contributor) enables separation of duty (SoD) compliance with security principles and compliance with enterprise standards.
@@ -168,7 +168,7 @@ GRANT EXECUTE ON master.dbo.xp_sqlagent_notify TO [login_name]
 
 ### In-memory OLTP memory limits are not applied
 
-Business Critical service-tier will not correctly apply [max memory limits for memory-optimized objects](../managed-instance/resource-limits.md#in-memory-oltp-available-space) in some cases. SQL Managed instance may enable workload to use more memory for In-memory OLTP operations, which may affect availability and stability of the instance. In-memory OLTP queries that are reaching the limits might not fail immediately. This issue will be fixed soon. The queries that use more In-memory OLTP memory will fail sooner if they reach the [limits](../managed-instance/resource-limits.md#in-memory-oltp-available-space).
+Business Critical service-tier will not correctly apply [max memory limits for memory-optimized objects](../managed-instance/resource-limits.md#in-memory-oltp-available-space) in some cases. SQL Managed Instance may enable workload to use more memory for In-memory OLTP operations, which may affect availability and stability of the instance. In-memory OLTP queries that are reaching the limits might not fail immediately. This issue will be fixed soon. The queries that use more In-memory OLTP memory will fail sooner if they reach the [limits](../managed-instance/resource-limits.md#in-memory-oltp-available-space).
 
 **Workaround:** [Monitor In-memory OLTP storage usage](https://docs.microsoft.com/azure/sql-database/sql-database-in-memory-oltp-monitor-space) using [SQL Server Management Studio](/sql/relational-databases/in-memory-oltp/monitor-and-troubleshoot-memory-usage#bkmk_Monitoring) to ensure that the workload is not using more than available memory. Increase the memory limits that depend on the number of vCores, or optimize your workload to use less memory.
  
diff --git a/articles/azure-sql/database/high-availability-sla.md b/articles/azure-sql/database/high-availability-sla.md
@@ -76,7 +76,7 @@ Because the zone redundant databases have replicas in different datacenters with
 
 > [!IMPORTANT]
 > Zone redundant databases and elastic pools are currently only supported in the Premium and Business Critical service tiers in select regions. When using the Business Critical tier, zone redundant configuration is only available when the Gen5 compute hardware is selected. For up to date information about the regions that support zone redundant databases, see [Services support by region](../../availability-zones/az-region.md).  
-> This feature is not available in Managed instance.
+> This feature is not available in SQL Managed Instance.
 
 The zone redundant version of the high availability architecture is illustrated by the following diagram:
 
diff --git a/articles/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.md b/articles/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.md
@@ -39,12 +39,12 @@ The vCore-based service tiers are differentiated based on database availability
 | **Best for** |All|Offers budget oriented balanced compute and storage options.|Most business workloads. Autoscaling storage size up to 100 TB, fast vertical and horizontal compute scaling, fast database restore.|OLTP applications with high transaction rate and low IO latency. Offers highest resilience to failures and fast failovers using multiple synchronously updated replicas.|
 |  **Resource type** ||Single database / elastic pool / managed instance | Single database | Single database / elastic pool / managed instance |
 | **Compute size**|Single database / elastic pool* | 1 to 80 vCores | 1 to 80  vCores* | 1 to 80 vCores |
-| |Managed instance | 8, 16, 24, 32, 40, 64, 80  vCores | N/A | 8, 16, 24, 32, 40, 64, 80  vCores |
+| |SQL Managed Instance | 8, 16, 24, 32, 40, 64, 80  vCores | N/A | 8, 16, 24, 32, 40, 64, 80  vCores |
 | **Storage type** | All |Premium remote storage (per instance) | De-coupled storage with local SSD cache (per instance) | Super-fast local SSD storage (per instance) |
 | **Storage size** | Single database / elastic pool *| 5 GB – 4 TB | Up to 100 TB | 5 GB – 4 TB |
-| | Managed instance  | 32 GB – 8 TB | N/A | 32 GB – 4 TB |
+| | SQL Managed Instance  | 32 GB – 8 TB | N/A | 32 GB – 4 TB |
 | **IOPS** | Single database | 500 IOPS per vCore with 7000 maximum IOPS | Hyperscale is a multi-tiered architecture with caching at multiple levels. Effective IOPS will depend on the workload. | 5000 IOPS with 200,000 maximum IOPS|
-| | Managed instance | Depends on file size | N/A | 1375 IOPS/vCore |
+| | SQL Managed Instance | Depends on file size | N/A | 1375 IOPS/vCore |
 |**Availability**|All|1 replica, no Read Scale-out, no local cache | Multiple replicas, up to 4 Read Scale-out, partial local cache | 3 replicas, 1 Read Scale-out, zone-redundant HA, full local storage |
 |**Backups**|All|RA-GRS, 7-35 day retention (7 days by default)| RA-GRS, 7 day retention, constant time point-in-time recovery (PITR) | RA-GRS, 7-35 day retention (7 days by default) |
 
diff --git a/articles/azure-sql/managed-instance/frequently-asked-questions-faq.md b/articles/azure-sql/managed-instance/frequently-asked-questions-faq.md
@@ -58,7 +58,7 @@ Expected time to create a SQL Managed Instance or change service tier (vCores, s
 
 Changing SQL Managed Instance name is not supported.
 
-SQL Managed instance default DNS zone *.database.windows.net* could be changed. 
+SQL Managed Instance default DNS zone *.database.windows.net* could be changed. 
 
 To use another DNS zone instead of the default, for example, *.contoso.com*: 
 - Use CliConfig to define an alias. The tool is just a registry settings wrapper, so it could be done using group policy or script as well.
diff --git a/articles/azure-sql/managed-instance/index.yml b/articles/azure-sql/managed-instance/index.yml
@@ -26,7 +26,7 @@ landingContent:
     linkLists:
       - linkListType: quickstart
         links:
-          - text: Create SQL Managed Intsance
+          - text: Create SQL Managed Instance
             url: instance-create-quickstart.md
       - linkListType: concept
         links:
diff --git a/articles/azure-sql/toc.yml b/articles/azure-sql/toc.yml
@@ -766,20 +766,20 @@
       items: 
       - name: Secure public endpoints
         href: managed-instance/public-endpoint-overview.md
-      - name: Managed instance auditing
+      - name: Auditing
         href: managed-instance/auditing-configure.md
 
   - name: How to
     items:
     - name: Overview
       href: managed-instance/how-to-content-reference-guide.md
-    - name: Migrate to Managed instance
+    - name: Migrate to SQL Managed Instance
       href: managed-instance/migrate-to-instance-from-sql-server.md
     - name: Customize time zone
       href: managed-instance/timezones-overview.md
     - name: Configure connection types
       href: managed-instance/connection-types-overview.md
-    - name: Migrate TDE cert to Managed instance
+    - name: Migrate TDE cert 
       href: managed-instance/tde-certificate-migrate.md
     - name: Restore to a point in time
       href: managed-instance/point-in-time-restore.md
