fix(pgw): review comments

Author: RoRoJ

pages/public-gateways/faq.mdx

@@ -39,6 +39,24 @@ Read our [dedicated documentation](/public-gateways/reference-content/understand
 
 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?
+
+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:
+
+- 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](/public-gateways/reference-content/understanding-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).
+
+  - **Console-only**: You do not need to take any action, except ensuring that your gateway is in IPAM mode.
+
+- Check in the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) whether your Public Gateway is in IPAM mode or legacy mode:
+
+  - **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use 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).
+
+  - **IPAM mode**: You do not have any action to take, except updating any code and scripts that you have (see above).
+
+See our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) for full details.
+
 ## 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.

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

@@ -71,7 +71,7 @@ Since the assignment and management of IP addresses on Private Networks is now m
 - Removal of DHCP entries
 - New SSH bastion feature: Allowed IPs
 
-Read on to find out more.
+Full details of each change are explained below.
 
 ### IPAM mode becomes default