fix(docs): review

Author: RoRoJ

pages/load-balancer/faq.mdx

@@ -5,7 +5,7 @@ meta:
 content:
   h1: Load Balancer FAQ
 dates:
-  validation: 2024-09-25
+  validation: 2025-03-31
 category: network
 productIcon: LbProductIcon
 ---
@@ -58,7 +58,7 @@ No, this is not necessary. Your Load Balancer can reach your backend servers via
 
 ## What is the difference between multi-cloud and non multi-cloud offers?
 
-Multi-cloud means that you can backend servers that are neither Instances, nor Elastic Metal servers, nor Dedibox dedicated servers. These can be services from other cloud platforms such as Amazon Web Services, Digital Ocean, Google Cloud, Microsoft Azure or OVH, but also on-premises servers hosted in a third-party data center.
+Multi-cloud means that you can add backend servers that are neither Instances, nor Elastic Metal servers, nor Dedibox dedicated servers. These can be services from other cloud platforms such as Amazon Web Services, Digital Ocean, Google Cloud, Microsoft Azure or OVH, but also on-premises servers hosted in a third-party data center.
 
 Unlike the multi-cloud offers, non-multi-cloud offers allow you to add only backend servers part of the Scaleway ecosystems which include Instances, Elastic Metal servers, and Dedibox dedicated servers.
 
@@ -92,4 +92,4 @@ Yes, this is possible with Scaleway's [Edge Services](/edge-services/) product,
 
 ## How can I add extra security such as a firewall or anti-DDOS to my Load Balancer?
 
-This will be available soon via [Edge Services](/edge-services/), watch this space.
+You can add a **W**eb **A**pplication **F**irewall to your Load Balancer using Scaleway Edge Services. [See the documentation](/edge-services/reference-content/understanding-waf/).

pages/public-gateways/faq.mdx

@@ -5,7 +5,7 @@ meta:
 content:
   h1: Public Gateways FAQ
 dates:
-  validation: 2024-09-25
+  validation: 2025-03-31
 category: network
 productIcon: PublicGatewayProductIcon
 ---
@@ -33,7 +33,7 @@ Pre-existing static leases created via the Public Gateway were fully migrated an
 
 ## Why is my Public Gateway labelled as Legacy?
 
-**Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatiblity with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources
+**Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatibility with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources
 
 Your gateway is probably a legacy gateway if you created it prior to 17 October 2023. These gateways will continue to function, but are not natively integrated with IPAM, and you cannot take advantage of features such as IP management via Scaleway [IPAM](/ipam/), or fully-isolated Kubernetes Kapsules. You should create a new gateway if you want to benefit from such features.