diff --git a/pages/edge-services/assets/scaleway-create-pipeline-lb.webp b/pages/edge-services/assets/scaleway-edge-create-pipeline-lb.webp
similarity index 100%
rename from pages/edge-services/assets/scaleway-create-pipeline-lb.webp
rename to pages/edge-services/assets/scaleway-edge-create-pipeline-lb.webp
diff --git a/pages/edge-services/how-to/configure-cache.mdx b/pages/edge-services/how-to/configure-cache.mdx
index 6173967f7d..93029f2df0 100644
--- a/pages/edge-services/how-to/configure-cache.mdx
+++ b/pages/edge-services/how-to/configure-cache.mdx
@@ -27,7 +27,7 @@ You can disable and enable caching at will, as well as control the lifetime of a
1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline on which you want to enable caching:
-
+
2. In the **Cache** panel, use the icon to enable the cache.
@@ -49,7 +49,7 @@ Purging objects clears all objects from your cache. Afterward, Edge Services wil
1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge:
-
+
2. In the **Purge cache** panel, click **Purge all**.
@@ -65,7 +65,7 @@ This allows you to specify the precise objects that you want to clear from the c
1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge:
-
+
2. In the **Purge cache** panel, click **Purge by object**.
@@ -108,7 +108,7 @@ For Object Storage bucket origins, the following example call to the S3 API upda
1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to disable:
-
+
2. In the **Cache** panel, use the icon to disable the cache.
diff --git a/pages/edge-services/how-to/configure-custom-domain.mdx b/pages/edge-services/how-to/configure-custom-domain.mdx
index 3ec16421e5..0a2727795f 100644
--- a/pages/edge-services/how-to/configure-custom-domain.mdx
+++ b/pages/edge-services/how-to/configure-custom-domain.mdx
@@ -25,7 +25,7 @@ The procedure for adding a customized endpoint is as follows:
1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline whose domain you want to customize:
-
+
2. In the **Endpoint** panel, click **Configure domain**. The following screen displays:
@@ -97,7 +97,7 @@ After customizing your domain, you can edit it (or its certificate) at any time
1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to customize:
-
+
2. In the **Endpoint** panel, click **Edit**. The **Edit Domain** screen displays.
@@ -113,7 +113,7 @@ Even though the original Edge Services endpoint (e.g. `https://pipeline-id.svc.e
1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to reset:
-
+
2. In the **Endpoint** panel, click **Reset**.
diff --git a/pages/edge-services/how-to/create-pipeline-lb.mdx b/pages/edge-services/how-to/create-pipeline-lb.mdx
index be7851d12b..63a2534534 100644
--- a/pages/edge-services/how-to/create-pipeline-lb.mdx
+++ b/pages/edge-services/how-to/create-pipeline-lb.mdx
@@ -34,7 +34,7 @@ You can create an Edge Services pipeline from the Load Balancer section of the c
2. Click **Create pipeline**. The pipeline creation wizard displays.
-
+
3. Configure the [origin](/edge-services/concepts/#origin) for this pipeline:
- Select **Load Balancer** as the origin type.
diff --git a/pages/edge-services/quickstart.mdx b/pages/edge-services/quickstart.mdx
index f885e038c7..5168c2dea6 100644
--- a/pages/edge-services/quickstart.mdx
+++ b/pages/edge-services/quickstart.mdx
@@ -106,7 +106,7 @@ If you already own a domain, you can customize an Edge Services pipeline endpoin
2. In the **Endpoint** panel, click **Configure domain**. The following screen displays:
-
+
3. Set a subdomain from which your Object Storage bucket or Load Balancer origin will be accessible via its Edge Services pipeline. You must already own the primary domain. For example, if you own `beautiful-domain.com`, choose any subdomain you like and enter `my-chosen-subdomain.beautiful-domain.com` into the box.
diff --git a/pages/load-balancer/how-to/add-certificate.mdx b/pages/load-balancer/how-to/add-certificate.mdx
index 7772a40d06..940c33f602 100644
--- a/pages/load-balancer/how-to/add-certificate.mdx
+++ b/pages/load-balancer/how-to/add-certificate.mdx
@@ -190,9 +190,7 @@ If you are using the [import certificate](#how-to-import-a-certificate) option,
## How to manage your certificates
-View the certificate(s) that you have uploaded for your Load Balancer on the **SSL certificates** tab:
-
-
+View the certificate(s) that you have uploaded for your Load Balancer on the **SSL certificates** tab.
Use the button to delete unwanted certificates.
diff --git a/pages/messaging/how-to/create-manage-subscriptions.mdx b/pages/messaging/how-to/create-manage-subscriptions.mdx
index b8e05a5e43..ceb665f831 100644
--- a/pages/messaging/how-to/create-manage-subscriptions.mdx
+++ b/pages/messaging/how-to/create-manage-subscriptions.mdx
@@ -82,9 +82,11 @@ An HTTP or HTTPS subscription will have a `Pending` status until you **confirm**
1. Access the subscriptions listing page (from the console side menu, **Serverless** > **Topics and Events** > **Topics**, click the topic containing the subscription).
-2. Click the icon next to the subscription you wish to confirm, then select **Confirm subscription** from the menu. A pop-up displays:
+2. Click the icon next to the subscription you wish to confirm, then select **Confirm subscription** from the menu. A pop-up displays, with the following message:
-
+ ```
+ A subscription confirmation message has been sent to the subscription endpoint. Retrieve the SubscribeURL value from the message and enter it in the box below. This is a necessary step to start receiving messages from the topic.
+ ```
3. Retrieve the confirmation message that Scaleway Topics and Events sent to your endpoint (delivered as an `HTTP POST` request), and extract the `SubscribeURL` from the message payload.
diff --git a/pages/vpc/troubleshooting/assets/scaleway-attached-resources.webp b/pages/vpc/troubleshooting/assets/scaleway-attached-resources.webp
new file mode 100644
index 0000000000..984555e987
Binary files /dev/null and b/pages/vpc/troubleshooting/assets/scaleway-attached-resources.webp differ