Format updates

Author: SnehaGunda

articles/cosmos-db/table-api-faq.md

@@ -12,7 +12,7 @@ ms.author: sngun
 
 The Azure Cosmos DB Table API is available in the [Azure portal](https://portal.azure.com) First you must sign up for an Azure subscription. After you've signed up, you can add an Azure Cosmos DB Table API account to your Azure subscription, and then add tables to your account. You can find the supported languages and associated quick-starts in the [Introduction to Azure Cosmos DB Table API](table-introduction.md).
 
-## Table API in Azure Cosmos DB Vs Azure Table storage
+## <a id="table-api-vs-table-storage"></a>Table API in Azure Cosmos DB Vs Azure Table storage
 
 ### Where is Table API not identical with Azure Table storage behavior?
 

articles/cosmos-db/table-storage-design-guide.md

@@ -208,7 +208,7 @@ Here are some general guidelines for designing Table storage queries. The filter
   `$filter=PartitionKey eq 'Sales' and LastName eq 'Smith'`.  
 * A *table scan* doesn't include the `PartitionKey`, and is inefficient because it searches all of the partitions that make up your table for any matching entities. It performs a table scan regardless of whether or not your filter uses the `RowKey`. For example:
   `$filter=LastName eq 'Jones'`.  
-* Azure Table storage queries that return multiple entities sort them in `PartitionKey` and `RowKey` order. To avoid resorting the entities in the client, choose a `RowKey` that defines the most common sort order. Query results returned by the Azure Table API in Azure Cosmos DB aren't sorted by partition key or row key. For a detailed list of feature differences, see [differences between Table API in Azure Cosmos DB and Azure Table storage](faq.md#where-is-table-api-not-identical-with-azure-table-storage-behavior).
+* Azure Table storage queries that return multiple entities sort them in `PartitionKey` and `RowKey` order. To avoid resorting the entities in the client, choose a `RowKey` that defines the most common sort order. Query results returned by the Azure Table API in Azure Cosmos DB aren't sorted by partition key or row key. For a detailed list of feature differences, see [differences between Table API in Azure Cosmos DB and Azure Table storage](table-api-faq.md#table-api-vs-table-storage).
 
 Using an "**or**" to specify a filter based on `RowKey` values results in a partition scan, and isn't treated as a range query. Therefore, avoid queries that use filters such as:
 `$filter=PartitionKey eq 'Sales' and (RowKey eq '121' or RowKey eq '322')`.  
@@ -251,7 +251,7 @@ Many designs must meet requirements to enable lookup of entities based on multip
 Table storage returns query results sorted in ascending order, based on `PartitionKey` and then by `RowKey`.
 
 > [!NOTE]
-> Query results returned by the Azure Table API in Azure Cosmos DB aren't sorted by partition key or row key. For a detailed list of feature differences, see [differences between Table API in Azure Cosmos DB and Azure Table storage](faq.md#where-is-table-api-not-identical-with-azure-table-storage-behavior).
+> Query results returned by the Azure Table API in Azure Cosmos DB aren't sorted by partition key or row key. For a detailed list of feature differences, see [differences between Table API in Azure Cosmos DB and Azure Table storage](table-api-faq.md#table-api-vs-table-storage).
 
 Keys in Table storage are string values. To ensure that numeric values sort correctly, you should convert them to a fixed length, and pad them with zeroes. For example, if the employee ID value you use as the `RowKey` is an integer value, you should convert employee ID **123** to **00000123**. 
 
@@ -738,7 +738,7 @@ The following patterns and guidance might also be relevant when implementing thi
 Retrieve the *n* entities most recently added to a partition by using a `RowKey` value that sorts in reverse date and time order.  
 
 > [!NOTE]
-> Query results returned by the Azure Table API in Azure Cosmos DB aren't sorted by partition key or row key. Thus, while this pattern is suitable for Table storage, it isn't suitable for Azure Cosmos DB. For a detailed list of feature differences, see [differences between Table API in Azure Cosmos DB and Azure Table Storage](faq.md#where-is-table-api-not-identical-with-azure-table-storage-behavior).
+> Query results returned by the Azure Table API in Azure Cosmos DB aren't sorted by partition key or row key. Thus, while this pattern is suitable for Table storage, it isn't suitable for Azure Cosmos DB. For a detailed list of feature differences, see [differences between Table API in Azure Cosmos DB and Azure Table Storage](table-api-faq.md#table-api-vs-table-storage).
 
 #### Context and problem
 A common requirement is to be able to retrieve the most recently created entities, for example the ten most recent expense claims submitted by an employee. Table queries support a `$top` query operation to return the first *n* entities from a set. There's no equivalent query operation to return the last *n* entities in a set.  

articles/cosmos-db/table-support.md

@@ -29,7 +29,7 @@ At this time, the [Azure Cosmos DB Table API](table-introduction.md) has four SD
 * [Node.js SDK](table-sdk-nodejs.md): This Azure Storage SDK has the ability to connect to Azure Cosmos DB accounts using the Table API.
 
 
-Additional information about working with the Table API is available in the [FAQ: Develop with the Table API](faq.md#table) article.
+Additional information about working with the Table API is available in the [FAQ: Develop with the Table API](table-api-faq.md) article.
 
 ## Developing with Azure Table storage
 

includes/storage-table-cosmos-db-tip-include.md

@@ -6,5 +6,5 @@ ms.date: 10/26/2018
 ms.author: tamram
 ---
 > [!TIP]
-> The content in this article applies to the original Azure Table storage. However, there is now a premium offering for table storage: the Azure Cosmos DB Table API. This API offers throughput-optimized tables, global distribution, and automatic secondary indexes. There are some [feature differences between Table API in Azure Cosmos DB and Azure table storage](../articles/cosmos-db/faq.md#where-is-table-api-not-identical-with-azure-table-storage-behavior). For more information, and to try out the premium experience, see [Azure Cosmos DB Table API](https://aka.ms/premiumtables). 
+> The content in this article applies to the original Azure Table storage. However, there is now a premium offering for table storage: the Azure Cosmos DB Table API. This API offers throughput-optimized tables, global distribution, and automatic secondary indexes. There are some [feature differences between Table API in Azure Cosmos DB and Azure table storage](../articles/cosmos-db/table-api-faq.md#table-api-vs-table-storage). For more information, and to try out the premium experience, see [Azure Cosmos DB Table API](https://aka.ms/premiumtables). 
 >