Fix formatting

Author: David Curwin

articles/defender-for-cloud/tutorial-enable-databases-plan.md

@@ -85,4 +85,3 @@ These plans protect all of the supported databases in your subscription.
 - [Microsoft Defender for SQL servers on machines](defender-for-sql-usage.md)
 - [Overview of Microsoft Defender for open-source relational databases](defender-for-databases-introduction.md)
 - [Overview of Microsoft Defender for Azure Cosmos DB](concept-defender-for-cosmos.md)
-

articles/defender-for-cloud/tutorial-enable-resource-manager-plan.md

@@ -41,6 +41,6 @@ Microsoft Defender for Resource Manager automatically monitors the resource mana
 
 1. Select **Save**.
 
-## Next steps
+## Next step
 
 [Overview of Microsoft Defender for Resource Manager](defender-for-resource-manager-introduction.md)

articles/defender-for-cloud/tutorial-enable-storage-plan.md

@@ -11,7 +11,7 @@ Microsoft Defender for Storage is an Azure-native solution offering an advanced
 
 With Microsoft Defender for Storage, organizations can customize their protection and enforce consistent security policies by enabling it on subscriptions and storage accounts with granular control and flexibility.
 
-   > [!TIP] 
+   > [!TIP]
    > If you're currently using Microsoft Defender for Storage classic, consider [migrating to the new plan](defender-for-storage-classic-migrate.md), which offers several benefits over the classic plan.
 
 ## Availability
@@ -26,6 +26,7 @@ With Microsoft Defender for Storage, organizations can customize their protectio
 *Azure DNS Zone is not supported for malware scanning and sensitive data threat detection.
 
 ## Prerequisites for malware scanning
+
 To enable and configure malware scanning, you must have Owner roles (such as Subscription Owner or Storage Account Owner) or specific roles with the necessary data actions. Learn more about the [required permissions](support-matrix-defender-for-storage.md).
 
 ## Set up and configure Microsoft Defender for Storage
@@ -53,6 +54,3 @@ Enabling Defender for Storage via a policy is recommended because it facilitates
 ## Next steps
 
 - Learn how to [enable and Configure the Defender for Storage plan at scale with an Azure built-in policy](defender-for-storage-policy-enablement.md).
-
-
-

articles/defender-for-cloud/upcoming-changes.md

@@ -57,7 +57,6 @@ In February 2021, the deprecation of the MSCA task was communicated to all custo
 
 Customers can get the latest DevOps security tooling from Defender for Cloud through [Microsoft Security DevOps](azure-devops-extension.md) and additional security tooling through [GitHub Advanced Security for Azure DevOps](https://azure.microsoft.com/products/devops/github-advanced-security).
 
-
 ## Update recommendations to align with Azure AI Services resources
 
 **Announcement date: February 20, 2024**
@@ -97,7 +96,6 @@ Customers that are still using the API version **2022-09-01-preview** under `Mic
 
 Customers currently using Defender for Cloud DevOps security from Azure portal won't be impacted.
 
-
 For details on the new API version, see [Microsoft Defender for Cloud REST APIs](/rest/api/defenderforcloud/operation-groups).
 
 ## Changes in endpoint protection recommendations

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

@@ -8,7 +8,6 @@ ms.custom: ignite-2023
 
 # Assign security standards
 
-
 Defender for Cloud's regulatory standards and benchmarks are represented as [security standards](security-policy-concept.md). Each standard is an initiative defined in Azure Policy.
 
 In Defender for Cloud, you assign security standards to specific scopes such as Azure subscriptions, AWS accounts, and GCP projects that have Defender for Cloud enabled.

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

@@ -18,11 +18,10 @@ This article describes the workflow automation feature of Microsoft Defender for
 - You must also have write permissions for the target resource.
 - To work with Azure Logic Apps workflows, you must also have the following Logic Apps roles/permissions:
 
-    - [Logic App Operator](../role-based-access-control/built-in-roles.md#logic-app-operator) permissions are required or Logic App read/trigger access (this role can't create or edit logic apps; only *run* existing ones)
-    - [Logic App Contributor](../role-based-access-control/built-in-roles.md#logic-app-contributor) permissions are required for logic app creation and modification.
-    
-- If you want to use Logic Apps connectors, you might need other credentials to sign in to their respective services (for example, your Outlook/Teams/Slack instances).
+  - [Logic App Operator](../role-based-access-control/built-in-roles.md#logic-app-operator) permissions are required or Logic App read/trigger access (this role can't create or edit logic apps; only *run* existing ones)
+  - [Logic App Contributor](../role-based-access-control/built-in-roles.md#logic-app-contributor) permissions are required for logic app creation and modification.
 
+- If you want to use Logic Apps connectors, you might need other credentials to sign in to their respective services (for example, your Outlook/Teams/Slack instances).
 
 ## Create a logic app and define when it should automatically run
 
@@ -79,7 +78,6 @@ The logic app designer supports the following Defender for Cloud triggers:
 > [!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.
 
-
 1. After you've defined your logic app, return to the workflow automation definition pane ("Add workflow automation").
 1. Select **Refresh** to ensure your new logic app is available for selection.
 1. Select your logic app and save the automation. The logic app dropdown only shows those with supporting Defender for Cloud connectors mentioned above.
@@ -92,7 +90,7 @@ To manually run a logic app, open an alert, or a recommendation and select **Tri
 
 [![Manually trigger a logic app.](media/workflow-automation/manually-trigger-logic-app.png)](media/workflow-automation/manually-trigger-logic-app.png#lightbox)
 
-## Configure workflow automation at scale 
+## Configure workflow automation at scale
 
 Automating your organization's monitoring and incident response processes can greatly improve the time it takes to investigate and mitigate security incidents.
 
@@ -110,9 +108,7 @@ To implement these policies:
     |Workflow automation for security recommendations     |[Deploy Workflow Automation for Microsoft Defender for Cloud recommendations](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F73d6ab6c-2475-4850-afd6-43795f3492ef)|73d6ab6c-2475-4850-afd6-43795f3492ef|
     |Workflow automation for regulatory compliance changes|[Deploy Workflow Automation for Microsoft Defender for Cloud regulatory compliance](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F509122b9-ddd9-47ba-a5f1-d0dac20be63c)|509122b9-ddd9-47ba-a5f1-d0dac20be63c|
 
-    
     You can also find these by searching Azure Policy. In Azure Policy, select **Definitions** and search for them by name.
-    
 
 1. From the relevant Azure Policy page, select **Assign**.
     :::image type="content" source="./media/workflow-automation/export-policy-assign.png" alt-text="Assigning the Azure Policy.":::