From 61db7b267eaf662bec37ddde7aa242affc646b2a Mon Sep 17 00:00:00 2001
From: drkvetta <dean.knudson@gmail.com>
Date: Sun, 15 Mar 2026 13:22:36 -0500
Subject: [PATCH] Revise nested match examples in basics.md

Updated nested match examples better explain and demonstrate the feature. The current example works but undersells the feature: the sub-match is only used once, so there is no apparent reason to nest rather than just write the word directly. The following example nests the same sub-match in two parent matches, making the core benefit clear: define content once, reuse it everywhere, and update it in one place.
---
 docs/matches/basics.md | 27 ++++++++++++++++++++-------
 1 file changed, 20 insertions(+), 7 deletions(-)

diff --git a/docs/matches/basics.md b/docs/matches/basics.md
index 97a90f2..57388e2 100644
--- a/docs/matches/basics.md
+++ b/docs/matches/basics.md
@@ -499,20 +499,33 @@ and store all your images there. Let's say I stored the `cat.png` image. We can
 
 
 ```yaml
-  - trigger: :one
-    replace: nested
+  - trigger: :store
+    replace: "ABC Store"
 
-  - trigger: :nested
-    replace: This is a {{output}} match
+  - trigger: :receipt_header
+    replace: "Receipt — {{store_name}}"
     vars:
-      - name: output
+      - name: store_name
         type: match
         params:
-          trigger: :one
+          trigger: :store
+
+  - trigger: :invoice_header
+    replace: "Invoice from {{store_name}} — thank you for your purchase."
+    vars:
+      - name: store_name
+        type: match
+        params:
+          trigger: :store
 ```
 
 
-At this point, if you type `:nested` you'll see `This is a nested match` appear.
+
+At this point, if you type `:receipt_header` you'll see `Receipt — ABC Store` appear.
+
+If you type `:invoice_header` you'll see `Invoice from ABC Store — thank you for your purchase.` appear.
+
+If the store name changes, you update `:store` in a single place and both parent matches reflect the change automatically.
 
 ## Keyboard Triggers