diff --git a/docs/.gitbook/assets/configure_integration_Amazon_ecr.png b/docs/.gitbook/assets/configure_integration_Amazon_ecr.png
new file mode 100644
index 000000000000..b4f2f9795d33
Binary files /dev/null and b/docs/.gitbook/assets/configure_integration_Amazon_ecr.png differ
diff --git a/docs/.gitbook/assets/confirmation_message_connected_docker_hub.png b/docs/.gitbook/assets/confirmation_message_connected_docker_hub.png
new file mode 100644
index 000000000000..7aff6dcb5132
Binary files /dev/null and b/docs/.gitbook/assets/confirmation_message_connected_docker_hub.png differ
diff --git a/docs/.gitbook/assets/project_page_security_information.png b/docs/.gitbook/assets/project_page_security_information.png
new file mode 100644
index 000000000000..e16740be4b29
Binary files /dev/null and b/docs/.gitbook/assets/project_page_security_information.png differ
diff --git a/docs/.gitbook/assets/projects_filter_integrations_ecr.png b/docs/.gitbook/assets/projects_filter_integrations_ecr.png
new file mode 100644
index 000000000000..6c559bdb5353
Binary files /dev/null and b/docs/.gitbook/assets/projects_filter_integrations_ecr.png differ
diff --git a/docs/.gitbook/assets/projects_github_container_registry.png b/docs/.gitbook/assets/projects_github_container_registry.png
new file mode 100644
index 000000000000..9fc9da1a495b
Binary files /dev/null and b/docs/.gitbook/assets/projects_github_container_registry.png differ
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-add-images-to-snyk.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-add-images-to-snyk.md
index 1dd9c324c006..447b20e8b2df 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-add-images-to-snyk.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-add-images-to-snyk.md
@@ -23,11 +23,11 @@ Log in to your account and navigate to the relevant Group and Organization you w
 5. When the import ends, a notification of success or failure appears at the top of the page. Click **Refresh Page** to view the **Projects** page with the newly imported images.\
    Images are grouped by repository and linked individually to a detailed **Projects** page.
 6. You can now connect your Git repo to this Project to use your Dockerfile for enriched fix advice.\
-   For more information, see [Detect vulnerable base images from your Dockerfile](../../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+   For more information, see [Detect vulnerable base images from your Dockerfile](../../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
 You can filter to view only ECR Projects, which are marked with a unique icon.
 
-<figure><img src="../../../../.gitbook/assets/List_of_ECR_Projects (4).png" alt="ECR Project" width="375"><figcaption><p>ECR Project</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/projects_filter_integrations_ecr.png" alt="" width="284"><figcaption><p>Filtering by ECR Project</p></figcaption></figure>
 
 Amazon ECR integration works like other Snyk integration. To continue to monitor, fix, and manage your Projects, see the relevant pages in the Snyk user documentation.
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-configure-your-integration-with-snyk.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-configure-your-integration-with-snyk.md
index 60a8417e11dc..b9e4e1b9bb77 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-configure-your-integration-with-snyk.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/amazon-elastic-container-registry-ecr-configure-your-integration-with-snyk.md
@@ -20,6 +20,6 @@ An example follows:
 
 Snyk tests the connection values, and the page reloads, now displaying Amazon ECR integration details as you entered them. A confirmation message that the details were saved also appears in green at the top of the screen.
 
-<figure><img src="../../../../.gitbook/assets/uuid-49671392-b5d5-389d-66c8-86b3daf9a2e1-en.png" alt="ECR integration was updated"><figcaption><p>ECR integration was updated</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/uuid-49671392-b5d5-389d-66c8-86b3daf9a2e1-en.png" alt="Confirmation message"><figcaption><p>Confirmation message that ECR integration was updated</p></figcaption></figure>
 
 If the connection to AWS fails, a notification appears under the **Connected to Amazon ECR** section.
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/configure-integration-for-amazon-elastic-container-registry-ecr.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/configure-integration-for-amazon-elastic-container-registry-ecr.md
index 63f41a58109e..fab02fe28566 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/configure-integration-for-amazon-elastic-container-registry-ecr.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/configure-integration-for-amazon-elastic-container-registry-ecr.md
@@ -10,7 +10,7 @@ This page explains how to enable integration between one Amazon ECR registry and
 
 You can establish cross-account access to enable Snyk's Amazon ECR integration as a one-click deployment using an [AWS Quick Start](https://github.com/aws-quickstart/quickstart-snyk-security), This eliminates the need for manual configuration.
 
-<figure><img src="../../../../.gitbook/assets/quickstart-snyk-security-ecr (1) (1).png" alt="AWS ECR and Snyk integration cross-account IAM role"><figcaption><p>AWS ECR and Snyk integration cross-account IAM role</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/configure_integration_Amazon_ecr.png" alt=""><figcaption><p>AWS ECR and Snyk integration cross-account IAM role</p></figcaption></figure>
 
 You must have your Snyk **Organization ID** and AWS IAM [role ARN](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference\_identifiers.html#identifiers-arns) to complete the integration. The role ARN is provided in the AWS CloudFormation Console's Output tab.
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/enable-snyk-permissions-to-access-amazon-elastic-container-registry-ecr-for-the-first-time.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/enable-snyk-permissions-to-access-amazon-elastic-container-registry-ecr-for-the-first-time.md
index 8be95918a38c..321c76bbd5e5 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/enable-snyk-permissions-to-access-amazon-elastic-container-registry-ecr-for-the-first-time.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-amazon-elastic-container-registry-ecr/enable-snyk-permissions-to-access-amazon-elastic-container-registry-ecr-for-the-first-time.md
@@ -29,4 +29,4 @@ This process explains how to set up a resource role in AWS and the necessary pol
    2. Click **Edit trust relationship**.
    3. In the **Policy Document**, select and delete the entire script and then copy and paste the following script as it is displayed from the UI in your Snyk account, in the Harden usability scope field of the Account credentials.
 
-![](../../../../.gitbook/assets/uuid-4b683f44-0a5e-0d13-f369-f7edecf98ce9-en.gif)
+<figure><img src="../../../../.gitbook/assets/uuid-4b683f44-0a5e-0d13-f369-f7edecf98ce9-en.gif" alt="Steps to enable permissions to access Amazon Elastic Container Registry"><figcaption><p>Enabling Snyk permissions to access Amazon Elastic Container Registry (ECR)</p></figcaption></figure>
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-digitalocean.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-digitalocean.md
index 326017a7c750..d02902d88d05 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-digitalocean.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-digitalocean.md
@@ -21,7 +21,7 @@ This page explains how to set up DigitalOcean integration in Snyk and start mana
 2. In the **Account credentials** section, enter your DigitalOcean personal access token as the login credential. You can find detailed instructions for creating the access token on the integration page.
 3. To finish, click **Save**.
 
-<figure><img src="../../../.gitbook/assets/mceclip0-10-.png" alt="DigitalOcean account credentials"><figcaption><p>DigitalOcean account credentials</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/mceclip0-10-.png" alt="Account credentials for DigitalOcean"><figcaption><p>DigitalOcean account credentials</p></figcaption></figure>
 
 If you are using self-hosted DigitalOcean, contact [Snyk Support](https://support.snyk.io/hc/en-us/requests/new) 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).
 
@@ -58,12 +58,12 @@ The steps follow to add images from DigitalOcean to Snyk.
 6. When the import ends:
    1. You can view the newly imported image, marked with a **NEW** tag, on the **Projects** page. Images are grouped by repository and are each linked individually to a detailed **Project** page.
    2. An **import log** becomes available; you can reach it at the top of the Projects list.
-   3. To enrich the data and get recommendations regarding your base image, under **Settings**, you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+   3. To enrich the data and get recommendations regarding your base image, under **Settings**, you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
 DigitalOcean imports are indicated with a unique icon. You can filter the integration in the **Projects** view to see DigitalOcean Projects only:
 
-<figure><img src="../../../.gitbook/assets/mceclip0-11-.png" alt="DigitalOcean Projects in Projects listing"><figcaption><p>DigitalOcean Projects in Projects listing</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/mceclip0-11-.png" alt="Example of DigitalOcean Projects"><figcaption><p>DigitalOcean Projects in Projects listing</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).
+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).
 {% endhint %}
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-desktop-extension.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-desktop-extension.md
index 454da88d3b3f..96528d43db97 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-desktop-extension.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-desktop-extension.md
@@ -9,7 +9,7 @@ To install and run the Snyk Docker Desktop Extension:
 1.  On the Docker Desktop home screen, click the three dots next to **Extensions**, and select **Marketplace**.\
 
 
-    <figure><img src="../../../.gitbook/assets/Docker_Desktop_Marketplace.png" alt="Marketplace on Docker Desktop"><figcaption><p>Marketplace on Docker Desktop</p></figcaption></figure>
+    <figure><img src="../../../.gitbook/assets/Docker_Desktop_Marketplace.png" alt=""><figcaption><p>Marketplace on Docker Desktop</p></figcaption></figure>
 2.  In the **Marketplace** window, navigate to the Snyk Extension and click **Install**.\
 
 
@@ -19,11 +19,11 @@ To install and run the Snyk Docker Desktop Extension:
 
 3.  After installation, launch the Snyk Extension and click **Settings**.
 
-    <figure><img src="../../../.gitbook/assets/Snyk_Ext_page_Docker_Deskop.png" alt=""><figcaption><p>Snyk Extension page on Docker Desktop</p></figcaption></figure>
+    <figure><img src="../../../.gitbook/assets/Snyk_Ext_page_Docker_Deskop.png" alt="Settings button on Docker Desktop"><figcaption><p>Snyk Extension page on Docker Desktop</p></figcaption></figure>
 4.  In the **Settings** window, add your API token or service account token and click **Save**.\
 
 
-    <figure><img src="../../../.gitbook/assets/Add_token_Docker_Desktop.png" alt="Add authorization token in the Settings window"><figcaption><p>Add authorization token in the Settings window</p></figcaption></figure>
+    <figure><img src="../../../.gitbook/assets/Add_token_Docker_Desktop.png" alt="Save button on the Docker Desktop settings page"><figcaption><p>Add authorization token in the Settings window</p></figcaption></figure>
 
 You can now select the local image you want to scan with Snyk by clicking **Test image**.
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/configure-the-integration-with-docker-hub.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/configure-the-integration-with-docker-hub.md
index 8aab28d1e398..5a2677277672 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/configure-the-integration-with-docker-hub.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/configure-the-integration-with-docker-hub.md
@@ -8,14 +8,14 @@ This page explains how to enable and configure the integration between Docker Hu
 2. Click **Docker Hub**.
 3. Enter your Docker Hub username and Access Token. For details, see [Generate Docker Hub Access Token](configure-the-integration-with-docker-hub.md#generate-docker-hub-access-token).
 4. Click **Save**.\
-   The page reloads with new options. The Access Token field is blank.\
+   The page reloads with new options. The **Access Token** field is blank.\
    A confirmation message that the details were saved also appears in green at the top of the screen.
 
-<figure><img src="../../../../.gitbook/assets/Screen Shot 2022-01-21 at 9.48.27 AM.png" alt="Successful connection with Docker Hub"><figcaption><p>Successful connection with Docker Hub</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/confirmation_message_connected_docker_hub.png" alt=""><figcaption><p>Confirmation message for successful connection to Docker Hub</p></figcaption></figure>
 
 If the connection to Docker Hub fails, an error notification appears:
 
-<figure><img src="../../../../.gitbook/assets/Screen Shot 2022-01-21 at 9.48.50 AM.png" alt="Failed connection, Could not connect to Docker Hub"><figcaption><p>Failed connection, Could not connect to Docker Hub</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/Screen Shot 2022-01-21 at 9.48.50 AM.png" alt=""><figcaption><p>Error notification that the connection to Docker Hub has failed</p></figcaption></figure>
 
 ## Troubleshooting with the Docker Hub integration
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/docker-hub-add-projects-and-images-to-the-snyk-ui.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/docker-hub-add-projects-and-images-to-the-snyk-ui.md
index a53dfde77db6..63400b3c5d17 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/docker-hub-add-projects-and-images-to-the-snyk-ui.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-docker-hub/docker-hub-add-projects-and-images-to-the-snyk-ui.md
@@ -11,23 +11,21 @@ Snyk tests and monitors Docker Hub repositories and images by evaluating root fo
 
 1. Log in to your Snyk account and navigate to the relevant Group and Organization you want to manage.
 2. Navigate to the **Projects** page and click **Add Projects**.\
-   The list of integrations that are already configured on your account opens.\
-   The view **Which images do you want to test?** opens, displaying all of the available images for the registry to which you connected, grouped by each of your repositories.
-3. Select one or multiple images using any or all of the following methods:
+   The list of integrations that are already configured on your account opens.
+3. The view **Which images do you want to test?** opens, displaying all of the available images for the registry to which you connected, grouped by each of your repositories.
+4. Select one or multiple images using any or all of the following methods:
    * Type the name of a single image for import in the **Image Name** field.
    * Select any of the repositories if you want to import all of the associated images.
    * Expand and collapse repositories to select multiple images.
-4.  Click **Add selected repositories**.
+5.  Click **Add selected repositories**.
 
     On the **Projects** page, a status bar appears at the top of the page as the images are imported; you can continue working in the meantime.
-5. When the import ends, a notification of success or failure appears at the top of the **Projects** page.\
+6. When the import ends, a notification of success or failure appears at the top of the **Projects** page.\
    Click **Refresh** to view the **Projects** page with the newly imported images.\
    Images are grouped by repository and are each linked individually to a detailed **Projects** page.
-6. You can now connect your Git repository to this Project in order to use your Dockerfile for enriched fix advice. For more information, see [Detect vulnerable base images from your Dockerfile](../../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+7. You can now connect your Git repository to this Project in order to use your Dockerfile for enriched fix advice. For more information, see [Detect vulnerable base images from your Dockerfile](../../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
-You can now also filter to view only Docker Hub Projects:
-
-<figure><img src="../../../../.gitbook/assets/uuid-ce306bb8-1d6d-c895-bdb5-3a7cd551977b-en (1) (1) (1) (1) (1) (1) (1) (1) (8) (7).png" alt="Docker Hub projects"><figcaption><p>Docker Hub projects</p></figcaption></figure>
+You can also filter to view only Docker Hub Projects.
 
 When repositories and images are imported, a confirmation appears in green at the top of the screen. Docker Hub files are indicated with a unique icon .
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-github-container-registry.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-github-container-registry.md
index 0bcfc893b86a..fb6ca6709aa6 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-github-container-registry.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-github-container-registry.md
@@ -21,8 +21,6 @@ This page explains how to set up GitHub Container registry integration in Snyk a
 2. Enter your GitHub Container registry username and password login credentials in the Account credentials section.
 3. In the **container registry name** fill in the full URL to the registry you want to integrate with. To finish, click **Save**.
 
-<figure><img src="../../../.gitbook/assets/mceclip1-4-.png" alt="GitHub Container registry Account credentials"><figcaption><p>GitHub Container registry Account credentials</p></figcaption></figure>
-
 If you are using a self-hosted GitHub Container registry, [contact Snyk Support](https://support.snyk.io/hc/en-us/requests/new) 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 GitHub Container registry integration information. The **Add your GitHub container registry images to Snyk** button becomes available.
@@ -59,11 +57,11 @@ Follow these steps to add images from the GitHub container registry to Snyk.
 7. When the import ends:
    * You can view the newly imported image, marked with a **NEW** tag, on the **Projects** page. Images are grouped by repository and are each linked individually to a detailed **Project** page.
    * An **import log** becomes available; you can reach it at the top of the Projects list.
-   * To enrich the data and get recommendations regarding your base image, you can connect your Dockerfile to the image Project under **Settings**. For more information, see [Adding your Dockerfile and testing your base image](../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+   * To enrich the data and get recommendations regarding your base image, you can connect your Dockerfile to the image Project under **Settings**. For more information, see [Adding your Dockerfile and testing your base image](../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
-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:
+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/mceclip1-5-.png" alt="GitHub Project in Projects listing"><figcaption><p>GitHub Project in Projects listing</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/projects_github_container_registry.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).
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-gitlab-container-registry.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-gitlab-container-registry.md
index 3744b534485b..446d9a1cc05b 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-gitlab-container-registry.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-gitlab-container-registry.md
@@ -22,8 +22,6 @@ This page explains how to set up GitLab Container Registry integration in Snyk a
 3. In the **Container registry name** fill in the full URL to the registry you want to integrate with.
 4. To finish, click **Save**.
 
-<figure><img src="../../../.gitbook/assets/mceclip1-6-.png" alt="GitLab Container Registry Account credentials"><figcaption><p>GitLab Container Registry Account credentials</p></figcaption></figure>
-
 If you are using a self-hosted GitLab Container Registry, [contact Snyk Support](https://support.snyk.io/hc/en-us/requests/new) 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.&#x20;
@@ -58,11 +56,11 @@ The steps follow for adding images from GitLab Container Registry to Snyk.
 7. When the import ends:
    * You can view the newly imported image, marked with a **NEW** tag, on the **Projects** page. Images are grouped by repository and are each linked individually to a detailed **Project** page.
    * An **import log** becomes available; you can reach it at the top of the Projects list.
-   * To enrich the data and get recommendations regarding your base image, under **Settings**, you can connect your Dockerfile to the image Project. For more information, see[ Adding your Dockerfile and testing your base image.](../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md)
+   * To enrich the data and get recommendations regarding your base image, under **Settings**, you can connect your Dockerfile to the image Project. For more information, see[ Adding your Dockerfile and testing your base image.](../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md)
 
 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="GitLab Container Registry Project in Projects listing"><figcaption><p>GitLab Container Registry Project in Projects listing</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/mceclip0-14-.png" alt=""><figcaption><p>GitLab Container Registry Project in Projects listing</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).
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/add-images-to-snyk-from-acr.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/add-images-to-snyk-from-acr.md
index ca5d6fc5595a..e9c31683b419 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/add-images-to-snyk-from-acr.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/add-images-to-snyk-from-acr.md
@@ -11,15 +11,13 @@ Snyk tests and monitors Google Container Registry (GCR) container images by eval
 
 Log in to your account and navigate to the relevant Group and Organization you want to manage.
 
-Go to **Projects** and click **Add projects**. The list of integrations already configured in your account opens, similar to the following:&#x20;
-
-<figure><img src="../../../../.gitbook/assets/Screenshot 2023-03-31 at 17.39.47.png" alt="Integrations configured in a Snyk account"><figcaption><p>Integrations configured in a Snyk account</p></figcaption></figure>
+Go to **Projects** and click **Add projects**. The list of integrations already configured in your account opens.&#x20;
 
 Decide which images you want to test. The view displays all of the available images for the registry to which you connected, grouped by each of your repositories, similar to the following:
 
-<figure><img src="../../../../.gitbook/assets/Screenshot 2023-03-31 at 17.50.25.png" alt="All available images for the registry to which you connected"><figcaption><p>All available images for the registry to which you connected</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/Screenshot 2023-03-31 at 17.50.25.png" alt="" width="375"><figcaption><p>Available images for the registry to which you connected</p></figcaption></figure>
 
-Continue by following these steps:
+Continue with the following steps:
 
 1. Select single or multiple images by using any or all of the following methods:
    * Type the name of a single image for import in the **Image Name** field at number one (1), the Image Name field in the preceding image.
@@ -29,17 +27,11 @@ Continue by following these steps:
 
     A status bar appears at the top of the page as the images are imported; you can continue working while the images are being imported.
 3. When the import ends, a notification of success or failure appears at the top of the page. Click **Refresh** to view the **Projects** page with the newly imported images. Images are grouped by repository and are each linked individually to a detailed Projects page.
-4. You can now connect your Git repo to this Project in order to use your Dockerfile for enriched fix advice. For more information, see [Adding your Dockerfile and testing your base image](../../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
-
-GCR files are indicated with a unique icon. You can now filter to view only those Projects:
-
-<div align="left">
-
-<figure><img src="../../../../.gitbook/assets/Screenshot 2023-03-31 at 18.10.17 (1).png" alt="GCR added to integrations filters"><figcaption><p>GCR added to integrations filters</p></figcaption></figure>
+4. You can now connect your Git repo to this Project in order to use your Dockerfile for enriched fix advice. For more information, see [Adding your Dockerfile and testing your base image](../../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
-</div>
+GCR files are indicated with a unique icon. You can now filter to view only those Projects.
 
-<figure><img src="../../../../.gitbook/assets/Screenshot 2023-03-31 at 18.06.20.png" alt="Projects listing with two filters applied"><figcaption><p>Projects listing with two filters applied</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/Screenshot 2023-03-31 at 18.06.20.png" alt=""><figcaption><p>Examples of GCR Projects</p></figcaption></figure>
 
 GCR integration works similarly to other Snyk integrations. To continue to monitor, fix, and manage your Projects, see the relevant pages in the Snyk docs.
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/enable-permissions-to-access-gcr.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/enable-permissions-to-access-gcr.md
index 0a29b34675e8..2ce715390d18 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/enable-permissions-to-access-gcr.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-google-container-registry-gcr/enable-permissions-to-access-gcr.md
@@ -14,9 +14,9 @@ From the relevant project in Google, ensure you have created a service account f
    * **Role** - Storage Object Viewer (roles/storage.objectViewer)
    * **Service account ID** - leave empty
    * **Key type** - JSON
-3. Click **Create** to generate the key for your project.
-4. Copy _the entire contents_ of the JSON file, which is similar to the following:
+3. Click **Create** to generate the key for your Project.
+4. Copy the entire contents of the JSON file, which is similar to the following:
 
-<figure><img src="../../../../.gitbook/assets/uuid-c4e3b781-e575-5ab8-6cea-b0a8654068c4-en.png" alt="GCR_key_file_contents"><figcaption><p>GCR_key_file_contents</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/uuid-c4e3b781-e575-5ab8-6cea-b0a8654068c4-en.png" alt=""><figcaption><p>GCR_key_file_contents</p></figcaption></figure>
 
 Save the data you copied to paste it when [configuring integration for GCR](configure-integration-for-gcr.md).
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-harbor-container-registry.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-harbor-container-registry.md
index ca3ee2050417..d1ad6ab7712a 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-harbor-container-registry.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-harbor-container-registry.md
@@ -2,7 +2,7 @@
 
 {% hint style="info" %}
 **Feature availability**\
-This feature is available with Enterprise plans. See [pricing plans](https://snyk.io/plans/) for more details.
+This feature is available only with Enterprise plans. For more information, see [pricing plans](https://snyk.io/plans/).
 {% endhint %}
 
 Snyk integrates with Harbor Container Registry to enable you to import your container images and monitor them for vulnerabilities.
@@ -27,18 +27,15 @@ Follow these instructions to set up Harbor integration in Snyk and start managin
 
 If you are using a self-hosted Harbor registry, contact Snyk 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).
 
-<figure><img src="../../../.gitbook/assets/mceclip2-1-.png" alt="Harbor Account credentials and Container registry name"><figcaption><p>Harbor Account credentials and Container registry name</p></figcaption></figure>
-
 {% hint style="info" %}
-**Note:** To set up the integration, the Harbor user should be an admin user. The integration currently uses /v2/\_catalog endpoint for listing repositories.
+To set up the integration, the Harbor user should be an admin user. The integration uses /v2/\_catalog endpoint for listing repositories.
 {% endhint %}
 
 <figure><img src="../../../.gitbook/assets/mceclip1-8-.png" alt="Harbor Account credentials with Broker token"><figcaption><p>Harbor Account credentials with Broker token</p></figcaption></figure>
 
-Snyk tests the connection values, and the page reloads, now displaying Harbor integration information. The **Add your Harbor images to Snyk** button becomes available. If the connection to Harbor fails, a notification appears under the **Connected to Harbor** section.\
-
+Snyk tests the connection values, and the page reloads, now displaying Harbor integration information. The **Add your Harbor images to Snyk** button becomes available. If the connection to Harbor fails, a notification appears under the **Connected to Harbor** section.
 
-When the connection is successful, you can use Snyk to scan your images from Harbor.
+Once the connection is successful, you can use Snyk to scan your images from Harbor.
 
 ## Scan container images from Harbor in Snyk
 
@@ -64,13 +61,13 @@ Follow these instructions to add images from Harbor to Snyk.
 7. When the import ends:
    1. You can view the newly imported image, marked with a **NEW** tag, on the **Projects** page. Images are grouped by repository and are each linked individually to a detailed Projects page.
    2. An **import log** becomes available; you can reach it from the top of the Projects list.
-   3. To enrich the data and get recommendations regarding your base image, under **Settings,** you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+   3. To enrich the data and get recommendations regarding your base image, under **Settings,** you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
 Harbor imports are indicated with a unique icon. You can also filter to view only the Harbor Projects:
 
 <figure><img src="../../../.gitbook/assets/mceclip1-9-.png" alt="Harbor Projects in Projects listing"><figcaption><p>Harbor Projects in Projects listing</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).
+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).
 {% endhint %}
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/README.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/README.md
index 6152b01a2c67..97965b85cac7 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/README.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/README.md
@@ -1,8 +1,8 @@
-# Container security with JFrog Artifactory integration
+# Integrate with JFrog Artifactory
 
 {% hint style="info" %}
 **Feature availability**\
-This feature is available with Enterprise plans. See [pricing plans](https://snyk.io/plans/) for more details.
+This feature is available only with Enterprise plans. For more information, see [pricing plans](https://snyk.io/plans/).
 {% endhint %}
 
 Snyk integrates with JFrog Artifactory Container Registry to enable you to import your Projects and monitor your containers for vulnerabilities. Snyk tests the Projects you have imported for any known security vulnerabilities found at a frequency you control.
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/add-artifactory-images-to-snyk.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/add-artifactory-images-to-snyk.md
index b4f9dc1f5fc6..c639b5a0f404 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/add-artifactory-images-to-snyk.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/add-artifactory-images-to-snyk.md
@@ -10,14 +10,8 @@ Snyk tests and monitors your Artifactory container images by evaluating the tags
 ## **Steps to adding Artifactory images to Snyk**
 
 * Log in to your account and navigate to the relevant Group and Organization you want to manage.
-* Go to **Projects** and click **Add projects**. The list of integrations already configured on your account opens, similar to the following:
-
-<figure><img src="../../../../.gitbook/assets/uuid-dd01aab7-482f-0fc2-01de-c2427a14a0e0-en.png" alt="Integrations configured on an account"><figcaption><p>Integrations configured on an account</p></figcaption></figure>
-
-* The view **Which images do you want to test?** opens, displaying all of the available images for the registry to which you connected, grouped by each of your repositories, similar to the following:
-
-<figure><img src="../../../../.gitbook/assets/uuid-bd9cf629-f5fb-b28b-1fc1-40df2367a7f9-en (1) (1) (2) (4) (2) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) ( (22).png" alt="All available images for the registry to which you connected"><figcaption><p>All available images for the registry to which you connected</p></figcaption></figure>
-
+* Go to **Projects** and click **Add projects**. The list of integrations already configured on your account opens.
+* The view **Which images do you want to test?** opens, displaying all of the available images for the registry to which you connected, grouped by each of your repositories.
 * Select single or multiple images using any or all of the following methods:
   * Type the name of a single image for import in the Image Name field (at number 1, the image name field, in the image above),
   * Select any of the repositories if you want to import all of the associated images (at number 2, the second item listed in the image above).
@@ -26,14 +20,14 @@ Snyk tests and monitors your Artifactory container images by evaluating the tags
 
     A status bar appears at the top of the page as the images are imported; you can continue working in the meantime.
 * When the import ends, a notification of success or failure appears at the top of the page. Click Refresh to view the Projects page with the newly imported images. Images are grouped by repository and are each linked individually to a detailed Projects page.
-* You can now connect your Git repo to this Project in order to use your Dockerfile for enriched fix advice. For more information, see [Adding your Dockerfile and testing your base image](../../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+* You can now connect your Git repo to this Project in order to use your Dockerfile for enriched fix advice. For more information, see [Adding your Dockerfile and testing your base image](../../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
-Images are indicated with a unique icon ![Artifactory](<../../../../.gitbook/assets/image (5) (2).png>).  You can filter to view only the Artifactory Projects:
+Images are indicated with a unique icon.  You can filter to view only the Artifactory Projects.
 
 <figure><img src="../../../../.gitbook/assets/uuid-5c95894c-97d8-a6a9-0969-7c5fee541211-en.png" alt="List of Artifactory Projects"><figcaption><p>List of Artifactory Projects</p></figcaption></figure>
 
 Artifactory integration works like other Snyk integrations. To continue to monitor, fix and manage your Projects, see the relevant pages in the Snyk user documentation.
 
 {% 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. See [Detecting application vulnerabilities in container images ](../../use-snyk-container/detect-application-vulnerabilities-in-container-images.md)for more information.
+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. See [Detecting application vulnerabilities in container images ](../../use-snyk-container/detect-application-vulnerabilities-in-container-images.md)for more information.
 {% endhint %}
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/configuring-your-jfrog-artifactory-container-registry-integration.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/configuring-your-jfrog-artifactory-container-registry-integration.md
index 0cba3b78b4aa..8f4c07e0bbef 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/configuring-your-jfrog-artifactory-container-registry-integration.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-jfrog-artifactory/configuring-your-jfrog-artifactory-container-registry-integration.md
@@ -18,7 +18,7 @@ The instructions on this page explain how to enable integration between one Arti
    * **Username and Password  -** use your Artifactory login credentials. If you're using SSO configuration, you must generate an access token in Artifactory and use the token details to login.
    * **Container registry name -** the full registry URL: `<subdomain>.jfrog.io/artifactory/api/docker/<repo-name>`
 
-<figure><img src="https://user-images.githubusercontent.com/112600/144875482-078b715e-2834-469b-9983-7e88a65f175e.png" alt="Artifactory account credentials" width="375"><figcaption><p>Artifactory account credentials</p></figcaption></figure>
+<figure><img src="https://user-images.githubusercontent.com/112600/144875482-078b715e-2834-469b-9983-7e88a65f175e.png" alt="" width="375"><figcaption><p>Artifactory account credentials</p></figcaption></figure>
 
 4. Click **Save Changes**.  A confirmation appears.
 
@@ -26,6 +26,4 @@ The instructions on this page explain how to enable integration between one Arti
 To set up the integration, the Artifactory credentials need, at minimum, read permissions to the relevant Artifactory repository.
 {% endhint %}
 
-Snyk tests the connection values and the page reloads, now displaying integration details as you entered them. At the top of the screen, a confirmation message in green indicates that the details were saved. If the connection fails, a notification appears.
-
-<figure><img src="../../../../.gitbook/assets/artifactory_confirmation.png" alt="" width="375"><figcaption></figcaption></figure>
+Snyk tests the connection values and the page reloads, now displaying integration details as you entered them. At the top of the screen, a confirmation message indicates that the details were saved. If the connection fails, a notification appears.
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/add-images-to-snyk-from-acr.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/add-images-to-snyk-from-acr.md
index 0dde649a3960..1e272a5a1888 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/add-images-to-snyk-from-acr.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/add-images-to-snyk-from-acr.md
@@ -10,16 +10,10 @@ Snyk tests and monitors Microsoft Azure Container Registry (ACR) container image
 ## Steps to add images to Snyk from ACR
 
 1. Log in to your account and navigate to the relevant Group and Organization you want to manage.
-2.  Go to **Projects**, and click **Add projects**. The list of integrations already configured on your account opens, similar to the following:
-
-
-
-    <figure><img src="../../../../.gitbook/assets/uuid-dd01aab7-482f-0fc2-01de-c2427a14a0e0-en.png" alt="List of integrations configured in an account"><figcaption><p>List of integrations configured in an account</p></figcaption></figure>
+2. Go to **Projects**, and click **Add projects**. The list of integrations already configured on your account opens.
 
 The view **Which images do you want to test?** opens, displaying all of the available images for the registry to which you connected, grouped by each of your repositories, similar to the following:
 
-![All available images for the registry to which you connected](<../../../../.gitbook/assets/uuid-bd9cf629-f5fb-b28b-1fc1-40df2367a7f9-en (1) (1) (2) (4) (2) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) ( (22).png>)
-
 1. Select single or multiple images using any or all of the following methods:
    1. Type the name of a single image for import in the **Image Name** field (at number 1, the Image Name field in the image above),
    2. Select any of the repositories if you want to import all of the associated images (at number 2, the second item listed in the image above).
@@ -30,7 +24,7 @@ The view **Which images do you want to test?** opens, displaying all of the avai
 3. When the import ends, a notification of success or failure appears at the top of the page. Click **Refresh** to view the **Projects** page with the newly imported images.\
    Images are grouped by repository and linked individually to a detailed Projects page.
 4. You can now connect your Git repository to this Project in order to use your Dockerfile for enriched fix advice.\
-   For more information, see [Adding your Dockerfile and testing your base image](../../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+   For more information, see [Adding your Dockerfile and testing your base image](../../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
 ACR files are indicated with a unique icon ![ACR](../../../../.gitbook/assets/uuid-5d10608d-d674-d4ee-d6c2-6faadd6fc8ea-en.png) . You can filter to view only those Projects:
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/configure-integration-for-acr.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/configure-integration-for-acr.md
index 2a65b1745d7f..2c537a5e2fa2 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/configure-integration-for-acr.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-microsoft-azure-container-registry-acr/configure-integration-for-acr.md
@@ -14,5 +14,3 @@ Follow these steps:
     Snyk tests the connection values, and the page reloads, now displaying ACR integration information.\
     A confirmation message that the details were saved also appears in green at the top of the screen.\
     In addition, if the connection to Azure failed, a notification appears under the **Connected to ACR section**.
-
-<figure><img src="../../../../.gitbook/assets/image (9) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt="ACR account credentials"><figcaption><p>ACR account credentials</p></figcaption></figure>
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-nexus-container-registry.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-nexus-container-registry.md
index 68558d52156b..293858591f01 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-nexus-container-registry.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-nexus-container-registry.md
@@ -24,8 +24,6 @@ This page explains how to set up Nexus Container Registry integration in Snyk an
 * In the **Account credentials** section, enter your Nexus username and password login credentials. In the **container registry name,** fill in the full URL to the registry you want to integrate with.
 * To finish, click **Save**.
 
-![Nexus Container Registry Account credentials](../../../.gitbook/assets/mceclip1-20-.png)
-
 If you are using a self-hosted Nexus registry, [contact Snyk Support](https://support.snyk.io/hc/en-us/requests/new) 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 Nexus integration information. The **Add your Nexus images to Snyk** button becomes available.
@@ -59,7 +57,7 @@ Follow these steps to add images from Nexus to Snyk.
 6. When the import ends:
    1. You can view the newly imported image, marked with a **NEW** tag, on the **Projects** page. Images are grouped by repository and are each linked individually to a detailed **Project** page.
    2. An **import log** becomes available; you can reach it at the top of the Projects list.
-   3. To enrich the data and get recommendations regarding your base image, under **Settings,** you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+   3. To enrich the data and get recommendations regarding your base image, under **Settings,** you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
 Nexus imports are indicated with a unique icon, and you can also filter to view only Nexus Projects:
 
diff --git a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-quay-container-registry.md b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-quay-container-registry.md
index c5277d25c0cf..044947fa4fa8 100644
--- a/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-quay-container-registry.md
+++ b/docs/scan-with-snyk/snyk-container/container-registry-integrations/integrate-with-quay-container-registry.md
@@ -18,8 +18,6 @@ Integration with Quay is available for all Snyk users.
 1. In your Snyk account, navigate to **Integrations.** Under the **Container Registries** section, find the **Quay** option and click it.
 2. In the **Account credentials** section, enter your Quay username and password login credentials. In the **container registry name**, enter the full URL to the registry you want to integrate with. This can be a cloud-based Quay or a private host. To finish, click **Save**.
 
-<figure><img src="../../../.gitbook/assets/mceclip1-10-.png" alt="Configure Quay integration"><figcaption><p>Configure Quay integration</p></figcaption></figure>
-
 If you are using a self-hosted Quay registry, [contact Snyk Support](https://support.snyk.io/hc/en-us/requests/new) 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).
 
 {% hint style="info" %}
@@ -32,8 +30,6 @@ When the connection succeeds, you can use Snyk to scan your images from Quay.
 
 Snyk tests and monitors your Quay container images by evaluating the tags in your repositories. After import to Snyk, your image vulnerabilities are identified and can be triaged easily.
 
-To add images from Quay to Snyk:
-
 ## Scan container images from Quay in Snyk
 
 ### **Prerequisites** for Quay image scanning
@@ -56,7 +52,7 @@ To add images from Quay to Snyk:
 7. When the import ends:
    1. You can view the newly imported image, marked with a **NEW** tag, on the **Projects** page; Images are grouped by repository and linked individually to a detailed **Project** page.\
       An **import log** becomes available; you can reach it at the top of the Projects list.
-   2. To enrich the data and get recommendations regarding your base image, from the **Settings** you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../../../scan-with-snyk/snyk-container/scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
+   2. To enrich the data and get recommendations regarding your base image, from the **Settings** you can connect your Dockerfile to the image Project. For more information, see [Adding your Dockerfile and testing your base image](../scan-your-dockerfile/detect-vulnerable-base-images-from-your-dockerfile.md).
 
 Quay imports are designated with a unique icon, and you can filter the integration in the **Projects** view to see Quay Projects only as shown:
 
diff --git a/docs/scan-with-snyk/snyk-container/how-snyk-container-works/severity-levels-of-detected-linux-vulnerabilities.md b/docs/scan-with-snyk/snyk-container/how-snyk-container-works/severity-levels-of-detected-linux-vulnerabilities.md
index 9c15166552fd..581841336848 100644
--- a/docs/scan-with-snyk/snyk-container/how-snyk-container-works/severity-levels-of-detected-linux-vulnerabilities.md
+++ b/docs/scan-with-snyk/snyk-container/how-snyk-container-works/severity-levels-of-detected-linux-vulnerabilities.md
@@ -18,7 +18,7 @@ Snyk supports relative importance in Ubuntu, Debian, Red Hat Enterprise Linux (R
 
 For each issue, information appears on the Project page, under **Security information**.
 
-<figure><img src="../../../.gitbook/assets/Debian-Unimportant.png" alt="Example of a vulnerability the security rating Unimportant"><figcaption><p>Example of a vulnerability the security rating Unimportant</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/project_page_security_information.png" alt=""><figcaption><p>Security information on a Project page</p></figcaption></figure>
 
 ## External information sources for relative importance
 
@@ -35,4 +35,4 @@ To provide information for the distribution, Snyk uses the following external so
 
 To create a report showing only NVD Score and Severity (without the Linux-maintainer rating), add the NVD Score and NVD Severity columns in the Issues Detail report.
 
-<figure><img src="../../../.gitbook/assets/container-NVD-report.png" alt="Example of a report with NVD Score and Severity"><figcaption><p>Example of a report with NVD Score and Severity</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/container-NVD-report.png" alt=""><figcaption><p>Example of a report with NVD Score and NVD Severity</p></figcaption></figure>