fix(docs): doc review

RoRoJ · RoRoJ · commit 65aa1325b5ed · 2025-09-22T15:50:09.000+02:00
diff --git a/pages/edge-services/concepts.mdx b/pages/edge-services/concepts.mdx
@@ -3,8 +3,8 @@ title: Edge Services - Concepts
 description: Understand Scaleway Edge Services terminology with our glossary of the core concepts underpinning this product. Learn about key features, architecture, and best practices.
 tags: edge-services edge services pipeline custom-domain cache
 dates:
-  creation: 2025-09-11
-  validation: 2025-03-03
+  creation: 2024-07-24
+  validation: 2025-09-22
 ---
 import image from './assets/scaleway-edge-services-pipeline.webp'
 
diff --git a/pages/edge-services/troubleshooting/certificate-errors.mdx b/pages/edge-services/troubleshooting/certificate-errors.mdx
@@ -3,7 +3,7 @@ title: I am experiencing problems with my Edge Services certificate
 description: Troubleshoot issues that may arise when adding an SSL/TLS certificate so that Scaleway Edge Services can serve content over HTTPS for your custom domain.
 tags: edge-services custom domain certificate ssl lets-encrypt
 dates:
-  validation: 2025-03-14
+  validation: 2025-09-22
   posted: 2025-03-14
 ---
 
diff --git a/pages/edge-services/troubleshooting/cname-errors.mdx b/pages/edge-services/troubleshooting/cname-errors.mdx
@@ -3,7 +3,7 @@ title: I am experiencing problems with my Edge Services CNAME record
 description: Troubleshoot issues that may arise when adding an CNAME record so that Scaleway Edge Services can serve content over HTTPS for your custom domain.
 tags: edge-services custom domain cname record dns
 dates:
-  validation: 2025-03-14
+  validation: 2025-09-22
   posted: 2025-03-14
 ---
 import image from './assets/scaleway-edge-services-cname-error.webp'
diff --git a/pages/edge-services/troubleshooting/index.mdx b/pages/edge-services/troubleshooting/index.mdx
@@ -3,7 +3,7 @@ title: Edge Services
 description: Find troubleshooting resources for resolving issues with Scaleway Edge Services. Get your pipelines running smoothly with our guides.
 dates:
   posted: 2025-03-14
-  validation: 2025-03-14
+  validation: 2025-09-22
 productIcon: EdgeServicesProductIcon
 ---
 
diff --git a/pages/generative-apis/api-cli/using-chat-api.mdx b/pages/generative-apis/api-cli/using-chat-api.mdx
@@ -3,12 +3,16 @@ title: Using Chat API
 description: This page explains how to use the Chat API to query models
 tags: generative-apis ai-data chat-api
 dates:
-  validation: 2025-03-11
+  validation: 2025-09-22
   posted: 2024-09-03
 ---
 
 Scaleway Generative APIs are designed as a drop-in replacement for the OpenAI APIs. If you have an LLM-driven application that uses one of OpenAI's client libraries, you can easily configure it to point to Scaleway Chat API, and get your existing applications running using open-weight instruct models hosted at Scaleway.
 
+<Message type="note">
+You can also try the **Responses** API for LLM-driven tasks. Released in 2025, it is designed to combine the simplicity of Chat Completions with the ability to do more agentic tasks and reasoning. Scaleway's support for the Responses API is currently at beta stage. [Find out more about the Responses API](/generative-apis/how-to/query-language-models/#chat-completions-api-or-responses-api).
+</Message>
+
 ## Create chat completion
 
 Creates a model response for the given chat conversation.
diff --git a/pages/generative-apis/api-cli/using-embeddings-api.mdx b/pages/generative-apis/api-cli/using-embeddings-api.mdx
@@ -3,7 +3,7 @@ title: Using Embeddings API
 description: This page explains how to use the Embeddings API
 tags: generative-apis ai-data embeddings-api
 dates:
-  validation: 2025-03-11
+  validation: 2025-09-22
   posted: 2024-09-03
 ---
 
diff --git a/pages/generative-apis/api-cli/using-models-api.mdx b/pages/generative-apis/api-cli/using-models-api.mdx
@@ -3,7 +3,7 @@ title: Using Models API
 description: This page explains how to use the Models API
 tags: generative-apis ai-data embeddings-api
 dates:
-  validation: 2025-03-11
+  validation: 2025-09-22
   posted: 2024-09-02
 ---
 
diff --git a/pages/generative-apis/reference-content/model-lifecycle.mdx b/pages/generative-apis/reference-content/model-lifecycle.mdx
@@ -3,7 +3,7 @@ title: Understand Generative APIs model lifecycle
 description: Learn about the lifecycle of generative AI models in Scaleway. This page explains how each status affects model usage and updates, ensuring you are informed about transitions and how to access the latest model versions.
 tags: generative-apis ai-data model-lifecyle
 dates:
-  validation: 2025-03-11
+  validation: 2025-09-22
   posted: 2024-09-02
 ---
 
diff --git a/pages/ipam/quickstart.mdx b/pages/ipam/quickstart.mdx
@@ -3,7 +3,7 @@ title: IPAM - Quickstart
 description: This page shows you how to get started with Scaleway IPAM.
 tags: ipam ip-address-management internet-protocol private-ip public-ip flexible-ip list-ips book-ip 
 dates:
-  validation: 2025-03-12
+  validation: 2025-09-22
   posted: 2021-05-30
 ---
 import image from './assets/scaleway-ipam-moreinfo.webp'
diff --git a/pages/load-balancer/how-to/create-manage-routes.mdx b/pages/load-balancer/how-to/create-manage-routes.mdx
@@ -3,7 +3,7 @@ title: How to create and manage routes
 description: Learn how to efficiently create and manage routes with Scaleway's Load Balancer, ensuring seamless traffic distribution and enhanced network performance.
 tags: route rules load-balancer sni host-header target-backend
 dates:
-  validation: 2025-09-11
+  validation: 2025-09-22
   posted: 2023-02-08
 ---
 import Requirements from '@macros/iam/requirements.mdx'
diff --git a/pages/load-balancer/how-to/use-edge-services.mdx b/pages/load-balancer/how-to/use-edge-services.mdx
@@ -2,7 +2,7 @@
 title: How to create an Edge Services pipeline for a Load Balancer
 description: This page explains how to configure an Edge Services pipeline on your Load Balancer, enabling a caching service for faster and more efficient delivery.
 dates:
-  validation: 2025-09-11
+  validation: 2025-09-22
   posted: 2024-10-15
 tags: load-balancer edge-services cdn network cache domain https
 ---
@@ -52,5 +52,6 @@ See the dedicated Edge Services section of the documentation for help with:
 
 - [Customizing your Edge Services endpoint](/edge-services/how-to/configure-custom-domain/)
 - [Configuring your Edge Services cache](/edge-services/how-to/configure-cache/)
+- [Configuring WAF for Edge Services](/edge-services/how-to/configure-waf/)
 
 To go further, browse our full range of Edge Services documentation on the [Edge Services Overview](/edge-services/) page.
diff --git a/pages/load-balancer/troubleshooting/certificates.mdx b/pages/load-balancer/troubleshooting/certificates.mdx
@@ -3,7 +3,7 @@ title: I am having problems with my Load Balancer's certificate
 description: Troubleshoot errors that you may experience when creating an SSL/TLS certificate, adding it to your Load Balancer frontend, or successfully handling HTTPS connections.
 tags: load-balancer certificate ssl tls dns
 dates:
-  validation: 2025-03-10
+  validation: 2025-09-22
   posted: 2025-03-10
 ---
 
diff --git a/pages/load-balancer/troubleshooting/configuration.mdx b/pages/load-balancer/troubleshooting/configuration.mdx
@@ -3,7 +3,7 @@ title: I am having problems configuring my Load Balancer
 description: Troubleshoot problems that you may experience when configuring your Load Balancer, such as adding backend servers, setting up Private Networks and dealing with security concerns.
 tags: load-balancer configuration backend server error security ip
 dates:
-  validation: 2025-09-11
+  validation: 2025-09-22
   posted: 2025-03-06
 ---
 
@@ -48,7 +48,6 @@ The Load Balancer is unable to successfully communicate with the Elastic Metal b
 - 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).
 
-
 ## My Load Balancer's IP address is appearing in the backend application's logs, instead of the real client IP address.
 
 You may find that as requests are passed from the client, through the Load Balancer, to your backend servers, that the client's original IP address is replaced with the Load Balancer's IP address in your backend application's logs. This is problematic if you need the original IP address for localization, security or other purposes.
diff --git a/pages/load-balancer/troubleshooting/http-connection-errors.mdx b/pages/load-balancer/troubleshooting/http-connection-errors.mdx
@@ -3,7 +3,7 @@ title: I am experiencing connection problems and HTTP errors with my Load Balanc
 description: Troubleshoot connection problems and HTTP errors that you may experience when accessing applications served via your Load Balancer. Learn how to resolve common problems and get your application back up and running.
 tags: load-balancer http-errors bad-request
 dates:
-  validation: 2025-09-11
+  validation: 2025-09-22
   posted: 2025-03-06
 ---
 
diff --git a/pages/load-balancer/troubleshooting/index.mdx b/pages/load-balancer/troubleshooting/index.mdx
@@ -3,7 +3,7 @@ title: Load Balancer
 description: Find troubleshooting resources for resolving issues with Scaleway Load Balancers.
 dates:
   posted: 2025-03-14
-  validation: 2025-03-14
+  validation: 2025-09-22
 productIcon: LbProductIcon
 ---
 
diff --git a/pages/load-balancer/troubleshooting/k8s-errors.mdx b/pages/load-balancer/troubleshooting/k8s-errors.mdx
@@ -3,7 +3,7 @@ title: I am experiencing problems with my Kubernetes Load Balancer
 description: Troubleshoot problems with your Kubernetes Load Balancer. Discover the solutions to common errors, and get your Load Balancer service back up and running.
 tags: load-balancer kubernetes annotations
 dates:
-  validation: 2025-09-11
+  validation: 2025-09-22
   posted: 2025-03-06
 ---
 
diff --git a/pages/public-gateways/how-to/upgrade-public-gateway.mdx b/pages/public-gateways/how-to/upgrade-public-gateway.mdx
@@ -3,7 +3,7 @@ title: How to upgrade a Public Gateway
 description: Find out how to upgrade your Scaleway Public Gateway to a more powerful commercial offer type, with just a couple of clicks in the Scaleway console.
 tags: public-gateway upgrade bandwidth offer
 dates:
-  validation: 2025-03-12
+  validation: 2025-09-22
   posted: 2024-09-02
 ---
 import Requirements from '@macros/iam/requirements.mdx'
diff --git a/pages/public-gateways/reference-content/understanding-v2.mdx b/pages/public-gateways/reference-content/understanding-v2.mdx
@@ -3,7 +3,7 @@ title: Understanding and preparing for Public Gateways v2
 description: Find out what to expect from Public Gateways v2, and get ready for deprecation of DHCP entries and the DHCP object, as well as new default behavior for IPAM mode.
 tags: public-gateways dhcp dhcp-entries api v2 ipam-mode legacy
 dates:
-  creation: 2025-01-23
+  creation: 2025-09-22
   validation: 2025-08-07
 ---
 import image from './assets/scaleway-pgw-listing.webp'
@@ -25,12 +25,12 @@ All Scaleway Public Gateways until now have been created and managed with the ve
 | Supports [IPAM-mode PGWs](/public-gateways/concepts/#ipam) | Yes ✅ | Yes ✅|
 | Supports SSH bastion allowed IPs, and future new features | No ❌| Yes ✅ |
 | Deprecated? | Yes ✅ | No ❌|
-| Removal date | 1 Oct 2025 | --- |
-| Compatible with PGW management via Scaleway console? | Only until 1 Oct 2025 | Yes ✅ |
+| Removal date | 1 Nov 2025 | --- |
+| Compatible with PGW management via Scaleway console? | Only until 1 Nov 2025 | Yes ✅ |
 
-After a deprecation period ending on 1 Oct 2025, the Public Gateways API v1 and associated developer tools will be removed. 
+After a deprecation period ending on 1 Nov 2025, the Public Gateways API v1 and associated developer tools will be removed. 
 
-**What you need to do before 1 Oct 2025:**
+**What you need to do before 1 Nov 2025:**
 
 - Ensure that your Public Gateway is in [IPAM mode](#ipam-mode-becomes-default). Only IPAM-mode gateways are compatible with v2.
 
@@ -79,7 +79,7 @@ Scaleway Public Gateways are either in **Legacy mode** or **IPAM mode**. You can
 <Lightbox image={image} alt="A screen in the Scaleway console shows a listing of two Public Gateways, one of which has a badge saying IPAM, the other a badge saying Legacy." />
 
 <Message type="tip">
-All Public Gateways created via the Scaleway console since 17 October 2023 are necessarily in IPAM mode.
+All Public Gateways created via the Scaleway console since 17 November 2023 are necessarily in IPAM mode.
 </Message>
 
 Legacy Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure IPAM compatibility. IPAM-mode Public Gateways are fully integrated with Scaleway's [IPAM](/ipam/concepts/#ipam), which manages the coherent assignment of IP addresses to the gateway itself, and resources on attached Private Networks.
@@ -131,7 +131,7 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also
     You will be able to list and manage all gateways with the **Scaleway console**, which will adapt to use v1 or v2 of the API as necessary depending on whether or not the gateway is in IPAM mode.
     </Message>
 
-- **8 April 2025 - 1 Oct 2025: Migration period**: You have a six month migration period to complete the following actions
+- **8 April 2025 - 1 Nov 2025: Migration period**: You have a six month migration period to complete the following actions
 
     - Ensure that your Public Gateway is in [IPAM mode](/public-gateways/concepts/#ipam). Only IPAM mode gateways are compatible with v2.
     - Put any non-IPAM mode ([legacy](/public-gateways/concepts/#ipam)) Public Gateways in IPAM-mode, by using the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md).
@@ -140,15 +140,15 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also
 
     If your Public Gateway is already in IPAM mode, and you only manage it via the console, you will not be affected by these changes and you do not need to take any action.
 
-- **1 Oct 2025 - V1 removal**: The Public Gateway v1 API will be removed. Any code or scripts still pointing to v1 will cease to function. We will automatically put any existing legacy Public Gateways into IPAM mode.
+- **1 Nov 2025 - V1 removal**: The Public Gateway v1 API will be removed. Any code or scripts still pointing to v1 will cease to function. We will automatically put any existing legacy Public Gateways into IPAM mode.
 
 ## FAQ
 
 ### How do I know if I have to take action?
 
 - Consider whether you manage your Public Gateway uniquely via the Scaleway console, or via calls to the API/devtools in code and scripts:
 
-  - **Code and scripts**: If you have any code or scripts that call v1 of the API, or use devtool functionality that is removed from v2 such as DHCP object or entries, **you must take action before 1 Oct 2025**. Update your code and scripts so they point to v2 of the API. [Follow the examples provided for tools such as Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) to rewrite your devtool templates so they do not refer to removed functionalities. Do this in synchronization with moving your gateway to IPAM mode (if necessary).
+  - **Code and scripts**: If you have any code or scripts that call v1 of the API, or use devtool functionality that is removed from v2 such as DHCP object or entries, **you must take action before 1 Nov 2025**. Update your code and scripts so they point to v2 of the API. [Follow the examples provided for tools such as Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) to rewrite your devtool templates so they do not refer to removed functionalities. Do this in synchronization with moving your gateway to IPAM mode (if necessary).
 
   - **Console-only**: You do not need to take any action, except ensuring that your gateway is in IPAM mode.
 
@@ -174,11 +174,11 @@ We will detach your Public Gateway from all attached Private Networks, and reatt
 
 If you only manage your gateway via the Scaleway console, you do not need to take any action once your gateway is in IPAM mode.
 
-If you have any code or scripts that call v1 of the Scaleway Public Gateways API, you must update these to point towards [v2](https://www.scaleway.com/en/developers/api/public-gateway/) before 1 Oct 2025.
+If you have any code or scripts that call v1 of the Scaleway Public Gateways API, you must update these to point towards [v2](https://www.scaleway.com/en/developers/api/public-gateway/) before 1 Nov 2025.
 
 ### What if I want to keep using my custom gateway DHCP configuration from v1 of the API?
 
-After version 1 of the Public Gateways API is removed on 1 Oct 2025, these functionalities will no longer be available.
+After version 1 of the Public Gateways API is removed on 1 Nov 2025, these functionalities will no longer be available.
 
 Going forward, we expect users who were previously using custom DHCP with a Public Gateway to move to the standard set-up of IPAM and Private Networks' inbuilt DHCP for private IP assignment. Remember that you can define a [custom CIDR block](/vpc/how-to/create-private-network/#how-to-configure-cidr) for a Private Network at the time of creation, and use [reserved IP addresses](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address) with IPAM when attaching both standard and custom resources.
 
@@ -199,11 +199,11 @@ Refer to our [Terraform migration guide](https://github.com/scaleway/terraform-p
 
 ### Can't I just wait for Scaleway to force the move to IPAM mode?
 
-After 1 Oct 2025 we will carry out a forced action which will move all existing legacy Public Gateways to IPAM mode, and we will remove v1 of the Public Gateways API.
+After 1 Nov 2025 we will carry out a forced action which will move all existing legacy Public Gateways to IPAM mode, and we will remove v1 of the Public Gateways API.
 
 We highly recommend that you move to IPAM mode **before** this date, so that you can plan a smooth and synchronized transition at a time that suits you. 
 
-If you still have code or scripts pointing to v1 of the API after the 1 Oct 2025, these will cease to function.
+If you still have code or scripts pointing to v1 of the API after the 1 Nov 2025, these will cease to function.
 
 ## Further help and support
 
diff --git a/pages/public-gateways/troubleshooting/index.mdx b/pages/public-gateways/troubleshooting/index.mdx
@@ -3,7 +3,7 @@ title: Public Gateways
 description: Find troubleshooting resources for resolving issues with Scaleway Public Gateways.
 dates:
   posted: 2025-03-14
-  validation: 2025-03-14
+  validation: 2025-09-22
 productIcon: PublicGatewayProductIcon
 ---
 
diff --git a/pages/vpc/reference-content/getting-most-private-networks.mdx b/pages/vpc/reference-content/getting-most-private-networks.mdx
@@ -3,7 +3,7 @@ title: Getting the most from Private Networks
 description: Optimize your Scaleway VPCs, Private Networks and resource connectivity with this guide which details tips and best practices.
 tags: vpc private-network connectivity best-practice
 dates:
-  validation: 2025-09-11
+  validation: 2025-09-22
   posted: 2024-08-28
 ---
 import image from './assets/scaleway-vpc-schema.webp'
@@ -97,7 +97,9 @@ You can also disable public connectivity on the Load Balancer itself. This may b
 
 ## Connecting a VPC to external infrastructure
 
-Watch this space for Scaleway's upcoming solution to provide private, secure connectivity between resources in a Scaleway VPC and your external or on-premises architecture. In the meantime, you may consider installing a manual VPN on a Scaleway Instance to connect to other non-Scaleway infrastructure, and create a [custom route](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) towards this VPN so traffic on your Private Network can securely communicate with resources at the other end of your VPN tunnel.
+You can provision a [Scaleway Interlink](/interlink) for private, secure, physical connectivity between resources in a Scaleway VPC and your external or on-premises architecture. Alternatively [Site-to-Site VPN](/site-to-site-vpn) (currently in Private Beta) provides a solution to connect your VPC to external infraustrcture via an encrypted tunnel. 
+
+If you wish to install a manual VPN on a Scaleway Instance to connect to other non-Scaleway infrastructure, you can install the VPN of your vhoice and create a [custom route](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) towards this VPN, so traffic on your Private Network can securely communicate with resources at the other end of your VPN tunnel.
 
 ## Resource-specific information
 
diff --git a/pages/vpc/troubleshooting/index.mdx b/pages/vpc/troubleshooting/index.mdx
@@ -3,7 +3,7 @@ title: VPC
 description: Find troubleshooting resources for resolving issues with Scaleway Virtual Private Cloud and Private Networks.
 dates:
   posted: 2025-03-14
-  validation: 2025-03-14
+  validation: 2025-09-22
 productIcon: VpcProductIcon
 ---
 
