From b2c87522117693a1d79c6144f78010548449fe66 Mon Sep 17 00:00:00 2001
From: jingfangliu <jingfangliu@google.com>
Date: Fri, 31 May 2019 09:58:48 -0700
Subject: [PATCH] update validation transformer example text

---
 examples/validationTransformer/README.md | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/examples/validationTransformer/README.md b/examples/validationTransformer/README.md
index d2134d0f0..d6c53b5c1 100644
--- a/examples/validationTransformer/README.md
+++ b/examples/validationTransformer/README.md
@@ -4,14 +4,13 @@
 [kubeval]: https://github.com/instrumenta/kubeval
 [plugin]: ../../docs/plugins.md
 
-Kustomize doesn't validate the resources that it loads
-from files or [bases], but kustomize has a [plugin]
-system that allows one to validate the
-loaded resources.
+kustomize doesn't validate either its input or
+output beyond the validation provided by the
+marshalling/unmarshalling packages it depends on.
+
+Another tool, [kubeval], goes beyond this to do
+k8s aware validation. Here's a usage example:
 
-One way to validate Kubernetes resources is to run
-[kubeval] against the resource file. For example,
-an invalid resource file gives similar error:
 ```shell
 $ kubeval my-invalid-rc.yaml
 The document my-invalid-rc.yaml contains an invalid ReplicationController