From b2c60c1ecf82225f722c2628a225dd37a6f309e5 Mon Sep 17 00:00:00 2001 From: Elliot Date: Tue, 4 Aug 2026 16:12:22 -0500 Subject: [PATCH] Use the CAP-67 shorthand on the token interface page The sentence added in #2725 wrote CAP-0067, while the docs use the CAP-NN shorthand almost everywhere: CAP-67 appears 22 times against 4 uses of the padded form, and the same holds for CAP-46, CAP-66, CAP-71, and the rest. The link target keeps the padded cap-0067.md filename, which is the actual path in stellar-protocol. This also matters for tooling. The Raven finding that prompted #2725 records its marker as CAP-67, so a literal recheck against the padded spelling reads as unresolved even though the citation is present. Co-Authored-By: Claude Opus 5 (1M context) --- docs/tokens/token-interface.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tokens/token-interface.mdx b/docs/tokens/token-interface.mdx index 991ccd5ba..9aa356513 100644 --- a/docs/tokens/token-interface.mdx +++ b/docs/tokens/token-interface.mdx @@ -198,7 +198,7 @@ The event shapes in the interface above are the ones a SEP-41 contract token emi Code written against the shapes above will therefore mis-parse an event emitted by a Stellar Asset Contract, reading the asset identifier as a missing field or ignoring it entirely. -[CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) is the normative source for the Stellar Asset Contract shapes below, and for the unification of classic events described further down. +[CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) is the normative source for the Stellar Asset Contract shapes below, and for the unification of classic events described further down. | Event | SEP-41 contract token | Stellar Asset Contract | | --- | --- | --- |