Added screenshots for security scanning setup

datacenter/dtr/2.2/guides/admin/configure/set-up-vulnerability-scans.md

@@ -41,7 +41,7 @@ If your current DTR license doesn't include scanning, you must first download th
 5. Click **Subscription Details** and select **Setup instructions**.
 6. Click **License key** below the Docker Datacenter logo.
     The license key (a `.lic` file) is downloaded to your local computer.
-
+	![](../../images/security-scanning-setup-1.png)
 Next, install the new license on the DTR instance.
 
 7. Log in to your DTR instance using an administrator account.
@@ -52,6 +52,8 @@ Next, install the new license on the DTR instance.
 
 10. Navigate to where you saved the license key (`.lic`) file, select it, and click **Open**.
 
+![](../../images/security-scanning-setup-2.png)
+
 Proceed to [enable DTR Security Scanning](#enable-dtr-security-scanning).
 
 ## Enable DTR security scanning
@@ -60,11 +62,12 @@ To enable security scanning in DTR:
 
 1. Log in to your DTR instance with an administrator account.
 2. Click **Settings** in the left navigation.
-3.  Click the **Security** tab.
+3. Click the **Security** tab.
 
     > **Note**: If you see a message on this tab telling you to contact your Docker sales representative, then the license installed on this DTR instance does not include Docker Security Scanning. Check that you have purchased Security Scanning, and that the DTR instance is using the latest license file.
 
 4. Click the **Enable scanning** toggle so that it turns blue and says "on".
+	![](../../images/security-scanning-setup-3.png)
 5.  Next, provide a security database for the scanner. **Security scanning will not function until DTR has a security database to use.**
 
     By default, security scanning is enabled in **Online** mode. In this mode,
@@ -73,7 +76,7 @@ To enable security scanning in DTR:
     manually upload a `.tar` file containing the security database.
 
     - If you are using `Online` mode, the DTR instance will contact a Docker server, download the latest vulnerability database, and install it. Scanning can begin once this process completes.<!--(TODO: no completion or confirmation message?) -->
-    - If you are using `Offline` mode, use the instructions in [Update scanning database - offline mode](#update-cve-database-offline-mode) to upload an initial security database.
+    - If you are using `Offline` mode, use the instructions in [Update scanning database - offline mode](#update-cve-database---offline-mode) to upload an initial security database.
 
 By default when Security Scanning is enabled, new repositories will automatically scan on `docker push`. If you had existing repositories before you enabled security scanning, you might want to [change repository scanning behavior](#set-repository-scanning-mode).
 
@@ -87,6 +90,8 @@ Two modes are available when Security Scanning is enabled:
 By default, _new_ repositories are set to `Scan on push & Scan manually`, but
 you can change this setting during repository creation.
 
+![](../../images/security-scanning-setup-4.png)
+
 Any repositories that existed before scanning was enabled are set to `Scan manually` mode by default. If these repositories are still in use, you can change this setting from each repository's **Settings** page.
 
 > **Note**: To change an individual repository's scanning mode, you must have
@@ -97,6 +102,7 @@ To change an individual repository's scanning mode:
 1. Navigate to the repository, and click the **Settings** tab.
 2. Scroll down to the **Image scanning** section.
 3. Select the desired scanning mode.
+![](../../images/security-scanning-setup-5.png)
 
 ## Update the CVE scanning database
 
@@ -166,7 +172,7 @@ To change the update mode:
 
 1. Log in to DTR as a user with administrator rights.
 2. Click **Settings** in the left navigation and click **Security**.
-3. Click **Offline**.
+3. Click **Online/Offline**.
 
 Your choice is saved automatically.