fixing toc

MashaMSFT · MashaMSFT · commit 3d1be6b4af65 · 2020-05-21T10:42:33.000-07:00
diff --git a/articles/azure-sql/multi-model-features.md b/articles/azure-sql/multi-model-features.md
@@ -19,8 +19,8 @@ Multi-model databases enable you to store and work with data represented in mult
 
 ## When to use multi-model capabilities
 
-[Azure SQL family of services](azure-sql-iaas-vs-paas-what-is-overview.md) are designed to work with the relational model that provides the best performance in the most of the cases for a variety of general-purpose applications. However, the Azure SQL family of services are not limited to relational-data only. The Azure SQL family of services enable you to use a variety of non-relational formats that are tightly integrated into the relational model.
-You should consider using multi-model capabilities of the Azure SQL family of services in the following cases:
+The [Azure SQL family of products](azure-sql-iaas-vs-paas-what-is-overview.md) are designed to work with the relational model that provides the best performance in the most of the cases for a variety of general-purpose applications. However, the Azure SQL family of products are not limited to relational-data only. The Azure SQL family of products enable you to use a variety of non-relational formats that are tightly integrated into the relational model.
+You should consider using multi-model capabilities of the Azure SQL family of products in the following cases:
 
 - You have some information or structures that are better fit for NoSQL models and you don't want to use separate NoSQL database.
 - A majority of your data is suitable for relational model, and you need to model some parts of your data in NoSQL style.
@@ -29,22 +29,22 @@ You should consider using multi-model capabilities of the Azure SQL family of se
 
 ## Overview
 
-The Azure SQL family of services provide the following multi-model features:
+The Azure SQL family of products provide the following multi-model features:
 
 - [Graph features](#graph-features) enable you to represent your data as set of nodes and edges, and use standard Transact-SQL queries enhanced with graph `MATCH` operator to query the graph data.
 - [JSON features](#json-features) enable you to put JSON documents in tables, transform relational data to JSON documents and vice versa. You can use the standard Transact-SQL language enhanced with JSON functions for parsing documents, and use non clustered indexes, columnstore indexes, or memory-optimized tables, to optimize your queries.
 - [Spatial features](#spatial-features) enables you to store geographical and geometrical data, index them using the spatial indexes, and retrieve the data using spatial queries.
-- [XML features](#xml-features) enable you to store and index XML data in your database and use native XQuery/XPath operations to work with XML data. The Azure SQL family of services have a specialized built-in XML query engine that process XML data.
+- [XML features](#xml-features) enable you to store and index XML data in your database and use native XQuery/XPath operations to work with XML data. The Azure SQL family of products have a specialized built-in XML query engine that process XML data.
 - [Key-value pairs](#key-value-pairs) are not explicitly supported as special features since key-value pairs can be natively modeled as two-column tables.
 
   > [!Note]
   > You can use JSON Path expression, XQuery/XPath expressions, spatial functions, and graph-query expressions in the same Transact-SQL query to access any data that you stored in the database. Also, any tool or programming language that can execute Transact-SQL queries, can also use that query interface to access multi-model data. This is the key difference compared to the multi-model databases such as [Azure Cosmos DB](/azure/cosmos-db/) that provides specialized API for different data models.
 
-In the following sections, you can learn about the most important multi-model capabilities of the Azure SQL family of services .
+In the following sections, you can learn about the most important multi-model capabilities of the Azure SQL family of products .
 
 ## Graph features
 
-The Azure SQL family of services offer graph database capabilities to model many-to-many relationships in database. A graph is a collection of nodes (or vertices) and edges (or relationships). A node represents an entity (for example, a person or an organization) and an edge represents a relationship between the two nodes that it connects (for example, likes or friends). Here are some features that make a graph database unique:
+The Azure SQL family of products offer graph database capabilities to model many-to-many relationships in database. A graph is a collection of nodes (or vertices) and edges (or relationships). A node represents an entity (for example, a person or an organization) and an edge represents a relationship between the two nodes that it connects (for example, likes or friends). Here are some features that make a graph database unique:
 
 - Edges or relationships are first class entities in a Graph Database and can have attributes or properties associated with them.
 - A single edge can flexibly connect multiple nodes in a Graph Database.
@@ -63,12 +63,12 @@ There is nothing a graph database can achieve, which cannot be achieved using a
 
 ## JSON features
 
-The Azure SQL family of services let you parse and query data represented in JavaScript Object Notation [(JSON)](https://www.json.org/) format, and export your relational data as JSON text.
+The Azure SQL family of products let you parse and query data represented in JavaScript Object Notation [(JSON)](https://www.json.org/) format, and export your relational data as JSON text.
 
 JSON is a popular data format used for exchanging data in modern web and mobile applications. JSON is also used for storing semi-structured data in log files or in NoSQL databases like [Azure Cosmos DB](https://azure.microsoft.com/services/cosmos-db/). Many REST web services return results formatted as JSON text or accept data formatted as JSON. Most Azure services such as [Azure Cognitive Search](https://azure.microsoft.com/services/search/), [Azure Storage](https://azure.microsoft.com/services/storage/), and [Azure Cosmos DB](https://azure.microsoft.com/services/cosmos-db/) have REST endpoints that return or consume JSON.
 
 
-The Azure SQL family of services let you work with JSON data easily and integrate your database with modern services, and provides the following functions for working with JSON data:
+The Azure SQL family of products let you work with JSON data easily and integrate your database with modern services, and provides the following functions for working with JSON data:
 
 ![JSON Functions](./media/multi-model-features/image_1.png)
 
@@ -90,19 +90,19 @@ Document models can be used instead of the relational models in some specific sc
 
 Spatial data represents information about the physical location and shape of geometric objects. These objects can be point locations or more complex objects such as countries/regions, roads, or lakes.
 
-The Azure SQL family of services let you parse and query data represented in JavaScript Object Notation [(JSON)](https://www.json.org/) format, and export your relational data as JSON text.
+The Azure SQL family of products let you parse and query data represented in JavaScript Object Notation [(JSON)](https://www.json.org/) format, and export your relational data as JSON text.
 
 
  The two supported two spatial data types: 
 
 - The geometry type represents data in a Euclidean (flat) coordinate system.
 - The geography type represents data in a round-earth coordinate system.
 
-There are a number of Spatial objects that can be used in the Azure SQL family of services let you parse and query data represented in JavaScript Object Notation [(JSON)](https://www.json.org/) format, and export your relational data as JSON text.
+There are a number of Spatial objects that can be used in the Azure SQL family of products let you parse and query data represented in JavaScript Object Notation [(JSON)](https://www.json.org/) format, and export your relational data as JSON text.
 such as [Point](/sql/relational-databases/spatial/point), [LineString](/sql/relational-databases/spatial/linestring),
 [Polygon](/sql/relational-databases/spatial/polygon), and so on.
 
-The Azure SQL family of services also provide specialized [Spatial indexes](/sql/relational-databases/spatial/spatial-indexes-overview) that can be used to improve performance of your spatial queries.
+The Azure SQL family of products also provide specialized [Spatial indexes](/sql/relational-databases/spatial/spatial-indexes-overview) that can be used to improve performance of your spatial queries.
 
 [Spatial support](/sql/relational-databases/spatial/spatial-data-sql-server) is a core SQL Server database engine feature.
 
@@ -129,7 +129,7 @@ Document models can be used instead of the relational models in some specific sc
 
 ## Key-value pairs
 
-The Azure SQL family of services don't have specialized types or structures that support key-value pairs since key-value structures can be natively represented as standard relational tables:
+The Azure SQL family of products don't have specialized types or structures that support key-value pairs since key-value structures can be natively represented as standard relational tables:
 
 ```sql
 CREATE TABLE Collection (
@@ -144,7 +144,7 @@ See [how BWin is using In-Memory OLTP to achieve unprecedented performance and s
 
 ## Next steps
 
-Multi-model capabilities in the Azure SQL family of services are also the core SQL Server database engine features that are shared among the Azure SQL family of services. To learn more details about these features, visit the SQL Relational database documentation pages:
+Multi-model capabilities in the Azure SQL family of products are also the core SQL Server database engine features that are shared among the Azure SQL family of products. To learn more details about these features, visit the SQL Relational database documentation pages:
 
 - [Graph processing](/sql/relational-databases/graphs/sql-graph-overview)
 - [JSON data](/sql/relational-databases/json/json-data-sql-server)
diff --git a/articles/azure-sql/toc.yml b/articles/azure-sql/toc.yml
@@ -1,42 +1,28 @@
-- name: Azure SQL 
+- name: Azure SQL Documentation
   href: index.yml
 
 - name: Azure SQL
   items: 
   - name: What is Azure SQL? 
     href: azure-sql-iaas-vs-paas-what-is-overview.md
-  - name: Concepts
-    items: 
-    - name: Azure Hybrid Benefit
-      href: azure-hybrid-benefit.md
-    - name: Multi-model features
-      href: multi-model-features.md
-    - name: Accelerated database recovery
-      href: accelerated-database-recovery.md
-    - name: Application and database tuning guidance
-      href: database/performance-guidance.md
-    - name: Use DMVs to monitor performance
-      href: database/monitoring-with-dmvs.md
+  - name: Multi-model features
+    href: multi-model-features.md
 
-  - name: How to guides
-    items:
-    - name: Identify query performance issues
-      href: identify-query-performance-issues.md
-    - name: Batching for performance
-      href: performance-improve-use-batching.md
-    - name: Load data with BCP
-      href: load-from-csv-with-bcp.md
 
 - name: Shared SQL DB & SQL MI docs 
   items:
   - name: Shared concepts 
     itemS: 
     - name: Feature comparison
-      href: database/features-comparison.md
+      href: database/features-comparison.md    
+    - name: Azure Hybrid Benefit
+      href: azure-hybrid-benefit.md
+    - name: Accelerated database recovery
+      href: accelerated-database-recovery.md
+    - name: In-memory OLTP
+      href: in-memory-oltp-overview.md
     - name: Temporal tables
       href: temporal-tables.md
-    - name: In-memory OLTP
-      href: in-memory-oltp-overview.md      
 
     - name: Purchasing models
       items:
@@ -153,19 +139,39 @@
       href: database/quota-increase-request.md
     - name: Job automation
       href: database/job-automation-overview.md
-    - name: Configure failover group
-      href: database/auto-failover-group-configure.md
-    - name: Store vulnerability scans in storage
-      href: database/sql-database-vulnerability-assessment-storage.md
-    - name: Log diagnostic telemetry
-      href: database/metrics-diagnostic-telemetry-logging-streaming-export-configure.md
-    - name: Configure TDE with BYOK
-      href: database/transparent-data-encryption-byok-configure.md
-    - name: Configure temporal retention policy
-      href: database/temporal-tables-retention-policy.md
-    - name: Configure backup retention using Azure Blob storage
-      href: database/long-term-backup-retention-configure.md
+
+    - name: Business continuity  
+      items: 
+      - name: Configure failover group
+        href: database/auto-failover-group-configure.md
+      - name: Configure temporal retention policy
+        href: database/temporal-tables-retention-policy.md
+      - name: Configure backup retention using Azure Blob storage
+        href: database/long-term-backup-retention-configure.md
+
+    - name: Security  
+      items: 
+      - name: Configure TDE with BYOK
+        href: database/transparent-data-encryption-byok-configure.md 
+      - name: Store vulnerability scans in storage
+        href: database/sql-database-vulnerability-assessment-storage.md
+
   
+    - name: Monitor & tune
+      items: 
+      - name: Identify query performance issues
+        href: identify-query-performance-issues.md
+      - name: Batching for performance
+        href: performance-improve-use-batching.md
+      - name: Load data with BCP
+        href: load-from-csv-with-bcp.md
+      - name: Application and database tuning guidance
+        href: database/performance-guidance.md
+      - name: Use DMVs to monitor performance
+        href: database/monitoring-with-dmvs.md 
+      - name: Log diagnostic telemetry
+        href: database/metrics-diagnostic-telemetry-logging-streaming-export-configure.md
+
     - name: Load and move data
       items:
       - name: Import a database from a BACPAC file
