Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
| ... | ... |
@@ -33,7 +33,7 @@ Finally, you'll need to have `git` installed on your local system or VM. |
| 33 | 33 |
## What is in the sandbox? |
| 34 | 34 |
|
| 35 | 35 |
If you are just using trust out-of-the-box you only need your Docker Engine |
| 36 |
-client and access to Docker's own public hub. The sandbox mimics a |
|
| 36 |
+client and access to the Docker hub. The sandbox mimics a |
|
| 37 | 37 |
production trust environment, and requires these additional components: |
| 38 | 38 |
|
| 39 | 39 |
| Container | Description | |
| ... | ... |
@@ -45,7 +45,7 @@ production trust environment, and requires these additional components: |
| 45 | 45 |
| MySQL | The database where all of the trust information will be stored | |
| 46 | 46 |
|
| 47 | 47 |
The sandbox uses the Docker daemon on your local system. Within the `notarysandbox` |
| 48 |
-you interact with a local registry rather than the public Docker Hub. This means |
|
| 48 |
+you interact with a local registry rather than the Docker Hub. This means |
|
| 49 | 49 |
your everyday image repositories are not used. They are protected while you play. |
| 50 | 50 |
|
| 51 | 51 |
When you play in the sandbox, you'll also create root and tagging keys. The |
| ... | ... |
@@ -50,4 +50,4 @@ publisher of all the data received from a registry over any channel. |
| 50 | 50 |
|
| 51 | 51 |
[Content trust](/security/trust) is currently only available for users of the |
| 52 | 52 |
public Docker Hub. It is currently not available for the Docker Trusted Registry |
| 53 |
-or for private registries. |
|
| 54 | 53 |
\ No newline at end of file |
| 54 |
+or for private registries. |