fix(pgw): correct dates

Author: RoRoJ

pages/public-gateways/reference-content/understanding-v2.mdx

@@ -14,7 +14,7 @@ categories:
 ---
 
 TODO CHECK CONSOLE MENTIONS
-TODO CHECK DATE - NOT JUNE
+TODO CHECK DATES
 
 Scaleway's VPC offering is evolving, and with this comes changes for the Public Gateway product.
 
@@ -30,15 +30,15 @@ All Scaleway Public Gateways until now have been created and managed with the ve
 |---|---|---|
 | Supports [legacy-mode PGWs](/public-gateways/concepts/#ipam) | Yes ✅ | No ❌|
 | Supports [IPAM-mode PGWs](/public-gateways/concepts/#ipam) | Yes ✅ | Yes ✅|
-| Supports custom DHCP via PGW | Yes ✅ | No ❌|
+| Supports custom DHCP via PGW (API only) | Yes ✅ | No ❌|
 | Supports SSH bastion allowed IPs, and future new features | No ❌| Yes ✅ |
 | Deprecated? | Yes ✅ | No ❌|
-| Removal date | 2 June 2025 | --- |
-| Compatible with PGW management via Scaleway console? | Only until 2 June 2025 | Yes ✅ |
+| Removal date | 1 Oct 2025 | --- |
+| Compatible with PGW management via Scaleway console? | Only until 1 Oct 2025 | Yes ✅ |
 
-After a deprecation period ending on 2 June 2025, the Public Gateways API v1 and associated developer tools will be removed. 
+After a deprecation period ending on 1 Oct 2025, the Public Gateways API v1 and associated developer tools will be removed. 
 
-**What you need to do before 2 June 2025:**
+**What you need to do before 1 Oct 2025:**
 
 - Ensure that your Public Gateway is in [IPAM mode](#ipam-mode-becomes-default). Only IPAM-mode gateways are compatible with v2.
 
@@ -131,14 +131,14 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also
 
 TODO CHECK DATES
 
-- **21 February 2025 - V2 release**: The Public Gateway v2 API is be released, co-existing with v1. 
-- **21 February 2025 - V1 deprecation**: The Public Gateway v1 API is deprecated. Deprecation means that the API will still function, but it is slated for removal and we do not recommended that you keep using it.
+- **7 March 2025 - V2 release**: The Public Gateway v2 API is be released, co-existing with v1. 
+- **7 March 2025 - V1 deprecation**: The Public Gateway v1 API is deprecated. Deprecation means that the API will still function, but it is slated for removal and we do not recommended that you keep using it.
 
     <Message type="note">
     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>
 
-- **21 February 2025 - 2 June 2025: Migration period**: You have a six month migration period to complete the following actions
+- **7 March 2025 2025 - 1 Oct 2025: Migration period**: You have a six month migration period to complete the following actions
 
     - Ensure that your Public Gateway is in [IPAM mode](/network/public-gateways/concepts/#ipam). Only IPAM mode gateways are compatible with v2.
     - Put any non-IPAM mode ([legacy](/network/public-gateways/concepts/#ipam)) Public Gateways in IPAM-mode, by using the **Move to IPAM mode** button in the console, or the [dedicated API call](TODO).
@@ -147,15 +147,15 @@ TODO CHECK DATES
 
     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.
 
-- **2 June 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 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.
 
 ## FAQ
 
 ### How do I know if I have to take action?
 
 - Consider whether you mange 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 2 June 2025**. Update your code and scripts so they point to v2 of the API. [Follow the examples provided for tools such as Terraform](TODO) 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 Oct 2025**. Update your code and scripts so they point to v2 of the API. [Follow the examples provided for tools such as Terraform](TODO) 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.
 
@@ -179,11 +179,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](TODO) before 2 June 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](TODO) before 1 Oct 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 2 June 2025, these functionalities will no longer be available.
+After version 1 of the Public Gateways API is removed on 1 Oct 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.
 
@@ -193,11 +193,11 @@ If you use Terraform to manage your infrastructure as code, ensure that you are
 
 ### Can't I just wait for Scaleway to force the move to IPAM mode?
 
-After the 2 June 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 the 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.
 
 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 2 June 2025, these will cease to function.
+If you still have code or scripts pointing to v1 of the API after the 1 Oct 2025, these will cease to function.
 
 ## Further help and support