Another missed update per PR comment

Author: lilinvictorms

articles/batch/private-connectivity.md

@@ -110,7 +110,7 @@ When creating private endpoint with your Batch account, keep in mind the followi
 - Private endpoint resources with the sub-resource **batchAccount** must be created in the same subscription as the Batch account.
 - Resource movement is not supported for private endpoints with Batch accounts.
 - If a Batch account resource is moved to a different resource group or subscription, the private endpoints can still work, but the association to the Batch account breaks. If you delete the private endpoint resource, its associated private endpoint connection still exists in your Batch account. You can manually remove connection from your Batch account.
-- To delete the private connection, you can either delete the private endpoint resource, or delete the private connection in Batch account which will set the related private endpoint resource to Disconnected state.
+- To delete the private connection, either delete the private endpoint resource, or delete the private connection in the Batch account (this action disconnects the related private endpoint resource).
 - DNS records in the private DNS zone are not removed automatically when you delete a private endpoint connection from the Batch account. You must manually remove the DNS records before adding a new private endpoint linked to this private DNS zone. If you don't clean up the DNS records, unexpected access issues might happen.
 
 ## Next steps