summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormoxiegirl <mary@docker.com>2015-08-13 06:42:26 -0700
committermoxiegirl <mary@docker.com>2015-08-13 06:42:26 -0700
commitef453f7118d704319768d8d9c0cfe79e2d521afa (patch)
treebcff2cf2c4eb82007971d9eff220509b0a15199f
parent650feb29f10bc2775877579c67534646949610f2 (diff)
downloaddocker-patch-bad-formatting.tar.gz
Fixing bad formatting reported by David via emailpatch-bad-formatting
Fixed and tested Signed-off-by: Mary Anthony <mary@docker.com>
-rw-r--r--docs/security/trust/trust_automation.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/security/trust/trust_automation.md b/docs/security/trust/trust_automation.md
index 0808d8cef2..08caa84956 100644
--- a/docs/security/trust/trust_automation.md
+++ b/docs/security/trust/trust_automation.md
@@ -32,7 +32,7 @@ $ export DOCKER_CONTENT_TRUST_TAGGING_PASSPHRASE="l7pEQcTKJjUHm6Lpe4"
Then, when pushing a new tag the Docker client does not request these values but signs automatically:
-``bash
+```bash
$ docker push docker/trusttest:latest
The push refers to a repository [docker.io/docker/trusttest] (len: 1)
a9539b34a6ab: Image already exists
@@ -45,7 +45,7 @@ Signing and pushing trust metadata
You can also build with content trust. Before running the `docker build` command, you should set the environment variable `DOCKER_CONTENT_TRUST` either manually or in in a scripted fashion. Consider the simple Dockerfile below.
-```Dockerfilea
+```Dockerfile
FROM docker/trusttest:latest
RUN echo
```