Merge pull request #274656 from dcurwin/yml-acrolinx-may8-2024

Improve Acrolinx

Author: prmerger-automator[bot]

articles/defender-for-cloud/azure-devops-extension.yml

@@ -138,7 +138,7 @@ procedureSection:
       While Defender for Cloud provides the MSDO CLI for standardized
       functionality and policy controls across a set of open source security
       analyzers, you have the flexibility to upload results from other
-      third-party security tooling that you may have configured in CI/CD
+      third-party security tooling that you might have configured in CI/CD
       pipelines to Defender for Cloud for comprehensive code-to-cloud
       contextualization. All results uploaded to Defender for Cloud must be in
       standard SARIF format.
@@ -150,7 +150,7 @@ procedureSection:
 
       You can use the 'PublishBuildArtifacts@1' task to ensure SARIF output is
       published to the correct artifact. For example, if a security analyzer
-      outputs 'results.sarif', you can configure the following task in your job
+      outputs `results.sarif`, you can configure the following task in your job
       to ensure results are uploaded to Defender for Cloud:
     code: |
         ```yml

articles/defender-for-cloud/update-regulatory-compliance-packages.yml

@@ -37,7 +37,7 @@ procedureSection:
 
           :::image type="content" source="media/update-regulatory-compliance-packages/manage-compliance.png" alt-text="Screenshot of the regulatory compliance page that shows you where to select the manage compliance policy button." lightbox="media/update-regulatory-compliance-packages/manage-compliance.png":::
       - |
-        Select an account or management account (Azure subscription or nmanagement group, AWS account or management account, GCP project or organization) on which you want to assign the security standard.
+        Select an account or management account (Azure subscription or management group, AWS account or management account, GCP project or organization) on which you want to assign the security standard.
 
           > [!NOTE]
           > We recommend selecting the highest scope for which the standard is applicable so that compliance data is aggregated and tracked for all nested resources.
@@ -53,11 +53,11 @@ procedureSection:
         The selected standard appears in **Regulatory compliance** dashboard as enabled for the subscription it was enabled on.
 
 relatedContent:
-  - text: Create custom standards for Azure
+  - text: Create custom standards for Azure.
     url: custom-security-policies.md
-  - text: Create custom standards for AWS, and GCP
+  - text: Create custom standards for AWS and GCP.
     url: create-custom-recommendations.md
-  - text: Improve regulatory compliance
+  - text: Improve regulatory compliance.
     url: regulatory-compliance-dashboard.md
 
 # - Create custom standards for [Azure](custom-security-policies.md), [AWS, and GCP](create-custom-recommendations.md).

articles/defender-for-cloud/workflow-automation.yml

@@ -2,7 +2,7 @@
 
 metadata:
   title: Workflow automation
-  description: Learn how to create and automate workflows in Microsoft Defender for Cloud
+  description: Learn how to create and automate workflows in Microsoft Defender for Cloud.
   author: dcurwin
   ms.author: dacurwin
   ms.date: 06/18/2023
@@ -78,14 +78,14 @@ procedureSection:
     summary: |
       The logic app designer supports the following Defender for Cloud triggers:
 
-      - **When a Microsoft Defender for Cloud Recommendation is created or triggered** - If your logic app relies on a recommendation that gets deprecated or replaced, your automation will stop working and you'll need to update the trigger. To track changes to recommendations, use the [release notes](release-notes.md).
+      - **When a Microsoft Defender for Cloud Recommendation is created or triggered** - If your logic app relies on a recommendation that gets deprecated or replaced, your automation stops working and you need to update the trigger. To track changes to recommendations, use the [release notes](release-notes.md).
 
       - **When a Defender for Cloud Alert is created or triggered** - You can customize the trigger so that it relates only to alerts with the severity levels that interest you.
 
       - **When a Defender for Cloud regulatory compliance assessment is created or triggered** - Trigger automations based on updates to regulatory compliance assessments.
 
       > [!NOTE]
-      > If you are using the legacy trigger "When a response to a Microsoft Defender for Cloud alert is triggered", your logic apps will not be launched by the Workflow Automation feature. Instead, use either of the triggers mentioned above.
+      > If you're using the legacy trigger **When a response to a Microsoft Defender for Cloud alert is triggered**, your logic apps won't be launched by the Workflow Automation feature. Instead, use either of the triggers mentioned above.
     steps: 
       - |
         After you've defined your logic app, return to the workflow automation definition pane ("Add workflow automation").