Addressing Docs team review feedback

Author: deborahc

articles/cosmos-db/create-alerts.md

@@ -30,8 +30,6 @@ This section shows how to create an alert when you receive an HTTP status code 4
 > [!TIP]
 > The scenario of alerting based on number of 429s exceeding a threshold is used here for illustration purposes. It does not mean that there is anything inherently wrong with seeing 429s on your database or container. In general, if you see 1-5% of requests with 429s in a production workload and your overall application latency is within your requirements, this is a normal and healthy sign that you are fully using the throughput (RU/s) you've provisioned. [Learn more about how to interpret and debug 429 exceptions](sql/troubleshoot-request-rate-too-large.md).
 
- [Diagnose and troubleshoot Azure Cosmos DB request rate too large (429) exceptions]
-
 1. Sign into the [Azure portal.](https://portal.azure.com/)
 
 1. Select **Monitor** from the left-hand navigation bar and select **Alerts**.

articles/cosmos-db/how-to-alert-on-logical-partition-key-storage-size.md

@@ -97,9 +97,9 @@ Follow the instructions in [Monitor Azure Cosmos DB data by using diagnostic set
 
         * Select your desired **Frequency of evaluation** based on your requirements. In our example, we’ll select **1 hour**. Note this value must be less than or equal to the alert evaluation period.
 
-    After completing Step 5, the **Condition** section will look like the example below. 
-
-    :::image type="content" source="media/how-to-alert-on-logical-partition-key-storage-size/alert-signal-logic.png" alt-text="Example configuration for signal logic":::
+        After completing Step 5, the **Condition** section will look like the example below. 
+    
+        :::image type="content" source="media/how-to-alert-on-logical-partition-key-storage-size/alert-signal-logic.png" alt-text="Screenshot of an example configuration for signal logic":::
 
 1. Fill out the **Actions** section:
 
@@ -145,7 +145,7 @@ When the alert is fired, it will include:
 
 For example, in the alert that was fired below, we see the logical partition of "ContosoTenant" has reached 0.78 of the 20GB logical partition storage limit, with 16GB of data in a particular database and collection. 
 
-:::image type="content" source="media/how-to-alert-on-logical-partition-key-storage-size/alert-when-logical-partition-key-exceeds-threshold.png" alt-text="Example alert fired when logical partition key size exceeds threshold":::
+:::image type="content" source="media/how-to-alert-on-logical-partition-key-storage-size/alert-when-logical-partition-key-exceeds-threshold.png" alt-text="Screenshot of an alert fired when logical partition key size exceeds threshold":::
 
 ## Remediation steps
 When the 20 GB logical partition size limit is reached, you won't be able to write any more data to that logical partition. As a result, it's recommended to rearchitect your application with a different partition key as a long-term solution.