docs(gen): faq section titles harmonization p to w (#5565)

* docs(gen): faq section titles harmonization p to w

* Apply suggestion from @nerda-codes

Co-authored-by: Néda <[email protected]>

* Apply suggestion from @nerda-codes

Co-authored-by: Néda <[email protected]>

* Update pages/queues/faq.mdx

Co-authored-by: Rowena Jones <[email protected]>

* Update pages/serverless-sql-databases/faq.mdx

Co-authored-by: Néda <[email protected]>

* Update pages/public-gateways/faq.mdx

Co-authored-by: Rowena Jones <[email protected]>

* Apply suggestions from code review

Co-authored-by: Néda <[email protected]>

---------

Co-authored-by: Néda <[email protected]>
Co-authored-by: Rowena Jones <[email protected]>

Author: 3 people

pages/apple-silicon/how-to/adjust-available-bandwidth.mdx

@@ -10,7 +10,7 @@ categories:
   - bare-metal
 ---
 
-Every Mac mini comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 10Gbps, all with unlimited traffic.
+Every Mac mini comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 10 Gbps, all with unlimited traffic.
 
 <Macro id="requirements" />
 

pages/apple-silicon/how-to/use-private-networks.mdx

@@ -1,6 +1,6 @@
 ---
 title: How to use Private Networks with your Mac mini
-description: Learn how to get the most from the Private Networks 1Gbps feature for your Mac mini. Find out how to activate the feature, attach your Mac mini to Private Networks, and enable secure communication with your other Scaleway resources.
+description: Learn how to get the most from the Private Networks 1 Gbps feature for your Mac mini. Find out how to activate the feature, attach your Mac mini to Private Networks, and enable secure communication with your other Scaleway resources.
 tags: mac-mini mac-mini apple-silicon private-network vpc
 dates:
   validation: 2025-08-05
@@ -70,7 +70,7 @@ Once you have attached the resource, some manual configuration of the network in
 
 You must configure the virtual network interface on each Mac mini you have attached to a Private Network. Traffic from the public internet and traffic from a Private Network will pass through the same network interface of the Mac mini. We must therefore separate the traffic by adding a VLAN interface.
 
-To configure the interface, you must connect to your Mac mini, either via SSH or the remote desktop and carry out the instructions given.
+To configure the interface, you must connect to your Mac mini, either via SSH or the remote desktop, and carry out the instructions given.
 
 ### Via SSH and networksetup
 

pages/elastic-metal/faq.mdx

@@ -3,7 +3,7 @@ title: Elastic Metal FAQ
 description: Explore Scaleway Elastic Metal servers, pioneering 100% cloud bare metal solutions. Learn about billing, server ranges, installation guides, and more.
 hero: assets/elasticmetal.webp
 dates:
-  validation: 2025-09-23
+  validation: 2025-09-24
 productIcon: ElasticMetalProductIcon
 ---
 
@@ -42,6 +42,10 @@ Elastic Metal servers are available in the following regions and Availability Zo
 * Paris, France (`PAR-1` and `PAR-2`)
 * Warsaw, Poland (`WAW-2` and `WAW-3`)
 
+### Do you provide an IPv6 address by default with Elastic Metal?
+
+Yes, Elastic Metal servers are delivered with an IPv6 address (/128) pre-configured.
+
 ## Pricing and billing
 
 ### How am I billed for Elastic Metal servers?
@@ -75,10 +79,6 @@ It is not possible to get a cash refund of the engagement fees.
 
 ## Specifications
 
-### How long does it take to boot an Elastic Metal server?
-
-An Elastic Metal server is delivered to your account within a few minutes. You can then launch the server installation, which can take up to one hour.
-
 ### Which OSEs can be installed on Elastic Metal servers?
 
 We provide a range of Linux and Windows Server distributions for automatic installation from the Scaleway console.
@@ -88,7 +88,7 @@ We provide a range of Linux and Windows Server distributions for automatic insta
 Yes, you have the flexibility to modify the bandwidth available for your Elastic Metal server according to your requirements.
 Each Elastic Metal dedicated server comes with an allocated bandwidth allowance. However, you can easily increase or decrease this bandwidth through your Scaleway console at any time.
 
-Scaleway offers high-performance bandwidth options of up to 25Gbps per server, all of which include unlimited traffic.
+Scaleway offers high-performance bandwidth options of up to 25 Gbps per server, all of which include unlimited traffic.
 For step-by-step instructions on how to modify the available bandwidth for your Elastic Metal server, refer to our documentation on [how to modify the available bandwidth for an Elastic Metal server](/elastic-metal/how-to/adjust-available-bandwidth/).
 
 <Message type="note">
@@ -97,6 +97,10 @@ For step-by-step instructions on how to modify the available bandwidth for your
 
 ## Usage and management
 
+### How long does it take to boot an Elastic Metal server?
+
+An Elastic Metal server is delivered to your account within a few minutes. You can then launch the server installation, which can take up to one hour.
+
 ### How can I reinstall an Elastic Metal server?
 
 You can reinstall an Elastic Metal server with a few clicks at any time, [directly from your Scaleway console](/elastic-metal/how-to/install-server/).
@@ -139,10 +143,6 @@ Each failover IP consists of a `/64` IPv6 subnet (18,446,744,073,709,551,616 IPv
   When you configure the reverse DNS of a failover IPv6, the configuration is applied only to the first IP of each block (`XXXX:0`).
 </Message>
 
-### Do you provide an IPv6 address by default with Elastic Metal?
-
-Yes, Elastic Metal servers are delivered with an IPv6 address (/128) pre-configured.
-
 ### Can I attach Block Storage volumes to my Elastic Metal server?
 
 Elastic Metal is not currently compatible with Block Storage, but this functionality is planned for the future.

pages/elastic-metal/how-to/adjust-available-bandwidth.mdx

@@ -9,7 +9,7 @@ dates:
 import Requirements from '@macros/iam/requirements.mdx'
 
 
-Every Elastic Metal server comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 25Gbps, all with unlimited traffic.
+Every Elastic Metal server comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 25 Gbps, all with unlimited traffic.
 
 <Requirements />
 

pages/interlink/reference-content/overview.mdx

@@ -28,7 +28,7 @@ Scaleway plans to offer two types of InterLink, though currently only the **host
 
 A hosted InterLink is provisioned via a [partner](/interlink/concepts/#partner). Partners are telecom operators or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink.
 
-By choosing a hosted InterLink, you can re-use existing connectivity between a PoP where both you and the partner are present, and the Scaleway network. Layer 2 isolation to your Scaleway VPC is preserved, with guaranteed bandwidth (100Mbps - 25Gbps) across the InterLink.
+By choosing a hosted InterLink, you can re-use existing connectivity between a PoP where both you and the partner are present, and the Scaleway network. Layer 2 isolation to your Scaleway VPC is preserved, with guaranteed bandwidth (100 Mbps - 25 Gbps) across the InterLink.
 
 #### How to choose a partner
 
@@ -57,11 +57,11 @@ While each InterLink can only be attached to a single Scaleway VPC, it is possib
 
 ## Routing across an InterLink
 
-InterLink uses [**B**order **G**ateway **P**rotocol](/interlink/concepts/#border-gateway-protocol-bgp) to exchange routing information between the customer’s network and the Scaleway VPC. 
+InterLink uses [**B**order **G**ateway **P**rotocol](/interlink/concepts/#border-gateway-protocol-bgp) to exchange routing information between the customer’s network and the Scaleway VPC.
 
 Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes. This facilitates efficient traffic flow across the link towards these destinations, providing that [routing policies](#routing-policies) and [route propagation](#route-propagation) have been correctly set up.
 
-In fact, each InterLink has two BGP sessions: one for IPv4 and one for IPv6. Each session handles the exchange of IP prefixes for its respective IP version. The separation of these sessions ensures that IPv4 and IPv6 traffic can be managed independently, and provides compatibility with networks that may only support one of the IP versions. 
+In fact, each InterLink has two BGP sessions: one for IPv4 and one for IPv6. Each session handles the exchange of IP prefixes for its respective IP version. The separation of these sessions ensures that IPv4 and IPv6 traffic can be managed independently, and provides compatibility with networks that may only support one of the IP versions.
 
 When both BGP sessions are up, the InterLink has `Active` status. If one BGP session is up, and the other down, the status moves to `Limited Connectivity`. If both BGP sessions are down, the status is marked as `Down`. See the page on [InterLink statuses](/interlink/reference-content/statuses) for full information.
 
@@ -71,4 +71,4 @@ By default, **all route announcements from both sides are blocked** by InterLink
 
 ### Route propagation
 
-Even after attaching a routing policy, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/interlink/reference-content/configuring/) page for more information on route propagation. 
+Even after attaching a routing policy, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism, enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/interlink/reference-content/configuring/) page for more information on route propagation.

pages/public-gateways/faq.mdx

@@ -2,42 +2,37 @@
 title: Public Gateways FAQ
 description: Discover Scaleway Public Gateways and get answers to all your questions about IP addressing, bandwidth, regionalization and more.
 dates:
-  validation: 2025-05-05
+  validation: 2025-09-24
 productIcon: PublicGatewayProductIcon
 ---
 
-## What is a Public Gateway?
+## Overview
+
+### What is a Public Gateway?
 
 Public Gateways sit at the border of Private Networks. They provide services to deal with traffic entering and exiting the network (NAT), and SSH bastion. A Public Gateway can be attached to up to 8 Private Networks, and up to 50 Public Gateways are supported per [Organization](/organizations-and-projects/concepts/#organization).
 
 The Public Gateway can be configured through the console or the [API](https://www.scaleway.com/en/developers/api/public-gateway/).
 
-## Does the Public Gateway require a public IPv4 address?
-
-No. A public IPv4 address (aka. flexible IP) must be assigned to the Public Gateway at creation time, but you can detach it and delete it afterward if you do not require it to be publically accessible.
+## Offering and availability
 
-## Can my Instances and other resources access the internet via a Public Gateway without a public IP address?
-
-Yes. The Public Gateway can advertise itself as the [default route to the internet](/public-gateways/concepts/#default-route) over the Private Network it is attached to, so that Instances and other resources can access the internet via the gateway. Resources attached to other Private Networks than the gateway's network in the VPC can [opt in](/vpc/how-to/manage-routing/#how-to-manage-default-route-scope) to receive its default route advertisement.
-Moreover, the Public Gateway supports [static NAT](/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) (aka. port forwarding), so that ingress traffic from the public internet can reach Instances on the Private Network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the VPC.
-
-## What happened to static leases (DHCP reservations) when DHCP moved from the Public Gateway to Private Networks?
+### What happened to static leases (DHCP reservations) when DHCP moved from the Public Gateway to Private Networks?
 
 On 12 July 2023, DHCP functionality moved from Public Gateways to Private Networks. See our [dedicated migration documentation](/vpc/reference-content/vpc-migration/) for full details.
 
 Pre-existing static leases created via the Public Gateway were fully migrated and still work for your attached resources on a Private Network. Manual static lease configuration is still available via the API v1 and other developer tools, but this functionality is now deprecated, and does not exist in v2 of the API.
 
 Read our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) to learn how to put your gateway into IPAM-mode and replicate static DHCP reservation functionality with Scaleway IPAM.
 
-## Why is my Public Gateway labeled as Legacy?
+### Why is my Public Gateway labeled as Legacy?
 
 **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 a legacy gateway if you created it prior to 17 October 2023 and you never recreated it in IPAM mode. Legacy gateways are now deprecated, as they are incompatible with v2 of the Public Gateways API. Such gateways must be [moved to IPAM mode](/public-gateways/reference-content/understanding-v2/) before October 2025 to ensure ongoing functionality.
 
-## I received a message about v1 of the Public Gateways API being deprecated, do I need to take action?
+### I received a message about v1 of the Public Gateways API being deprecated, do I need to take action?
 
-The Public Gateways API v1 is now deprecated, and will be removed on 1 October 2025. Only IPAM-mode gateways will be compatible with the new version of the API (v2). Whether or not you need to take action depends on the following two points:
+The Public Gateways API v1 is now deprecated, and will be removed on 1 November 2025. Only IPAM-mode gateways will be compatible with the new version of the API (v2). Whether or not you need to take action depends on the following two points:
 
 - Consider whether you manage your Public Gateway uniquely via the Scaleway console, or via calls to the API/devtools in code and scripts:
 
@@ -53,16 +48,33 @@ The Public Gateways API v1 is now deprecated, and will be removed on 1 October 2
 
 See our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) for full details.
 
-## Do I need a Public Gateway for each Availability Zone (AZ)?
+## Specifications
+
+### Does the Public Gateway require a public IPv4 address?
+
+No. A public IPv4 address (also known as flexible IP) must be assigned to the Public Gateway at creation time, but you can detach it and delete it afterward if you do not need it to be publicly accessible.
+
+### Do I need a Public Gateway for each Availability Zone (AZ)?
 
 VPC and Private Networks are both [regional](/public-gateways/concepts/#region-and-availability-zone), meaning they span all AZs across a given region. Even though Public Gateways are zoned and not regional, one Public Gateway attached to a regional Private Network is functionally enough, and will cover the whole region. That is to say a Public Gateway created in PAR-1 can serve Instances in PAR-2 and PAR-3, as long as they are all attached to the same PAR-region Private Network.
 
-## How can I achieve truly High Availability (HA) networking when the Public Gateway is a zoned resource? 
+## Access and security
+
+### Can my Instances and other resources access the internet via a Public Gateway without a public IP address?
+
+Yes. The Public Gateway can advertise itself as the [default route to the internet](/public-gateways/concepts/#default-route) over the Private Network it is attached to, so that Instances and other resources can access the internet via the gateway. Resources attached to other Private Networks than the gateway's network in the VPC can [opt in](/vpc/how-to/manage-routing/#how-to-manage-default-route-scope) to receive its default route advertisement.
+Moreover, the Public Gateway supports [static NAT](/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) (also known as port forwarding), so that ingress traffic from the public internet can reach Instances on the Private Network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the VPC.
+
+## Usage and management
+
+### How can I achieve High Availability (HA) networking when the Public Gateway is a zoned resource?
 
 Notwithstanding the answer to the previous question, if you have a single Public Gateway in, for example, PAR-1, serving resources from other AZs on the same Private Network and there is an outage in the PAR-1 zone, the gateway will not be able to serve the resources from other unaffected AZs. We are working to improve and develop our Public Gateway product to counteract this.
 
 In the meantime, if this is a concern, you could consider attaching several Public Gateways from different AZs to a single Private Network, each advertising a default route to the internet. As long as you are using a recent kernel (e.g. Ubuntu Jammy, Debian bookworm), the traffic will be spread across the different gateways. In the case of an outage in one AZ, you will only lose the gateway in that zone, and the others will continue to serve traffic.
 
-## I need more than 1Gbps bandwidth for my Public Gateway, what can I do?
+## Support and troubleshooting
+
+### I need more than 1 Gbps bandwidth for my Public Gateway, what can I do?
 
-We have introduced a `VPC-GW-L` offer with 3Gbps bandwidth, and a `VPC-GW-XL` offer with 10Gbps of bandwidth, to accommodate customers with this type of need. For pricing details, see our [dedicated page](https://www.scaleway.com/en/pricing/network/). You can upgrade your existing Public Gateway to one of these new offers via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-upgrade-a-public-gateway-to-the-latest-version-andor-to-a-different-commercial-offer-type) or the [Scaleway console](/public-gateways/how-to/upgrade-public-gateway/).
+We have introduced a `VPC-GW-L` offer with 3 Gbps bandwidth, and a `VPC-GW-XL` offer with 10 Gbps of bandwidth, to accommodate customers with this type of need. For pricing details, see our [dedicated page](https://www.scaleway.com/en/pricing/network/). You can upgrade your existing Public Gateway to one of these new offers via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-upgrade-a-public-gateway-to-the-latest-version-andor-to-a-different-commercial-offer-type) or the [Scaleway console](/public-gateways/how-to/upgrade-public-gateway/).