docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

two more nits 

Signed-off-by: LRubin <lrubin@docker.com>
This commit is contained in:
LRubin 2017-01-04 11:56:15 -08:00 committed by Joao Fernandes
parent 9ebe122ed5
commit 3f959afd8b
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
datacenter/dtr/2.2/guides/configure/setup-scanning-dtr.md
View File

@ -21,7 +21,7 @@ action is needed. If you are using a license associated with an organization
account, you may need to make sure your Docker ID is a member of the `Owners` account, you may need to make sure your Docker ID is a member of the `Owners`
team. Only `Owners` team members can download license files for an Organization. team. Only `Owners` team members can download license files for an Organization.
If you will be allowing the Security Scanning module to update itself If you will be allowing the Security Scanning database to update itself
automatically, make sure that the server hosting your DTR instance can access automatically, make sure that the server hosting your DTR instance can access
`https://dss-cve-updates.docker.com/` on the standard https port 443. `https://dss-cve-updates.docker.com/` on the standard https port 443.

2
datacenter/dtr/2.2/guides/security-scan-dtr.md
View File

@ -55,7 +55,7 @@ To start a security scan:
1. Navigate to the repository. 1. Navigate to the repository.
2. Click the **Images** tab. 2. Click the **Images** tab.
3. Locate the image tag that you want to scan. 3. Locate the image tag that you want to scan.
3. In the **Vulnerabilities** column, click **Start a scan**. 4. In the **Vulnerabilities** column, click **Start a scan**.
DTR begins the scanning process. You may need to refresh the page to see the results once the scan is complete. DTR begins the scanning process. You may need to refresh the page to see the results once the scan is complete.