edits

tejaswikolli-web · tejaswikolli-web · commit 06db15054c0b · 2022-07-25T14:14:32.000-07:00
diff --git a/includes/container-registry-scanning-limitation.md b/includes/container-registry-scanning-limitation.md
@@ -16,5 +16,5 @@ ms.custom: include file
 >
 > * When public network access to a registry is disabled, registry access by certain [trusted services](../articles/container-registry/allow-access-trusted-services.md) including Azure Security Center requires enabling a network setting to bypass the network rules.
 > * Once the public network access is disabled, Instances of certain Azure services including Azure DevOps Services are currently unable to access the container registry. 
-> * Private endpoints are not currently supported with self-hosted agents on Azure DevOps, including standalone VMs, VMSS or function apps in user VNETs. Managed agents cannot be linked to a user VNET, therefore they cannot access a registry over the private endpoint.  
+> * Private endpoints are not currently supported with self-hosted agents on Azure DevOps, including standalone VMs, VMSS or function apps in user VNETs. Managed agents cannot be linked to a user VNET, restricting access to a registry over the private endpoint.  
 > * If the registry has an approved private endpoint and public network access is disabled, repositories and tags can't be listed outside the virtual network using the Azure portal, Azure CLI, or other tools.

Original file line number	Diff line number	Diff line change
`@@ -16,5 +16,5 @@ ms.custom: include file`
`16`	`16`	`>`
`17`	`17`	`> * When public network access to a registry is disabled, registry access by certain [trusted services](../articles/container-registry/allow-access-trusted-services.md) including Azure Security Center requires enabling a network setting to bypass the network rules.`
`18`	`18`	`> * Once the public network access is disabled, Instances of certain Azure services including Azure DevOps Services are currently unable to access the container registry.`
`19`		`-> * Private endpoints are not currently supported with self-hosted agents on Azure DevOps, including standalone VMs, VMSS or function apps in user VNETs. Managed agents cannot be linked to a user VNET, therefore they cannot access a registry over the private endpoint.`
	`19`	`+> * Private endpoints are not currently supported with self-hosted agents on Azure DevOps, including standalone VMs, VMSS or function apps in user VNETs. Managed agents cannot be linked to a user VNET, restricting access to a registry over the private endpoint.`
`20`	`20`	`> * If the registry has an approved private endpoint and public network access is disabled, repositories and tags can't be listed outside the virtual network using the Azure portal, Azure CLI, or other tools.`