fix(ipam): modification review

Author: RoRoJ

network/ipam/reference-content/public-connectivity-best-practices.mdx

@@ -20,7 +20,7 @@ This document sets out best practices for securing and optimizing public connect
 Public vs private connectivity defines how resources are accessed and exposed over networks.
 
 - **Public connectivity**: Your resource has a [public IP address](/network/ipam/concepts/#public-flexible-ip-address) and is reachable over the public internet. Anyone with the right credentials can access the resource via its public IP address, e.g. over an [SSH connection](/compute/instances/how-to/connect-to-instance/) or simply by directly accessing its IP address in a browser to retrieve and display any content it is serving, e.g. over HTTP.
-- **Private connectivity**: Your resources is reachable over an attached [Private Network](/network/vpc/concepts/#private-networks). The resource has a [private IP address](/network/vpc/concepts/#private-ip-address), but it can only be accessed via this address from within the Private Network. Such a resource may or may not also have a public IP address.
+- **Private connectivity**: Your resources is reachable over an attached [Private Network](/network/vpc/concepts/#private-networks). The resource has a [private IP address](/network/vpc/concepts/#private-ip-address), but it can only be accessed via this address from within the VPC of the Private Network. Such a resource may or may not also have a public IP address.
 
 ## Effectively managing IP addresses