From bf1c1fa896251125dd675ed0f23c0c940affa999 Mon Sep 17 00:00:00 2001
From: Jessica Yao <jessica@heptio.com>
Date: Wed, 31 Jan 2018 11:42:47 -0800
Subject: [PATCH] clarify point about prototypes

Signed-off-by: Jessica Yao <jessica@heptio.com>
---
 docs/concepts.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/concepts.md b/docs/concepts.md
index 35dad18c..12c95e2b 100644
--- a/docs/concepts.md
+++ b/docs/concepts.md
@@ -87,7 +87,9 @@ All of the component files in an *app* can be deployed to a specified *environme
 
 ### Prototype
 
-Prototypes are often used as the basis for components; they are the reason that `ks generate` allows you to quickly move from a blank app to multiple complete manifests.
+Prototypes are *examples* that you can use as the basis for your components. By `ks generate`-ing components from prototypes, you can quickly move from a blank app to multiple complete manifests.
+
+*Although you can use these components right away, they are really intended as a starting point.* If a prototype-generated component does not fully address your needs, you can directly modify its Jsonnet afterwards (e.g. adding parameters).
 
 By itself, a prototype is a pre-written but incomplete manifest:
 
-- 
GitLab