docs(marshal): Update to latest agreed ocapn terminology #1988
Conversation
This file contains 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
dckc
reviewed
Jan 19, 2024
dckc
reviewed
Jan 19, 2024
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.
closes: #XXXX
refs: #XXXX
Description
Upgrade the smallcaps cheatsheet's "OCapn name" column to use the latest agreed OCapN names.
Attn @cwebber @tsyesika @jar398
Security Considerations
none
Scaling Considerations
none
Documentation Considerations
This PR itself doesn't change the first column "Passable value" of the names we normally use when we're not speaking to OCapN interoperability, so none there.
OCapN connected discussions have largely already moved to the new terminology, so this is mostly catchup.
Testing Considerations
none
Upgrade Considerations
none