Fix broken anchor links

Author: seesharprun

articles/cosmos-db/cassandra/support.md

@@ -350,7 +350,7 @@ Azure Cosmos DB supports Azure role-based access control (Azure RBAC) for provis
 
 ## Keyspace and Table options
 
-The options for region name, class, replication_factor, and datacenter in the `CREATE KEYSPACE` command are ignored currently. The system uses the underlying Azure Cosmos DB's [global distribution](../global-distribution.md) replication method to add the regions. If you need the cross-region presence of data, you can enable it at the account level with PowerShell, CLI, or the Azure portal. For more information, see [Add regions to your database account](../how-to-manage-database-account.yml#add-remove-regions-from-your-database-account).
+The options for region name, class, replication_factor, and datacenter in the `CREATE KEYSPACE` command are ignored currently. The system uses the underlying Azure Cosmos DB's [global distribution](../global-distribution.md) replication method to add the regions. If you need the cross-region presence of data, you can enable it at the account level with PowerShell, CLI, or the Azure portal. For more information, see [Add regions to your database account](../how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account).
 
 Durable_writes can't be disabled because Azure Cosmos DB ensures every write is durable. In every region, Azure Cosmos DB replicates the data across the replica set that is made up of four replicas and this replica set [configuration](../global-distribution.md) can't be modified.
 

articles/cosmos-db/data-residency.md

@@ -20,7 +20,7 @@ In Azure Cosmos DB, you can configure your data and backups to remain in a singl
 
 ## Residency requirements for data
 
-In Azure Cosmos DB, you must explicitly configure the cross-region data replication. Learn how to configure geo-replication using [Azure portal](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account), [Azure CLI](scripts/cli/common/regions.md). To meet data residency requirements, you can create an Azure Policy definition that allows certain regions to prevent data replication to unwanted regions.
+In Azure Cosmos DB, you must explicitly configure the cross-region data replication. Learn how to configure geo-replication using [Azure portal](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account), [Azure CLI](scripts/cli/common/regions.md). To meet data residency requirements, you can create an Azure Policy definition that allows certain regions to prevent data replication to unwanted regions.
 
 ## Residency requirements for backups
 

articles/cosmos-db/distribute-data-globally.md

@@ -65,6 +65,6 @@ With Azure Cosmos DB, you can add or remove the regions associated with your acc
 * [Global distribution - under the hood](global-distribution.md)
 * [How to configure multi-region writes in your applications](how-to-multi-master.md)
 * [Configure multiple write-regions](how-to-manage-database-account.yml#configure-multiple-write-regions)
-* [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account)
+* [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account)
 * [Create a custom conflict resolution policy for API for NoSQL accounts](how-to-manage-conflicts.md#create-a-custom-conflict-resolution-policy)
 * [Programmable consistency models in Azure Cosmos DB](consistency-levels.md)

articles/cosmos-db/global-distribution.md

@@ -98,7 +98,7 @@ For complete details on consistency level semantics and guarantees, see [Consist
 
 Next learn how to configure global distribution by using the following articles:
 
-* [Add/remove regions from your database account](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account)
+* [Add/remove regions from your database account](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account)
 * [How to create a custom conflict resolution policy](how-to-manage-conflicts.md#create-a-custom-conflict-resolution-policy)
 * Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.
     * If all you know is the number of vcores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](convert-vcore-to-request-unit.md) 

articles/cosmos-db/how-to-manage-conflicts.md

@@ -535,7 +535,7 @@ Learn about the following Azure Cosmos DB concepts:
 - [Global distribution - under the hood](global-distribution.md)
 - [How to configure multi-region writes in your applications](how-to-multi-master.md)
 - [Configure clients for multihoming](how-to-manage-database-account.yml#configure-multiple-write-regions)
-- [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account)
+- [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account)
 - [How to configuremulti-region writes in your applications](how-to-multi-master.md).
 - [Partitioning and data distribution](partitioning.md)
 - [Indexing in Azure Cosmos DB](index-policy.md)

articles/cosmos-db/scaling-provisioned-throughput-best-practices.md

@@ -36,7 +36,7 @@ When you send a request to increase the RU/s of your database or container, depe
   - As a result, the operation can take some time to complete, typically 4-6 hours. Each physical partition can support a maximum of 10,000 RU/s (applies to all APIs) of throughput and 50 GB of storage (applies to all APIs, except Cassandra, which has 30 GB of storage). 
 
   > [!NOTE]
-  > If you perform a [change write region operation](how-to-manage-database-account.yml#change-write-region-for-your-azure-cosmos-db-account) or [add/remove a new region](how-to-manage-database-account.yml#add-remove-regions-from-your-database-account) while an asynchronous scale-up operation is in progress, the throughput scale-up operation pauses. It resumes automatically when the failover or add/remove region operation is complete.
+  > If you perform a [change write region operation](how-to-manage-database-account.yml#change-write-region-for-your-azure-cosmos-db-account) or [add/remove a new region](how-to-manage-database-account.yml#add-or-remove-regions-from-your-database-account) while an asynchronous scale-up operation is in progress, the throughput scale-up operation pauses. It resumes automatically when the failover or add/remove region operation is complete.
 
 - **Instant scale-down**:
   - For scale-down operation, Azure Cosmos DB doesn’t need to split or add new partitions.