Integrated comments from Rimma

Author: Thomas Weiss

articles/cosmos-db/request-units.md

@@ -70,4 +70,4 @@ While you estimate the number of RUs per second to provision, consider the follo
 * Learn how to [optimize provisioned throughput cost in Azure Cosmos DB](optimize-cost-throughput.md).
 * Learn how to [optimize reads and writes cost in Azure Cosmos DB](optimize-cost-reads-writes.md).
 * Learn how to [optimize query cost in Azure Cosmos DB](optimize-cost-queries.md).
-* Learn how to [use metrics to monitor consumed throughput](use-metrics.md).
+* Learn how to [use metrics to monitor throughput](use-metrics.md).

articles/cosmos-db/set-throughput.md

@@ -69,7 +69,7 @@ You can combine the two models. Provisioning throughput on both the database and
 * You can create an Azure Cosmos database named *Z* with provisioned throughput of *"K"* RUs. 
 * Next, create five containers named *A*, *B*, *C*, *D*, and *E* within the database. When creating container B, make sure to enable **Provision dedicated throughput for this container** option and explicitly configure *"P"* RUs of provisioned throughput on this container. Note that you can configure shared and dedicated throughput only when creating the database and container. 
 
-![Setting the throughput at the collection-level](./media/set-throughput/coll-level-throughput.png)
+![Setting the throughput at the container-level](./media/set-throughput/coll-level-throughput.png)
 
 * The *"K"* RUs throughput is shared across the four containers *A*, *C*, *D*, and *E*. The exact amount of throughput available to *A*, *C*, *D*, or *E* varies. There are no SLAs for each individual container’s throughput.
 * The container named *B* is guaranteed to get the *"P"* RUs throughput all the time. It's backed by SLAs.

articles/cosmos-db/stored-procedures-triggers-udfs.md

@@ -82,7 +82,7 @@ Azure Cosmos DB provides triggers that can be invoked by performing an operation
 Similar to pre-triggers, post-triggers, are also associated with an operation on an Azure Cosmos DB item and they don’t require any input parameters. They run *after* the operation has completed and have access to the response message that is sent to the client. For examples, see [How to write triggers](how-to-write-stored-procedures-triggers-udfs.md#triggers) article.
 
 > [!NOTE]
-> Registered triggers don't run automatically when their corresponding operations (create / delete / replace / update) happen. They have to be explicitly called when executing these operations. See [this section](how-to-use-stored-procedures-triggers-udfs#pre-triggers) to learn how to run triggers.
+> Registered triggers don't run automatically when their corresponding operations (create / delete / replace / update) happen. They have to be explicitly called when executing these operations. See [this section](how-to-use-stored-procedures-triggers-udfs.md#pre-triggers) to learn how to run triggers.
 
 ## <a id="udfs"></a>User-defined functions