docs: improve kargo concepts docs (#2564)

Signed-off-by: nitishfy <[email protected]> Signed-off-by: Kent Rancourt <[email protected]> Co-authored-by: Kent Rancourt <[email protected]> (cherry picked from commit 218bd0d)
akuity · Oct 8, 2024 · a52bfb7 · a52bfb7
1 parent 6d4aa91
commit a52bfb7
Showing 1 changed file with 8 additions and 4 deletions.
diff --git a/docs/docs/15-concepts.md b/docs/docs/15-concepts.md
@@ -19,10 +19,14 @@ for automatic promotions of new **freight**.
 ### What is a Stage?
 
 When you hear the term “environment”, what you envision will depend
-significantly on your perspective. To eliminate confusion, Kargo avoids the term
-"environment" altogether in favor of **stage**. The important feature of a stage
-is that its name ("test" or "prod," for instance) denotes an application
-instance's _purpose_ and not necessarily its _location_.
+significantly on your perspective. A developer, for example, may think of
+an "environment" as a specific _instance_ of an application they work on,
+while a DevOps engineer, may think of an "environment" as a particular segment
+of the infrastructure they maintain.
+
+To eliminate confusion, Kargo avoids the term "environment" altogether in favor of **stage**.
+The important feature of a stage is that its name ("test" or "prod," for instance)
+denotes an application instance's _purpose_ and not necessarily its _location_.
 [This blog post](https://akuity.io/blog/kargo-stage-not-environment/) discusses
 the rationale behind this choice.