fix(lb): clarify mentions of PNs in LB

Author: RoRoJ

macros/network/lb-create-backend-2-traffic-mgnt.mdx

@@ -14,7 +14,7 @@ Traffic management configuration lets you define how your Load Balancer's backen
 2. Add the **Server IP addresses** of the servers the Load Balancer will forward requests/connections to. These will be your backend servers. 
 
         <Message type="note">
-        If you want your Load Balancer to communicate with its backend servers over an attached [Private Network](/vpc/concepts/#private-networks), ensure that you enter the servers' private IP addresses on that network. This is necessary in the case of a [private Load Balancer](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers), but may also be desired for public Load Balancers attached to Private Networks where backend servers are on the same Private Network.
+        If you want your Load Balancer to communicate with its backend servers over an attached [Private Network](/vpc/concepts/#private-networks), ensure that you enter the servers' private IP addresses. This is necessary in the case of a [private Load Balancer](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers), but may also be desired for public Load Balancers attached to Private Networks where backend servers are in the same VPC. As Load Balancers are compatible with [VPC routing](/vpc/reference-content/understanding-routing/), they will be able to direct requests to any backend server within the same VPC, via its private IP address. The Load Balancer and backend server do not have to be on the same Private Network in that VPC.
         </Message>
 
 3. Choose whether to activate **sticky sessions** (default setting is deactivated). Sticky sessions enable the Load Balancer to bind a given user's sessions to a specific backend server. If you choose to activate sticky sessions, you are prompted to select either **IP-based** (clients' IPs are used to bind sessions) or **cookie-based** (an HTTP cookie is used to bind sessions, and you must choose a name for the cookie).

pages/load-balancer/how-to/use-with-private-network.mdx

@@ -15,7 +15,7 @@ categories:
 
 The Private Network feature of the managed Load Balancers product lets you attach your Load Balancer to up to eight different Private Networks. [Scaleway Private Networks](/vpc/concepts/#private-networks) allow your cloud resources to communicate in an isolated and secure network. Load Balancers using Private Networks can communicate with their backend servers without using the public internet.
 
-[Private Load Balancers](/load-balancer/concepts/#private-load-balancer) must be connected to a Private Network in order to be functional, as they do not have a public IP address and can only receive requests from other resources on the Private Network. This is in contrast to public Load Balancers, which are accessible for requests via the internet through their public IP address, but can optionally use Private Networks to communicate with their backend servers. The procedure for attaching either a public or a private Load Balancer to a Private Network is the same, and described below.
+[Private Load Balancers](/load-balancer/concepts/#private-load-balancer) must be connected to a Private Network in order to be functional, as they do not have a public IP address and can only receive requests from other resources in the same VPC. This is in contrast to public Load Balancers, which are accessible for requests via the internet through their public IP address, but can optionally use Private Networks to communicate with their backend servers. The procedure for attaching either a public or a private Load Balancer to a Private Network is the same, and described below.
 
 <Macro id="requirements" />
 

pages/load-balancer/reference-content/public-private-accessibility.mdx

@@ -51,6 +51,6 @@ A private Load Balancer can be used to balance requests between backends interna
 
 <Lightbox src="scaleway-private-lb.webp" alt="" />
 
-When you attach a private Load Balancer to multiple Private Networks, it has an IP address in each one. The Load Balancer can then forward traffic to any resource or service attached to any of its Private Networks, thus allowing inter-Private-Networks load balancing. Scaleway's managed DNS also makes it possible to contact the Load Balancer over the Private Network without knowing its IP address (using `lb-name.pn-name`, which then resolves to its private IP address). [VPC routing](/vpc/concepts/#routing) also allows Load Balancers on different Private Networks in the same VPC to communicate.
+When you attach a private Load Balancer to multiple Private Networks, it has an IP address in each one. The Load Balancer can then forward traffic to any resource or service attached to any of its Private Networks, thus allowing inter-Private-Networks load balancing. Scaleway's managed DNS also makes it possible to contact the Load Balancer over the Private Network without knowing its IP address (using `lb-name.pn-name.internal`, which then resolves to its private IP address). [VPC routing](/vpc/concepts/#routing) also allows Load Balancers on different Private Networks in the same VPC to communicate.
 
 <Lightbox src="scaleway-privatelb-multipn.webp" alt="" />

pages/load-balancer/troubleshooting/configuration.mdx

@@ -51,7 +51,7 @@ The Load Balancer is unable to successfully communicate with the Elastic Metal b
 ### Solution
 
 - Check that your health checks and backend servers are correctly configured to work together.
-- Check that you have entered the correct [private IP address](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) for your Elastic Metal server, and that it is attached to the same Private Network as the Load Balancer.
+- Check that you have entered the correct [private IP address](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) for your Elastic Metal server, and that it is attached to a Private Network within the same VPC as the Load Balancer.
 - Elastic Metal servers require additional manual configuration of their network interface, unlike Instances and other resource types. Ensure you have [followed the necessary configuration steps](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks).