From d98ad39ee980988db3bbe13ece07b46eaad218a4 Mon Sep 17 00:00:00 2001 From: scjane Date: Mon, 20 Feb 2017 19:04:44 +0800 Subject: [PATCH] Update content_trust.md (#1860) --- engine/security/trust/content_trust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/security/trust/content_trust.md b/engine/security/trust/content_trust.md index 8b09ffd5ff..da77e9936f 100644 --- a/engine/security/trust/content_trust.md +++ b/engine/security/trust/content_trust.md @@ -66,7 +66,7 @@ the unsigned version of an image before officially signing it. Image consumers can enable content trust to ensure that images they use were signed. If a consumer enables content trust, they can only pull, run, or build with trusted images. Enabling content trust is like wearing a pair of -rose-colored glasses. Consumers "see" only signed images tags and the less +rose-colored glasses. Consumers "see" only signed image tags and the less desirable, unsigned image tags are "invisible" to them. ![Trust view](images/trust_view.png)