fix(faq): review faqs

faq/loadbalancer.mdx

@@ -1,35 +1,35 @@
 ---
 meta:
   title: Load Balancer FAQ
-  description: Discover Scaleway Load Balancer and its multicloud feature.
+  description: Discover Scaleway Load Balancer and find the answers to all your questions about flexible IP addresses, IPv6, multicloud offers and more. 
 content:
   h1: Load Balancer
 hero: assets/loadbalancer.webp
 dates:
-  validation: 2024-03-18
+  validation: 2024-09-25
 category: network
 ---
 
 ## What is a Load Balancer?
 
-Load Balancers are highly available and fully managed Instances which distribute the workload among your servers. 
-They ensure the scaling of applications while securing their continuous availability. They are commonly used to improve the performance and reliability of websites, applications, databases, and other services by distributing the workload across multiple servers.
-It monitors the availability of your backend servers, detects if a server fails and rebalances the load between the rest of the servers, making your applications highly available for users.
+Load Balancers are highly available and fully managed Instances, configured to distribute workload across a set of backend servers. They ensure the scaling of applications while securing their continuous availability. Load Balancers are therefore commonly used to improve the performance and reliability of websites, applications, databases, and other services.
+Scaleway Load Balancer monitors the availability of your backend servers via health checks. If it detects that a server is down, it rebalances the load between the rest of the servers, making your applications highly available for users.
 
-A Load Balancer can be used as frontend for any Instance type, even if they do not belong to Scaleway thanks to the [multicloud feature](/faq/loadbalancer/#what-is-the-difference-between-multicloud-and-non-multicloud-offers).
+A Load Balancer can be used as frontend for any Instance type, even if it is not a Scaleway resource, thanks to the [multicloud feature](/faq/loadbalancer/#what-is-the-difference-between-multicloud-and-non-multicloud-offers).
 
 ## Can I use Load Balancers with other products? 
 
-See our documentation on [using a Load Balancer to expose a Kubernetes Kapsule](/containers/kubernetes/reference-content/kubernetes-load-balancer/).
+Yes: Check out our documentation on:
+- [Using a Load Balancer to expose a Kubernetes Kapsule](/containers/kubernetes/reference-content/kubernetes-load-balancer/).
+- [Setting up caching for your Load Balancer via Edge Services](/network/edge-services/quickstart/)
 
 ## What is a flexible IP address?
 
-Your frontend listens to your Load Balancer's public flexible IP address. In case of a failure of the Load Balancer, a replica Load Balancer is immediately spawned and deployed, and the IP address is automatically rerouted to this replica. This is done automatically, by the Load Balancer control subsystems.
+By default, each [public](/network/load-balancer/concepts/#accessibility) Load Balancer is created automatically with a flexible IPv4 address. This is a public IP that can be held in your account even after you delete your Load Balancer. You can optionally also add an IPv6 address.
 
-By default, each [public](/network/load-balancer/concepts/#accessibility) Load Balancer is created automatically with a flexible IPv4 address. You can optionally also add an IPv6 address.
+Your frontend listens to your Load Balancer's public flexible IP address. In case of a failure of the Load Balancer, a replica Load Balancer is immediately spawned and deployed, and the IP address is automatically rerouted to this replica. This is done automatically, by the Load Balancer control subsystems.
 
-When you delete a Load Balancer, you can choose to keep its flexible IP(s) in your account, to reuse later with a new Load Balancer. These 
-flexible IPs are not compatible with other Scaleway products (e.g. Instances, Elastic Metal servers, Public Gateways): each resource has its own set of flexible IPs.
+When you delete a Load Balancer, you can choose to keep its flexible IP(s) in your account, to reuse later with a new Load Balancer. These flexible IPs are not compatible with other Scaleway products (e.g. Instances, Elastic Metal servers, Public Gateways): each resource has its own set of flexible IPs.
 
 ## Can I have more than one flexible IP address for a Load Balancer?
 
@@ -46,31 +46,36 @@ If you want to know more about the failover system, read [our article about stre
 
 ## Do backend servers require a public IP address?
 
-No, it is not required. You can use private Scaleway IPs on your backend servers if they are hosted in the same Availability Zone (AZ) as the Load Balancer.
+No, this is not necessary. Your Load Balancer can reach your backend servers via their private IP addresses on a Private Network, as long as the Load Balancer and servers are all in the same region.
 
 ## What is the difference between multicloud and non multicloud offers?
 
-Multicloud means that you can add as many 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 datacenter.
+Multicloud 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 datacenter.
 
 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.
 
+To take advantage of multicloud, you must choose a compatible Load Balancer offer type when creating your Load Balancer, or [resize](/network/load-balancer/how-to/resize-lb/) to such an offer afterwards.
+
 ## What are the communication protocols currently supported?
 
 All protocols based on `TCP` are supported. This includes `database`, `HTTP`, `LDAP`, `IMAP` and so on. You can also specify `HTTP` to benefit from support and features that are exclusive to this protocol.
 
 ## Is it possible to add security to restrict access to a URL or port on the Load Balancer?
 
-Yes, you can restrict the use of a `TCP` port or `HTTP` URL via `ACLS`. Find more information in our [developers documentation](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-acls).
+Yes, you can restrict the use of a `TCP` port or `HTTP` URL using ACLs. Find more information in our [ACL documentation](/network/load-balancer/how-to/create-manage-acls/).
 
 ## What is a route?
 
 Once you have created one or more Load Balancers, you can create routes. Routes indicate how to direct incoming connections to certain backends based on various parameters such as IP addresses, path, host, etc. You can choose the frontend to which the rule should apply, and the backend it should direct to. Routes can be based on **Server Name Indication** (SNI) for TCP Load Balancers, or the **HTTP Host header** for HTTP Load Balancers. Check out our [dedicated documentation](/network/load-balancer/how-to/create-manage-routes/) for more information.
 
+## Can I add multiple backends to a frontend?
+
+Yes, this is possible using routes. When you create a frontend, you must select a "default" backend, to which it forwards traffic when the request doesn't match any configured route. But via the **routes** tab for your frontend in the Scaleway console, you can create routes to different backends from the same frontend. Routes are currently supported based on the value of the `Host` header of incoming HTTP requests for HTTP backends, or on SNI for TCP backends.
+
 ## What is a health check?
 
-A health check is one of the core concepts for a well-functioning Load Balancer. It is a predefined request which periodically checks whether the server is in a healthy state or an unhealthy state. Only servers that respond correctly to the health check receive client requests. When the Load Balancer determines that an Instance is unhealthy, it stops routing requests to that Instance. Currently, our Load Balancer supports `TCP` and `TCP-based` health checks such as `HTTP(S)`, `LDAP`, `REDIS`, etc.
+A health check is one of the core concepts for a well-functioning Load Balancer. It is a predefined request which periodically checks whether the server is in a healthy state or an unhealthy state. Only servers that respond correctly to the health check receive client requests. When the Load Balancer determines that an Instance is unhealthy, it stops routing requests to that Instance. Currently, our Load Balancer supports `TCP` and `TCP-based` health checks such as `HTTP(S)`, `LDAP`, `REDIS`, etc. [Find out more about health checks](/network/load-balancer/reference-content/configuring-health-checks/).
 
-## Can I add multiple backends to a frontend?
+## Can I set up a caching service for my load balanced application?
 
-Yes, this is possible using routes. When you create a frontend, you must select a "default" backend, which it forwards traffic to when the request doesn't match any configured route. But via the **routes** tab for your frontend in the Scaleway console, you can create routes to different backends from the same frontend. Routes are currently supported based on the value of the `Host` header of incoming HTTP requests for HTTP backends, or on SNI for TCP backends.
+Yes, this is possible with Scaleway's [Edge Services](/network/edge-services/) product, currently in Public Beta. By creating an Edge Services pipeline for your Load Balancer, you can access Edge Services caching service reduce load on your origin. 

faq/messaging-and-queuing.mdx

@@ -1,13 +1,12 @@
 ---
 meta:
   title: Messaging and Queuing FAQ
-  description: Discover Scaleway Messaging and Queuing.
+  description: Discover Scaleway Messaging and Queuing, and get answers to common questions about the different protocols available, compatibility with various services, and billing.
 content:
   h1: Messaging and Queuing
 hero: assets/messaging.webp
 dates:
-  validation: 2024-03-18
-category: serverless
+  validation: 2024-09-125category: serverless
 ---
 
 ## What are NATS, SNS and SQS?
@@ -43,12 +42,6 @@ Messaging and Queuing namespaces have been removed.
 
 The new version of Messaging and Queuing is designed to provide a better and more secure experience, as well as preparing Messaging and Queuing for further integration into the Scaleway ecosystem.
 
-## Why can't I see my SQS or SNS resources in the console anymore?
-
-The console now points to the new and improved version of Messaging and Queuing, `v1beta1`. Any SQS or SNS resources created with the API or the console prior to the date of SQS and NATS going into General Availability, existed within the old `v1alpha1` version of Messaging and Queuing which has now been deprecated.
-
-All users were warned to **[activate the SQS and/or SNS protocol(s)](/serverless/messaging/how-to/get-started/#how-to-activate-sqs-or-sns)** for their Scaleway Project via the v1beta1 version of the API or the console, and **recreate their resources** (credentials, queues etc) in this new version.
-
 ## Can I still keep using the old v1alpha1 API?
 
 The v1alpha1 API has now been deprecated, and all resources still existing in it deleted.

faq/private-networks.mdx

@@ -1,12 +1,12 @@
 ---
 meta:
   title: Private Networks FAQ
-  description: Discover Private Networks.
+  description: Discover Scaleway Private Networks, and find answers to all your questions about attaching resources, how IP addressing works, and other configuration details.
 content:
   h1: Private Networks
 hero: assets/private-networks.webp
 dates:
-  validation: 2024-03-18
+  validation: 2024-09-25
 category: network
 ---
 
@@ -16,9 +16,13 @@ Private Networks are a managed cloud service allowing you to create layer 2 ethe
 
 These domains can also be called virtual LAN (VLAN). They are virtual but completely private local networks that securely connect your Scaleway resources without necessarily exposing them publicly. Scaleway resources including Instances, Elastic Metal servers, Load Balancers, and Databases are all compatible with Private Networks.
 
-## Can I connect multiple Private Networks on the same Scaleway resource?
+## What's the difference between Private Networks and VPC?
 
-Yes, you can configure multiple Private Networks on the same Scaleway resource. For example, in the case of Instances, you can connect multiple Private Networks to the same Instance. A virtual network interface is created for each Private Network the Instance is attached to. You can then bring up each of them as indicated in our [documentation](/compute/instances/how-to/use-private-networks/#how-to-configure-the-private-network-interface-on-your-instances). For Elastic Metal, check out our documentation on [configuring the network interface](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks).
+Scaleway VPC offers layer 3 network isolation, while layer 2 Private Networks are created inside a given VPC. See the VPC FAQ for [more information](/faq/vpc/).
+
+## Can I connect multiple Private Networks to the same Scaleway resource?
+
+Yes, you can configure multiple Private Networks on the same Scaleway resource. For example, you can connect up to 8 Private Networks to the same Instance. A virtual network interface is created for each Private Network the Instance is attached to. For Elastic Metal, some additional configuration is required: check out our documentation on [configuring the network interface](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks).
 
 You can configure:
 - Up to 8 Private Networks per Scaleway resource
@@ -31,20 +35,22 @@ No, Private Network interfaces will appear on your resources without any reboot.
 
 ## Does Private Network support IPv6?
 
-Yes, you can configure IPv6 within Private Networks. To use it, the netmask should always be `/64` and we recommend using `fc00::/7` unique [local address (ULA)](https://en.wikipedia.org/wiki/Unique_local_address) range. ULA IPv6 address generators are widely available to generate a personalized range.
+Yes, when you create a Private Network both an IPv4 and an IPv6 CIDR block are defined. The IPv6 CIDR block is defined automatically and "invisibly" by default at the time of creating the Private Network. It cannot be modified either at the time of creation, or afterward.
+
+It is a `/64 block`, guaranteed to be unique within the VPC and not overlapping with any of your other Private Networks. Resources that support private IPv6 addressing, e.g. Instances, can then acquire an IPv6 address when they join the Private Network.
 
 ## Do resources in a Private Network require a public IPv4 address?
 
 No, they do not require a public IPv4 address.
 
 ## Can resources in a Private Network access the internet without a public IPv4 address?
 
-Yes. You can attach a Public Gateway to your Private Network and enable NAT to provide internet access to your Instances, Elastic Metal servers, and other Scaleway resources.
+Yes. You can attach a [Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) to your Private Network to provide internet access to your Instances, Elastic Metal servers, and other attached Scaleway resources.
 
-## Do Non-IP protocols work Over Private Networks?
+## Do non-IP protocols work over Private Networks?
 
 Technically, any ethernet payload should work over Private Networks. However, only IPv4 and IPv6 are officially supported. If you have real use cases for other protocols, let us know by reaching us on the [Scaleway Community Slack](https://scaleway-community.slack.com/).
 
 ## Do Private Networks support IP autoconfiguration?
 
-Yes. You can attach a Public Gateway to your Private Network and enable DHCP to provide IP autoconfiguration for your resources.
+Yes, DHCP is an inbuilt function of Private Networks and provides IP autoconfiguration for your attached resources. Alternatively, you can use Scaleway IPAM to [reserve specific IP addresses](/network/ipam/how-to/reserve-ip/) on a Private Network and use these to attach resources.