Use the CAP-67 shorthand on the token interface page - #2726
Open
ElliotFriend wants to merge 1 commit into
Open
Conversation
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) <noreply@anthropic.com>
|
Preview is available here: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #2725, which wrote
CAP-0067. The docs use theCAP-NNshorthand almost everywhere:CAP-67appears 22 times against 4 uses of the padded form, and the same pattern holds for CAP-46, CAP-66, CAP-71, and the rest. The link target keeps the paddedcap-0067.mdfilename, since that is the real path in stellar-protocol.It also matters for tooling. The Raven finding behind #2725 records its marker as
CAP-67, so a literal recheck against the padded spelling reads as unresolved even though the citation is right there.Scope is the one line. The other four padded references (
anatomy-of-an-asset.mdx,send-and-receive-payments.mdx,galexie/admin_guide/running.mdx,state-archival.mdx, and a few more) are pre-existing and left alone.🤖 Generated with Claude Code