fix(pgw): corrections

Author: RoRoJ

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

@@ -17,6 +17,10 @@ Scaleway's VPC offering is evolving, and with this comes changes for the Public
 
 This document explains what to expect and how to prepare for the upcoming changes.
 
+## Summary (TL;DR)
+
+[TODO INSERT BRIEF SUMMARY OF CHANGES AND WHAT USERS MUST DO]
+
 ## Background: DHCP and IPAM
 
 When Scaleway originally introduced Public Gateways, they provided DHCP functionality for resources on attached Private Networks. With the [arrival of Scaleway VPC](/network/vpc/reference-content/vpc-migration/), DHCP was moved from Public Gateways to Private Networks themselves.
@@ -61,7 +65,7 @@ When attaching a Public Gateway to a Private Network (creating a [Gateway Networ
 
 This functionality will be deprecated going forward. 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.
 
-### Deprecation of the `address` field
+### Deprecation of the address field
 
 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 use the `address` field to define a single static IP address to assign to the Public Gateway on that Private Network.
 
@@ -83,7 +87,7 @@ We will release v2 of the Public Gateway API on [TODO-DATE - SAME DATE?]. During
 
 [TODO - INSERT INFORMATION ON HOW TO MIGRATE]
 
-[TODO - WHAT WILL THIS ALL LOOK LIKE IN THE CONSOLE? 
+[TODO - WHAT WILL THIS ALL LOOK LIKE IN THE CONSOLE? ]
 
 [TODO - DO USERS WHO DON'T USE LEGACY  / DHCP OBJECT / DHCP ENTRIES HAVE ANY ACTION TO TAKE?]