fix(s2s): last modifs for images

Author: RoRoJ

pages/site-to-site-vpn/reference-content/understanding-s2svpn.mdx

@@ -16,6 +16,13 @@ dates:
   posted: 2025-06-03
 ---
 
+import image1 from './assets/scaleway-s2svpn-conceptual.webp'
+import image2 from './assets/scaleway-vpn-two-tunnels.webp'
+import image3 from './assets/scaleway-vpn-one-tunnel-both.webp'
+import image4 from './assets/scaleway-vpn-one-tunnel-one-type.webp'
+import image5 from './assets/scaleway-vpn-tunnel-detail.webp'
+
+
 <Message type="note">
 Site-to-Site VPN is currently in Private Beta, and available to selected testers only via the Scaleway API. [Request an invitation](https://www.scaleway.com/en/betas/#site-to-site-vpn).
 </Message>
@@ -35,7 +42,7 @@ Scaleway Site-to-Site VPN consists of:
 
 You must create all of the above elements, and correctly configure your customer gateway device, for a functional Site-to-Site VPN.
 
-<Lightbox src="scaleway-s2svpn-conceptual.webp" alt="A diagram shows the four elements described above, connected together" />
+<Lightbox image={image1} alt="A diagram shows the four elements described above, connected together" />
 
 ### VPN gateway
 
@@ -54,11 +61,11 @@ The customer gateway provides a connection point on the customer (remote) side o
 A customer gateway has the following properties, which you can customize when you create the gateway:
 
 - **Region**: The geographical location in which the gateway object is created. It must be in the same region as the other Site-to-Site VPN resources (VPN gateways, routing policies, connections) that you want to use it with.
-- **Name** and (optioanlly) **tags**: A name and tags to identify the gateway.
+- **Name** and (optionally) **tags**: A name and tags to identify the gateway.
 
 The rest of the properties **must** correspond to the real properties of the corresponding real customer gateway device:
 
-- **Public IP address**: The address(s) used to establish the VPN tunnel. Maximum of one IPv4 and one IPv6 address per gateway. Gateways with both types of IP will be able to support dual tunnels for a single connection, one IPv4 and one IPv6, providing increased redundancy.
+- **Public IP address**: The address(es) used to establish the VPN tunnel. Maximum of one IPv4 and one IPv6 address per gateway. Gateways with both types of IP will be able to support dual tunnels for a single connection, one IPv4 and one IPv6, providing increased redundancy.
 - **Autonomous System Number (ASN)**: The unique identifier assigned to the customer's network, used by BGP (Border Gateway Protocol) to exchange routing information with other networks.
 
 <Message type="note">
@@ -106,13 +113,13 @@ A connection has the following properties, which you can customize when you crea
     Having both types of public IP for both gateways types increases redundancy by providing two tunnels per connection, but it is not this in itself which determines the traffic types which can be routed.
     <br/><br/>
     The following diagram shows a connection with two tunnels, configured to route both types of IP traffic:
-    <Lightbox src="scaleway-vpn-two-tunnels.webp" alt="A diagram shows a VPN gateway and a customer gateway, with two tunnels between them. One is via the gateways' public IPv4 addresses, the other via their public IPv6 addresses. Both IPv4 and IPv6 traffic flow through both tunnels."/>
+    <Lightbox image={image2} alt="A diagram shows a VPN gateway and a customer gateway, with two tunnels between them. One is via the gateways' public IPv4 addresses, the other via their public IPv6 addresses. Both IPv4 and IPv6 traffic flow through both tunnels."/>
 
     The following diagram shows a connection with only one tunnel (established via the gateways' public IPv4 addresses), configured to route both types of IP traffic:
-    <Lightbox src="scaleway-vpn-one-tunnel-both.webp" alt="A diagram shows a VPN gateway and a customer gateway, with one tunnel between them, established via their public IPv4 addresses. Both IPv4 and IPv6 traffic flow through the tunnel."/>
+    <Lightbox image={image3} alt="A diagram shows a VPN gateway and a customer gateway, with one tunnel between them, established via their public IPv4 addresses. Both IPv4 and IPv6 traffic flow through the tunnel."/>
 
     The following diagram shows a connection with only one tunnel (established via the gateways' public IPv6 addresses), which has been configured to only route IPv4 traffic:
-    <Lightbox src="scaleway-vpn-one-tunnel-one-type.webp" alt="A diagram shows a VPN gateway and a customer gateway, with one tunnel between them, established via their public IPv6 addresses. IPv4 traffic flows through the tunnel."/>
+    <Lightbox image={image4} alt="A diagram shows a VPN gateway and a customer gateway, with one tunnel between them, established via their public IPv6 addresses. IPv4 traffic flows through the tunnel."/>
     </Message>
 
 - **Connection initiation policy**: Which gateway should initiate the tunnel(s). This can be either the VPN gateway, or the customer gateway. The chosen gateway will be responsible for kicking off the secure exchange that sets up the IPsec tunnel(s).
@@ -137,7 +144,7 @@ You also need to set up route announcements and filters on the customer side. Fo
 
 - **BGP interconnection subnet(s)**: The private subnet used to provide private IP addresses for the VPN gateway and customer gateway over the tunnel(s). The gateways connect over this private subnet to establish a BGP session and exchange routing information. For connections that are configured to route both IPv4 and IPv6 traffic, one IPv4 and one IPv6 subnet will be provided. Subnet information can be accessed via the API.
 
-    <Lightbox src="scaleway-vpn-tunnel-detail.webp" alt="A diagram shows a VPN gateway and a customer gateway, with one tunnel between them, established via their public IPv4 addresses. IPv4 and IPv6 traffic is routed through the tunnel. Two BGP sessions are established within the tunnel between the two gateways over private subnets: one IPv4 and one IPv6, whereby they exchange route announcements for each traffic type."/>
+    <Lightbox image={image5} alt="A diagram shows a VPN gateway and a customer gateway, with one tunnel between them, established via their public IPv4 addresses. IPv4 and IPv6 traffic is routed through the tunnel. Two BGP sessions are established within the tunnel between the two gateways over private subnets: one IPv4 and one IPv6, whereby they exchange route announcements for each traffic type."/>
 
 - **Routing policy**: Take into account the routing policy(ies) you attached to the connection, when configuring routing policy on the customer gateway device.