Merge pull request #58140 from paulth1/cosmos-db-broken-bookmarks2

fixing broken bookmarks

Author: PRMerger15

articles/cosmos-db/consistency-levels-choosing.md

@@ -49,7 +49,7 @@ You may get stronger consistency guarantees in practice. Consistency guarantees
 
 * For the remaining three consistency levels, the staleness window is largely dependent on your workload. For example, if there are no write operations on the database, a read operation with **eventual**, **session**, or **consistent prefix** consistency levels is likely to yield the same results as a read operation with strong consistency level.
 
-If your Cosmos DB account is configured with a consistency level other than the strong consistency, you can find out the probability that your clients may get strong and consistent reads for your workloads by looking at the Probabilistic Bounded Staleness (PBS) metric. This metric is exposed in the Azure portal, to learn more, see [Monitor the probabilistically bounded staleness metric](how-to-manage-consistency.md#monitor-probabilistically-bounded-staleness-pbs-metric).
+If your Cosmos DB account is configured with a consistency level other than the strong consistency, you can find out the probability that your clients may get strong and consistent reads for your workloads by looking at the Probabilistic Bounded Staleness (PBS) metric. This metric is exposed in the Azure portal, to learn more, see [Monitor Probabilistically Bounded Staleness (PBS) metric](how-to-manage-consistency.md#monitor-probabilistically-bounded-staleness-pbs-metric).
 
 Probabilistic bounded staleness shows how eventual is your eventual consistency. This metric provides an insight into how often you can get a stronger consistency than the consistency level that you have currently configured on your Cosmos DB account. In other words, you can see the probability (measured in milliseconds) of getting strongly consistent reads for a combination of write and read regions.
 
@@ -60,4 +60,4 @@ Read more about the consistency levels in the following articles:
 * [Consistency level mapping across Cosmos DB APIs](consistency-levels-across-apis.md)
 * [Availability and performance tradeoffs for various consistency levels](consistency-levels-tradeoffs.md)
 * [How to manage the session token for your application](how-to-manage-consistency.md#utilize-session-tokens)
-* [Monitor the probabilistically bounded staleness metric](how-to-manage-consistency.md#monitor-probabilistically-bounded-staleness-pbs-metric)
+* [Monitor Probabilistically Bounded Staleness (PBS) metric](how-to-manage-consistency.md#monitor-probabilistically-bounded-staleness-pbs-metric)

articles/cosmos-db/global-dist-under-the-hood.md

@@ -78,5 +78,5 @@ The semantics of the five consistency models in Cosmos DB are described [here](c
 Next learn how to configure global distribution by using the following articles:
 
 * [How to configure clients for multi-homing](how-to-manage-database-account.md#configure-clients-for-multi-homing)
-* [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.md#addremove-regions-from-your-database-account)
+* [Add/remove regions from your database account](how-to-manage-database-account.md#addremove-regions-from-your-database-account)
 * [How to create a custom conflict resolution policy for SQL API accounts](how-to-manage-conflicts.md#create-a-custom-conflict-resolution-policy)

articles/cosmos-db/scaling-throughput.md

@@ -20,7 +20,7 @@ In Azure Cosmos DB, provisioned throughput is represented as request units/secon
 
 You can provision RUs on a Cosmos container or a Cosmos database. RUs provisioned on a container are exclusively available for operations performed on that container. RUs provisioned on a database are shared among all the containers within that database (except for any containers with exclusively assigned RUs).
 
-For elastically scaling throughput, you can increase or decrease the provisioned RU/s at any time. For more information, see [How-to provision throughput](set-throughput.md) and elastically scale Cosmos containers and databases. For globally scaling throughput, you can add or remove regions on your Cosmos account at any time. For more information, see [Add or remove regions from your Azure Cosmos DB account](how-to-manage-database-account.md#addremove-regions-from-your-database-account). Associating multiple regions with a Cosmos account is important in many scenarios to achieve low latency and [high availability](high-availability.md) around the world.
+For elastically scaling throughput, you can increase or decrease the provisioned RU/s at any time. For more information, see [How-to provision throughput](set-throughput.md) and elastically scale Cosmos containers and databases. For globally scaling throughput, you can add or remove regions on your Cosmos account at any time. For more information, see [Add/remove regions from your database account](how-to-manage-database-account.md#addremove-regions-from-your-database-account). Associating multiple regions with a Cosmos account is important in many scenarios to achieve low latency and [high availability](high-availability.md) around the world.
 
 ## how provisioned throughput is distributed across regions