diff options
| author | Philipp C. H <pch@mailbox.org> | 2019-06-01 21:00:12 +0000 |
|---|---|---|
| committer | Philipp C. H <pch@mailbox.org> | 2019-06-01 21:00:12 +0000 |
| commit | a5b6a18dd40e58b420918e70eeab3e500a8a8d22 (patch) | |
| tree | 882cd9b8a2ee20a2acc67f7d7a11ccf44b4cf8ff /doc | |
| parent | 2ad5b30b6c02a3e3f84275121a709f5de75dac48 (diff) | |
| download | gitlab-ce-a5b6a18dd40e58b420918e70eeab3e500a8a8d22.tar.gz | |
Fix typo
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/user/project/container_registry.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/container_registry.md b/doc/user/project/container_registry.md index 83b268db967..58b7fe33906 100644 --- a/doc/user/project/container_registry.md +++ b/doc/user/project/container_registry.md @@ -53,7 +53,7 @@ If you visit the **Registry** link under your project's menu, you can see the explicit instructions to login to the Container Registry using your GitLab credentials. -For example if the Registry's URL is `registry.example.com`, the you should be +For example if the Registry's URL is `registry.example.com`, then you should be able to login with: ``` @@ -204,7 +204,7 @@ at the communication between the client and the Registry. The REST API between the Docker client and Registry is [described here](https://docs.docker.com/registry/spec/api/). Normally, one would just use Wireshark or tcpdump to capture the traffic and see where things went -wrong. However, since all communication between Docker clients and servers +wrong. However, since all communications between Docker clients and servers are done over HTTPS, it's a bit difficult to decrypt the traffic quickly even if you know the private key. What can we do instead? |