docs(privacy): use "private transfers" instead of "confidential transfers" - #1769
Merged
Merged
Conversation
Align terminology across the Starknet Privacy docs. The overview page's subtitle said "Confidential transfers" while the body describes "private asset transfers" — two different concepts. Standardize on "private transfers". Leaves the distinct "confidential note(s)" term and the separate Starkzap (Tongo) "Confidential Transfers" feature unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
eitanm-starkware
approved these changes
Jul 14, 2026
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This branch was successfully deployed
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
2 participants
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.
What
Standardizes wording in the Starknet Privacy docs: "confidential transfer(s)" → "private transfer(s)".
Why
The Starknet Privacy Overview page mixed both terms — the page subtitle said "Confidential transfers on Starknet…" while the body describes a "protocol for private asset transfers." These are different concepts, so the mismatch was confusing.
Changes
build/starknet-privacy/overview.mdx— page subtitle + "Why Starknet Privacy?" introbuild/starknet-privacy/strk20-by-example.mdx— page subtitlelearn/cheatsheets/tools.mdx— STRK20 by Example entryDeliberately unchanged
🤖 Generated with Claude Code