fix(pgw): fix dates

Author: RoRoJ

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

@@ -13,9 +13,6 @@ categories:
   - network
 ---
 
-TODO CHECK CONSOLE MENTIONS
-TODO CHECK DATES
-
 Scaleway's VPC offering is evolving, and with this comes changes for the Public Gateway product.
 
 This document explains what to expect and how to prepare for the upcoming changes.
@@ -123,24 +120,22 @@ For some time now, this functionality has been available via the API and develop
 
 For custom resources, such as VMs hosted on Elastic Metal servers, we now provide [dedicated functionality](https://www.scaleway.com/en/docs/vpc/how-to/attach-resources-to-pn/) for attaching these to Private Networks. When choosing the **Custom Resource** type, you can specify a MAC address and hostname at the moment of attachment.
 
-We will automatically migrate any existing DHCP entries to IPAM for you, at the moment you put a legacy Public Gateway into IPAM mode. TODO STUFF ABOUT LATER ON DETACH/REATTACH
+We will automatically migrate any existing DHCP entries to IPAM for you, at the moment you put a legacy Public Gateway into IPAM mode.
 
 ### SSH bastion allowed IPs
 
 Allowed IPs is a new functionality of the Public Gateways API v2, that will also be available to all IPAM-mode Public Gateways via the Scaleway console. This feature allows you to specify a list of IP address ranges which should be allowed to connect to the gateway's SSH bastion and the resources behind it. All other IP addresses will be blocked from connecting. Find out more in the [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) documentation.
 
 ## Timeline and action to take
 
-TODO CHECK DATES
-
-- **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.
+- **March 2025 - V2 release**: The Public Gateway v2 API is released, co-existing with v1. 
+- **8 April 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>
 
-- **7 March 2025 2025 - 1 Oct 2025: Migration period**: You have a six month migration period to complete the following actions
+- **8 March 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, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/#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).