fix(pgw): corrections

Author: RoRoJ

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

@@ -114,7 +114,7 @@ TODO
 2. [TODO-DATE] **V2 release**: The Public Gateway v2 API will be released, co-existing with v1. 
 
     <Message type="note">
-    You will be able to list and manage both v1 and v2 Gateways with the **Scaleway console**. However, all new Public Gateways created via the console after [TODO-DATE] will necessarily be v2 gateways.
+    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. However, all new Public Gateways created via the console after [TODO-DATE] will necessarily be v2 gateways.
     </Message>
 
 3. [TODO-DATE - TODO-DATE] **Migration period**: You have a six month migration period to complete the following actions
@@ -124,7 +124,7 @@ TODO
     - Ensure that [DHCP is activated](TODO) on all Private Networks attached to your IPAM-mode Public Gateways.
     - Update any code or scripts you have that call version 1 of the Public Gateways API, so that they call version 2 instead. This includes removing any use of the DHCP entries, DHCP objects or address fields as mentioned [above](link).
 
-    If your Public Gateway is already in IPAM-mode, and you only manage it via the console, you will not be affected by this changes and you do not need to take any action.
+    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.
 
 4. [TODO-DATE] **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.