fix(review): review doc (#5386)

Author: RoRoJ

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

@@ -4,7 +4,7 @@ description: Find out what to expect from Public Gateways v2, and get ready for
 tags: public-gateways dhcp dhcp-entries api v2 ipam-mode legacy
 dates:
   creation: 2025-01-23
-  validation: 2025-01-23
+  validation: 2025-08-07
 ---
 import image from './assets/scaleway-pgw-listing.webp'
 

pages/vpc/how-to/activate-dhcp.mdx

@@ -3,7 +3,7 @@ title: How to activate DHCP on a legacy Private Network
 description: Learn how to activate DHCP for your Scaleway VPC with this step-by-step guide. Ensure seamless IP address management and efficient network configuration.
 tags: regional-private-network private-network vpc virtual-private-cloud dhcp activate old migrate migration
 dates:
-  validation: 2025-01-28
+  validation: 2025-08-07
   posted: 2023-07-06
 ---
 import Requirements from '@macros/iam/requirements.mdx'

pages/vpc/troubleshooting/autoconfig-not-working.mdx

@@ -3,7 +3,7 @@ title: My legacy Instance is attached to a Private Network but auto-configuratio
 description: Troubleshoot VPC autoconfiguration issues with this guide. Find solutions to common problems and ensure smooth network setup on Scaleway.
 tags: resource instance private-network auto-configuration auto configuration dhcp default-route
 dates:
-  validation: 2025-01-28
+  validation: 2025-08-07
   posted: 2023-07-05
 ---
 

pages/vpc/troubleshooting/resource-attached-no-ip.mdx

@@ -3,7 +3,7 @@ title: My resource is attached to a Private Network but has no IP address on the
 description: This page helps you troubleshoot problems when you have a resource attached to a Private Network, but it has no reserved or configured IP private IP address on the network
 tags: resource instance private-network vpc ipv4 ipv6 ip-address IPAM reserved configured old nics
 dates:
-  validation: 2025-01-28
+  validation: 2025-08-07
   posted: 2023-07-05
 ---
 import image from './assets/scaleway-attached-resources.webp'
@@ -42,7 +42,7 @@ To fix this problem, **detach your resource from the Private Network, and reatta
 
 Note that some manual configuration of the network interface is required for Elastic Metal servers. Follow the steps in our [dedicated documentation](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks).
 
-You can also attach custom resources, such as virtual machines hosted on your Elastic Metal server, to Private Networks, by specifying their MAC addresses upon attachment/ Follow the instructions for attaching such a resource in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn/).
+You can also attach custom resources, such as virtual machines hosted on your Elastic Metal server, to Private Networks, by specifying their MAC addresses upon attachment. Follow the instructions for attaching such a resource in the [Private Networks documentation](/vpc/how-to/attach-resources-to-pn/).
 
 ### ArchLinux and Debian Bullseye