minor edit to ease cross-repo include use

Author: Brenduns

memdocs/intune/.vscode/settings.json

@@ -0,0 +1,8 @@
+{
+    "markdownlint.config": {
+        "MD028": false,
+        "MD025": {
+            "front_matter_title": ""
+        }
+    }
+}

memdocs/intune/protect/mde-security-integration.md

@@ -45,11 +45,7 @@ This scenario extends the Microsoft Endpoint Manager Endpoint Security surface t
 
 :::image type="content" source="./media/mde-security-integration/endpoint-security-overview.png" alt-text="Conceptual diagram of the MDE-Attach solution." lightbox="./media/mde-security-integration/endpoint-security-overview.png":::
 
-## Prerequisites
-
-Review the following sections for requirements for the Security Management for Microsoft Defender for Endpoint Scenario:
-
-### High-level flow
+**High-level flow**:
 
 When a device onboards to Microsoft Defender for Endpoint and security management is enabled:
 
@@ -59,6 +55,10 @@ When a device onboards to Microsoft Defender for Endpoint and security managemen
 - Azure Active Directory trust is used to communicate with Endpoint Manager (Intune) and retrieve policies
 - Policy retrieve from Endpoint Manager is enforced on the device by Microsoft Defender for Endpoint
 
+## Prerequisites
+
+Review the following sections for requirements for the Security Management for Microsoft Defender for Endpoint Scenario:
+
 ### Active Directory Requirements
 
 When a device that is domain joined creates a trust with Azure Active Directory, this scenario is referred to as a *Hybrid Azure Active Directory Join* scenario. The Security Management for MDE fully supports this scenario with the following requirements: