From cef65c21ff0ee7736863c82c77a39a05fd1e82f6 Mon Sep 17 00:00:00 2001
From: Narutama Aurum <narutamaaurum@gmail.com>
Date: Sun, 24 May 2026 07:59:24 +0800
Subject: [PATCH] docs: correct lease vendor namespace wording

---
 docs/guides/leases.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/guides/leases.md b/docs/guides/leases.md
index 3b07640..15f942d 100644
--- a/docs/guides/leases.md
+++ b/docs/guides/leases.md
@@ -27,7 +27,9 @@ patterns. Reserved capability names:
 | `cost.budget`    | Spend cap; entries are `currency:amount` strings (see §9.6 below). |
 
 Custom capability names MUST use `x-vendor.<vendor>.<cap>` (at least
-three dot-separated segments after the `x-vendor.` prefix):
+two dot-separated segments after the `x-vendor.` prefix). See the
+[vendor extensions guide](./vendor-extensions.md) for the canonical
+namespace rules:
 
 ```ts
 const lease = {
@@ -35,6 +37,10 @@ const lease = {
 };
 ```
 
+For the same namespace shape in another ARCP surface, the tracing
+middleware uses `x-vendor.opentelemetry.tracecontext` as its envelope
+extension key.
+
 ## Example
 
 ```ts