fix(pgw): fix deprecation doc

Author: RoRoJ

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

@@ -15,6 +15,7 @@ categories:
 
 TODO CHECK CONSOLE MENTIONS
 TODO CHECK DATES
+TODO ADD TERRAFORM SNIPPETS
 
 Scaleway's VPC offering is evolving, and with this comes changes for the Public Gateway product.
 
@@ -30,7 +31,6 @@ 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 (API only) | Yes ✅ | No ❌|
 | Supports SSH bastion allowed IPs, and future new features | No ❌| Yes ✅ |
 | Deprecated? | Yes ✅ | No ❌|
 | Removal date | 1 Oct 2025 | --- |
@@ -91,15 +91,11 @@ If you still have a legacy gateway, you must transition it to IPAM mode so that
 
 ### Removal of the DHCP object
 
-For some time now, this functionality has been available via the API and developer tools only (not the Scaleway console).
-
-The [DHCP object](https://www.scaleway.com/en/developers/api/public-gateway/#path-dhcp-list-dhcp-configurations) has allowed users to define a DHCP configuration, which specified how the gateway should assign IP addresses to devices on attached Private Networks (parameters including the subnet of the DHCP server, entry validity period and more). 
-
-When attaching a Public Gateway to a Private Network (creating a [Gateway Network](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateway-networks-attach-a-public-gateway-to-a-private-network)) via the API, you can pass a DHCP object, or the ID of an existing DHCP object. 
+The DHCP object has remained present in v1 of the API, despite the [migration of DHCP to Private Networks](/vpc/reference-content/vpc-migration/), which replaced DHCP on Public Gateways.
 
-**The DHCP object does not exist in v2 of the API**. After v1 is removed, it will no longer be possible to create or attach DHCP objects to Gateway Networks. Instead, IPAM configuration, where auto-configuration of `GatewayNetwork` is managed by IPAM, will become default, and replace any need for DHCP configuration via the Public Gateway.
+**The DHCP object does not exist in v2 of the API**. Instead, IPAM configuration, where auto-configuration of `GatewayNetwork` is managed by IPAM and DHCP is managed by Private Networks, replaces any need for DHCP configuration via the Public Gateway.
 
-When you move your gateway to IPAM mode, any existing custom DHCP objects will become defunct. Going forward, we expect users who were previously using a custom DHCP object 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.
+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.
 
 ### Removal of the address field