Changes from Shani

Author: David Curwin

articles/defender-for-cloud/defender-for-containers-enable.md

@@ -97,7 +97,7 @@ A full list of supported alerts is available in the [reference table of all Defe
 [!INCLUDE [Remove the profile](./includes/defender-for-containers-remove-profile.md)]
 ::: zone-end
 
-## Learn More
+## Learn more
 
 You can check out the following blogs:
 

articles/defender-for-cloud/faq-defender-for-containers.yml

@@ -29,13 +29,6 @@ sections:
         answer: |
           No. Only Azure Kubernetes Service (AKS) clusters that use Virtual Machine Scale Sets for the nodes is supported.
 
-      - question: |
-          Does Microsoft Defender for Containers support clusters in a private network?
-        answer: |
-          No. Only the configurations described [here](support-matrix-defender-for-containers.md#kubernetes-distributionsconfigurations-support-eks) are supported. For a workaround, you can try one of these options:
-          - Allow inbound network traffic during deployment, and then disable it after the deployment is complete. You will need to repeat this action for every upgrade.
-          - Contact AWS and see if you can add the the official AWS mirror server to your Security Group. The server that Defender for Cloud uses to download the kernel headers is `amazonlinux.<aws region>.amazonaws.com`.
-
       - question: |
           Do I need to install the Log Analytics VM extension on my AKS nodes for security protection?
         answer: |

articles/defender-for-cloud/includes/defender-for-containers-enable-plan-gke.md

@@ -13,6 +13,9 @@ author: dcurwin
 
 To protect your GKE clusters, you'll need to enable the Containers plan on the relevant GCP project.
 
+> [!NOTE]
+> Verify that you don't have any Azure policies that prevent the Arc installation.
+
 **To protect Google Kubernetes Engine (GKE) clusters**:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
@@ -46,8 +49,12 @@ The connector will update after the script executes. This process can take up to
 If you disabled any of the default auto provisioning configurations to Off, during the [GCP connector onboarding process](../quickstart-onboard-gcp.md#configure-the-defender-for-containers-plan), or afterwards. You'll need to manually install Azure Arc-enabled Kubernetes, the Defender extension, and the Azure Policy extensions to each of your GKE clusters to get the full security value out of Defender for Containers.
 
 There are 2 dedicated Defender for Cloud recommendations you can use to install the extensions (and Arc if necessary):
--	`GKE clusters should have Microsoft Defender's extension for Azure Arc installed`
--	`GKE clusters should have the Azure Policy extension installed`
+
+- `GKE clusters should have Microsoft Defender's extension for Azure Arc installed`
+- `GKE clusters should have the Azure Policy extension installed`
+
+> [!NOTE]
+> When installing Arc extensions, you must verify that the GCP project provided is identical to the one in the relevant connector.
 
 **To deploy the solution to specific clusters**:
 
@@ -72,7 +79,7 @@ There are 2 dedicated Defender for Cloud recommendations you can use to install
 
     :::image type="content" source="../media/defender-for-containers-enable-plan-gke/fix-button.png" alt-text="Screenshot showing the location of the fix button.":::
 
-1. Defender for Cloud will generate a script in the language of your choice: 
+1. Defender for Cloud will generate a script in the language of your choice:
     - For Linux, select **Bash**.
     - For Windows, select **PowerShell**.
 

articles/defender-for-cloud/tutorial-enable-container-gcp.md

@@ -74,6 +74,9 @@ There are two dedicated Defender for Cloud recommendations you can use to instal
 - `GKE clusters should have Microsoft Defender's extension for Azure Arc installed`
 - `GKE clusters should have the Azure Policy extension installed`
 
+> [!NOTE]
+> When installing Arc extensions, you must verify that the GCP project provided is identical to the one in the relevant connector.
+
 **To deploy the solution to specific clusters**:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).