Merge pull request #248123 from memildin/docs-editor/concept-agentless-containers-1691944509

Update concept-agentless-containers.md

Author: prmerger-automator[bot]

articles/defender-for-cloud/concept-agentless-containers.md

@@ -1,6 +1,6 @@
 ---
 title: Agentless container posture for Microsoft Defender for Cloud
-description: Learn how agentless container posture offers discovery, visibility, and vulnerability assessment for Containers without installing an agent on your machines.
+description: Learn how agentless container posture offers discovery, visibility, and vulnerability assessment for containers without installing an agent on your machines.
 ms.service: defender-for-cloud
 ms.topic: conceptual
 ms.date: 07/03/2023
@@ -17,14 +17,14 @@ Learn more about [CSPM](concept-cloud-security-posture-management.md).
 
 For support and prerequisites for agentless containers posture, see [Support and prerequisites for agentless containers posture](support-agentless-containers-posture.md).
 
-Agentless container Posture provides the following capabilities:
+Agentless container posture provides the following capabilities:
 
 - [Agentless discovery and visibility](#agentless-discovery-and-visibility-within-kubernetes-components) within Kubernetes components.
 - [Container registry vulnerability assessment](agentless-container-registry-vulnerability-assessment.md) provides vulnerability assessment for all container images, with near real-time scan of new images and daily refresh of results for maximum visibility to current and emerging vulnerabilities, enriched with exploitability insights, and added to Defender CSPM security graph for contextual risk assessment and calculation of attack paths.
 - Using Kubernetes [attack path analysis](concept-attack-path.md) to visualize risks and threats to Kubernetes environments.
 - Using [cloud security explorer](how-to-manage-cloud-security-explorer.md) for risk hunting by querying various risk scenarios, including viewing security insights, such as internet exposure, and other predefined security scenarios. For more information, search for `Kubernetes` in the [list of Insights](attack-path-reference.md#insights).
 
-All of these capabilities are available as part of the [Defender Cloud Security Posture Management](concept-cloud-security-posture-management.md) plan.
+All of these capabilities are available as part of the [Defender CSPM](concept-cloud-security-posture-management.md) plan.
 
 ## Agentless discovery and visibility within Kubernetes components
 
@@ -38,9 +38,9 @@ The discovery process is based on snapshots taken at intervals:
 
 When you enable the agentless discovery for Kubernetes extension, the following process occurs:
 
-- **Create**: MDC (Microsoft Defender for Cloud) creates an identity in customer environments called CloudPosture/securityOperator/DefenderCSPMSecurityOperator.
+- **Create**: Defender for Cloud creates an identity in customer environments called CloudPosture/securityOperator/DefenderCSPMSecurityOperator.
 
-- **Assign**: MDC assigns 1 built-in role called **Kubernetes Agentless Operator** to that identity on subscription scope.
+- **Assign**: Defender for Cloud assigns 1 built-in role called **Kubernetes Agentless Operator** to that identity on subscription scope.
 
     The role contains the following permissions:
       - AKS read (Microsoft.ContainerService/managedClusters/read)
@@ -53,11 +53,11 @@ When you enable the agentless discovery for Kubernetes extension, the following
 
 - **Discover**: Using the system assigned identity, Defender for Cloud performs a discovery of the AKS clusters in your environment using API calls to the API server of AKS.
 
-- **Bind**: Upon discovery of an AKS cluster, MDC performs an AKS bind operation between the created identity and the Kubernetes role “Microsoft.Security/pricings/microsoft-defender-operator”. The role is visible via API and gives MDC data plane read permission inside the cluster.
+- **Bind**: Upon discovery of an AKS cluster, Defender for Cloud performs an AKS bind operation between the created identity and the Kubernetes role “Microsoft.Security/pricings/microsoft-defender-operator”. The role is visible via API and gives Defender for Cloud data plane read permission inside the cluster.
 
 ### What's the refresh interval?
 
-Agentless information in Defender CSPM is updated through a snapshot mechanism. It can take up to **24 hours** to see results in Cloud Security Explorer and Attack Path.
+Agentless information in Defender CSPM is updated through a snapshot mechanism. It can take up to **24 hours** to see results in attack paths and the cloud security explorer.
 
 ## Next steps