Apply suggestions from code review

Author: shsagir

articles/defender-for-cloud/data-sensitivity-settings.md

@@ -56,7 +56,7 @@ To customize data sensitivity settings that appear in Defender for Cloud, review
 1. Select the info types that you want to be marked as sensitive.
 1. Select **Apply** and **Save**.
 
-    :::image type="content" source="./media/concept-data-security-posture/data-sensitivity.png" alt-text="Graphic showing data sensitivity settings.":::
+    :::image type="content" source="./media/concept-data-security-posture/data-sensitivity.png" alt-text="Screenshot of the data sensitivity page, showing the sensitivity settings.":::
 
 ## Set the threshold for sensitive data labels
 
@@ -74,7 +74,7 @@ If you're using Microsoft Purview sensitivity labels, make sure that:
 1. Select **Change** to see the list of sensitivity labels and select the lowest sensitivity label that you want marked as sensitive.
 1. Select **Apply** and **Save**.
 
-    :::image type="content" source="./media/concept-data-security-posture/sensitivity-threshold.png" alt-text="Graphic showing data sensitivity threshold.":::
+    :::image type="content" source="./media/concept-data-security-posture/sensitivity-threshold.png" alt-text="Screenshot of the data sensitivity page, showing the sensitivity label threshold.":::
 
 > [!NOTE]
 > - When you turn on the threshold, you select a label with the lowest setting that should be considered sensitive in your organization.

articles/defender-for-cloud/release-notes.md

@@ -359,7 +359,7 @@ Now, the new Defender for DevOps plan integrates source code management systems,
 
 Defender for DevOps allows you to gain visibility into and manage your connected developer environments and code resources. Currently, you can connect [Azure DevOps](quickstart-onboard-devops.md) and [GitHub](quickstart-onboard-github.md) systems to Defender for Cloud and onboard DevOps repositories to Inventory and the new DevOps Security page. It provides security teams with a high-level overview of the discovered security issues that exist within them in a unified DevOps Security page.
 
-Security teams, can now configure pull request annotations to help developers address secret scanning findings in Azure DevOps directly on their pull requests.
+Security teams can now configure pull request annotations to help developers address secret scanning findings in Azure DevOps directly on their pull requests.
 
 You can configure the Microsoft Security DevOps tools on Azure Pipelines and GitHub workflows to enable the following security scans: