mermaid chart tweaks

Author: rsgalloway

README.md

@@ -13,17 +13,19 @@ Environment variable composition and activation layer for tools and processes.
 - Shared, policy-driven environments
 - Inspectable and deterministic behavior
 
-envstack focuses on **configuration and activation**, not dependency resolution.
+envstack environments are layered hierarchically, with later layers inheriting
+from and overriding earlier ones.
 
 ```mermaid
-flowchart TD
+flowchart LR
   default[default.env] --> prod[prod.env]
   prod --> dev[dev.env]
   prod --> test[test.env]
 ```
 
 Later layers override earlier ones. Use envstack -t VAR to trace where a value
-comes from.
+comes from. envstack focuses on **configuration and activation**, not dependency
+resolution.
 
 For the core concepts, see `docs/index.md`.
 

docs/examples.md

@@ -14,11 +14,11 @@ This is the simplest envstack use case and a direct evolution of a `.env` file.
 
 ```mermaid
 flowchart LR
-  base[default.env] --> local[local.env]
+  default[default.env] --> local[local.env]
 ```
 
 Typical characteristics:
-- One base environment
+- One default base environment
 - A small number of variables
 - Defaults that can be overridden externally
 
@@ -38,8 +38,8 @@ A common pattern is to define a shared base environment and layer environment
 tiers on top (e.g. dev, prod, CI).
 
 ```mermaid
-flowchart TD
-  base[default.env] --> prod[prod.env]
+flowchart LR
+  default[default.env] --> prod[prod.env]
   prod --> dev[dev.env]
   prod --> test[test.env]
 ```
@@ -66,7 +66,7 @@ envstack models this naturally through inheritance and layering.
 
 ```mermaid
 flowchart LR
-  base[default.env] --> prod[prod.env]
+  default[default.env] --> prod[prod.env]
   prod -. include .-> project[project.env]
 ```