Skip to content

📝 Inline fix most egregious typos - #1984

Open
JFWooten4 wants to merge 2 commits into
stellar:masterfrom
JFWooten4:cap76-stability-upgrade-docs
Open

📝 Inline fix most egregious typos#1984
JFWooten4 wants to merge 2 commits into
stellar:masterfrom
JFWooten4:cap76-stability-upgrade-docs

Conversation

@JFWooten4

Copy link
Copy Markdown
Contributor

This cherry-picks the first two commits made in #1803 just four days after the CAP-76 draft proposal was released. In deference to #1913 (comment) precedence for not updating after Final status, it can be added using a merge commit with the original commit metadata. This places the updates a full four days before the last adopting commit.

I worked well into the night to get this in as soon as possible after the bug. Even though I don't think all of it will get merged in, I really think we should do this minimum set of changes. c96ca2a can be brought up separately if the maintainers want to keep that style uniform downstream.

This looks super wierd with double backticks enclosing almost two sentences worth of text.
Presumably we cannot do an incorrect snapshot the wrong way as a double negative
Copilot AI review requested due to automatic review settings July 22, 2026 18:48

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Clarifies two passages in CAP-0076.

Changes:

  • Removes a duplicated correct_entry definition.
  • Removes a repeated “incorrectly.”

Comment thread core/cap-0076.md

If the entry is amendable, then a new ledger entry with value ``correct_entry` - base64 encoded `LedgerEntry` XDR, the correct value that should have been archived (i.e. the value of the affected entry at the moment when it has been archived)
` (from the table) will be written to the Hot Archive and thus become the most recent state of the entry that will be used for the restoration.
If the entry is amendable, then a new ledger entry with value `correct_entry` (defined above) from the table will be written to the Hot Archive and thus become the most recent state of the entry that will be used for the restoration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants