docs: clarify 'How does TUF secure updates?' for first-time readers - #165
Draft
harshgounder wants to merge 1 commit into
Draft
docs: clarify 'How does TUF secure updates?' for first-time readers#165harshgounder wants to merge 1 commit into
harshgounder wants to merge 1 commit into
Conversation
Restructures the dense paragraph into four concrete questions the metadata chain answers (trusted keys, version, hashes, expiry), addressing theupdateframework#164. Signed-off-by: Harsh Gounder <harshgounder@users.noreply.github.com>
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
1 participant
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 #164 (docs clarity, no code change).
Restructures the dense single paragraph into four concrete questions the metadata chain answers:
No behavioral/content claims changed — purely structural rewrite of the existing prose, preserving all links.
First-time contributor here. I noticed the contribution policy (#159) asks first-timers to work good-first-issue-labeled issues, but none are currently open. Happy to adjust scope per maintainer guidance.