diff --git a/faq/vpc.mdx b/faq/vpc.mdx
index 742735eec6..77dda9fd28 100644
--- a/faq/vpc.mdx
+++ b/faq/vpc.mdx
@@ -5,7 +5,7 @@ meta:
 content:
   h1: VPC
 dates:
-  validation: 2024-05-28
+  validation: 2024-12-16
 category: network
 productIcon: VpcProductIcon
 ---
diff --git a/network/load-balancer/how-to/create-manage-flex-ips.mdx b/network/load-balancer/how-to/create-manage-flex-ips.mdx
index fc30a5be4b..793cb6bd8d 100644
--- a/network/load-balancer/how-to/create-manage-flex-ips.mdx
+++ b/network/load-balancer/how-to/create-manage-flex-ips.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to create and manage flexible IP addresses for your Scaleway Load Balancer
 tags: load-balancer flexible-ip failover-ip flex-ip ip-address reverse reverse-dns  
 dates:
-  validation: 2024-06-10
+  validation: 2024-12-16
   posted: 2023-12-05
 categories:
   - network
@@ -92,6 +92,4 @@ The steps below show how to delete a flexible IP that is not attached to a Load
 
 4. Click **Delete flexible IP** to confirm.
 
-    The flexible IP is deleted.
-
-
+    The flexible IP is deleted.
\ No newline at end of file
diff --git a/network/load-balancer/reference-content/public-private-accessibility.mdx b/network/load-balancer/reference-content/public-private-accessibility.mdx
index 6170409d1a..a876c1f971 100644
--- a/network/load-balancer/reference-content/public-private-accessibility.mdx
+++ b/network/load-balancer/reference-content/public-private-accessibility.mdx
@@ -1,16 +1,15 @@
 ---
 meta:
   title: Public vs private Load Balancers
-  description: Learn how to choose an appropriate accessibility setting for your Load Balancer
-content:
+  description: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favouring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer.
   h1: Public vs private Load Balancers
-  paragraph: Learn how to choose an appropriate accessibility setting for your Load Balancer
+  paragraph: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favoring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer.
 tags: load-balancer public private accessibility
 categories: 
   - load-balancer
   - network
 dates:
-  validation: 2024-06-14
+  validation: 2024-12-16
   posted: 2024-06-14
 ---
 
@@ -48,10 +47,10 @@ A Load Balancer is defined as private when you choose the "private" accessibilit
 - It does not allow the use of a Let's Encrypt [certificate](/network/load-balancer/concepts/#certificate) - only imported certificates are supported.
 - It does not support multi-cloud IP addresses for its backend servers, since it is not directly connected to the internet. Routes to them are thus, not guaranteed.
 
-A private Load Balancer can be used to balance requests between backends internally, where your backends' clients are in the same Private Network as the Load Balancer. The security of your infrastructure is strengthened, as the Load Balancer does not have a public IP address and is not accessible over the public internet.
+A private Load Balancer can be used to balance requests between backends internally, where your backends' clients are in the same VPC as the Load Balancer. The security of your infrastructure is strengthened, as the Load Balancer does not have a public IP address and is not accessible over the public internet.
 
 <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).
+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](/network/vpc/concepts/#routing) also allows Load Balancers on different Private Networks in the same VPC to communicate.
 
 <Lightbox src="scaleway-privatelb-multipn.webp" alt="" />
\ No newline at end of file