GITBOOK-8909: AL - Merged - Snyk Container - update screenshots

Author: aluca3

docs/.gitbook/assets/aggregate_list_vuln_Kubernetes_workload.png

@@ -61,7 +61,7 @@ Follow these steps to add images from the GitHub container registry to Snyk.
 
 GitHub container registry imports are designated with a unique icon. You can filter the integration in the **Projects** view to see GitHub container registry Projects only.
 
-<figure><img src="../../../.gitbook/assets/projects_github_container_registry.png" alt=""><figcaption><p>Example of a GitHub Project </p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/container_registry_integrations_github.png" alt=""><figcaption><p>Example of a GitHub Project</p></figcaption></figure>
 
 {% hint style="info" %}
 For application vulnerabilities within container images, any changes to the application will not be reflected with a manual or recurring retest. A re-import of the image is required. For more information, see [Detecting application vulnerabilities in container images](../use-snyk-container/detect-application-vulnerabilities-in-container-images.md).

docs/.gitbook/assets/container_registry_integrations_github.png

@@ -13,18 +13,18 @@ This page explains how to set up GitLab Container Registry integration in Snyk a
 ### **Prerequisites for GitLab Container Registry integration**
 
 * You must be an administrator for the Organization you are configuring in Snyk.
-* Snyk needs a [personal access token](https://docs.gitlab.com/ee/user/profile/personal\_access\_tokens.html) to integrate with GitLab Container Registry. Snyk does not support integration when GitLab SSO is in use for access to the GitLab Container Registry.
+* Snyk needs a [personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) to integrate with GitLab Container Registry. Snyk does not support integration when GitLab SSO is in use for access to the GitLab Container Registry.
 
 ## **Configure GitLab Container Registry integration**
 
 1. In your Snyk account, navigate to **Integrations**. Under the Container Registries section, find the GitLab Container Registry option and click it.
-2. In the **Account credentials** section, enter your GitLab Container Registry username and [personal access token](https://docs.gitlab.com/ee/user/profile/personal\_access\_tokens.html).
+2. In the **Account credentials** section, enter your GitLab Container Registry username and [personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html).
 3. In the **Container registry name** fill in the full URL to the registry you want to integrate with.
 4. To finish, click **Save**.
 
 If you are using a self-hosted GitLab Container Registry, [contact Snyk Support](https://support.snyk.io/) to provide you with a token. For more information, see [Snyk Container for self-hosted container registries (with Broker)](../../../enterprise-setup/snyk-broker/snyk-broker-container-registry-agent/integrate-with-self-hosted-container-registries-broker.md).
 
-Snyk tests the connection values, and the page reloads, now displaying GitLab Container Registry integration information. The **Add your GitLab container registry images to Snyk** button becomes available. 
+Snyk tests the connection values, and the page reloads, now displaying GitLab Container Registry integration information. The **Add your GitLab container registry images to Snyk** button becomes available.
 
 If the connection to GitLab Container Registry fails, a notification appears under the **Connected to GitLab container registry** section.
 
@@ -60,7 +60,7 @@ The steps follow for adding images from GitLab Container Registry to Snyk.
 
 GitLab Container Registry imports are designated with a unique icon. You can filter the integration in the **Projects** view to see GitLab Container Registry Projects only.
 
-<figure><img src="../../../.gitbook/assets/mceclip0-14-.png" alt=""><figcaption><p>Example of a GitLab Container Registry Project</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/container_registry_integrations_gitlab.png" alt=""><figcaption><p>Example of a GitLab Project</p></figcaption></figure>
 
 {% hint style="info" %}
 For application vulnerabilities within container images, any changes to the application will not be reflected with a manual or recurring retest. A re-import of the image is required. For more information, see [Detecting application vulnerabilities in container images](../use-snyk-container/detect-application-vulnerabilities-in-container-images.md).

docs/.gitbook/assets/container_registry_integrations_gitlab.png

@@ -61,7 +61,7 @@ Follow these steps to add images from Nexus to Snyk.
 
 Nexus imports are indicated with a unique icon. You can also filter to view only Nexus Projects.
 
-<figure><img src="../../../.gitbook/assets/mceclip0-18-.png" alt="Nexus Project in Projets listing"><figcaption><p>Nexus Project in Projects listing</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/container_registry_integrations_nexus.png" alt="Nexus Project in Projets listing"><figcaption><p>Example of a Nexus Project</p></figcaption></figure>
 
 {% hint style="info" %}
 For application vulnerabilities within container images, any changes to the application will not be reflected with a manual or recurring retest. A re-import of the image is required. For more information, see [Detecting application vulnerabilities in container images](../use-snyk-container/detect-application-vulnerabilities-in-container-images.md).

docs/.gitbook/assets/container_registry_integrations_nexus.png

@@ -13,13 +13,13 @@ Expand any Project to view:
 
 To view vulnerabilities in detail for any image, including its history, click the image name. The Project details page loads for the selected image:
 
-![Project details for a selected image](../../../../.gitbook/assets/project\_details\_for\_container\_image.png)
+![Project details for a selected image](../../../../.gitbook/assets/project_details_for_container_image.png)
 
 To view an aggregate list of the vulnerabilities in all of the images in the workload, including details about the security posture of the workload configuration, click the workload.
 
 The Project details page loads for the selected image.
 
-![Aggregated list of vulnerabilities in images in Kubernetes workload](../../../../.gitbook/assets/uuid-79e06589-b59c-4bad-30e4-56c0e15607e0-en.png)
+![Aggregated list of vulnerabilities in images in Kubernetes workload](../../../../.gitbook/assets/aggregate_list_vuln_Kubernetes_workload.png)
 
 Snyk scans the workload configuration for the following properties: