Skip to content

chore: fix assorted typos in packages/ doc comments and messages - #11505

Open
SafraNako wants to merge 1 commit into
dfinity:masterfrom
SafraNako:chore/fix-packages-typos
Open

chore: fix assorted typos in packages/ doc comments and messages#11505
SafraNako wants to merge 1 commit into
dfinity:masterfrom
SafraNako:chore/fix-packages-typos

Conversation

@SafraNako

Copy link
Copy Markdown
Contributor

What

Fixes 17 spelling mistakes across five packages/ crates. All changes are in
doc comments, test comments, one .expect() panic message, and the
user-facing writeln! output of ValuePredicateFailurestext only, no
code / API / behavior changes
.

Crate Fix
ic-ed25519 cooresponding / coorespondscorresponding / corresponds
ic-hpke identiferidentifier, occuredoccurred
ic-secp256k1 infalliableinfallible
icrc-ledger-types successfullsuccessful (pretty-print output)
pocket-ic instaceinstance, overridenoverridden, comparisioncomparison

Notes

  • Found with codespell; each hit was reviewed individually.
  • No CHANGELOG.md files touched — the one remaining infalliable in
    ic-ed25519/CHANGELOG.md sits under the already-released 0.6.0 heading and
    is left as-is.
  • No dependency changes, so no Bazel repin needed.

🤖 Generated with Claude Code

Corrects spelling in doc comments, test comments, an .expect() panic
message, and user-facing writeln! output across five packages/ crates.
Comment/string text only; no code, API, or behavior changes.

- ic-ed25519:        cooresponding/cooresponds -> corresponding/corresponds
- ic-hpke:           identifer -> identifier, occured -> occurred
- ic-secp256k1:      infalliable -> infallible
- icrc-ledger-types: successfull -> successful
- pocket-ic:         instace -> instance, overriden -> overridden,
                     comparision -> comparison

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@cla-idx-bot

cla-idx-bot Bot commented Sep 8, 2026

Copy link
Copy Markdown

Dear @SafraNako,

In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.

If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.

— The DFINITY Foundation

@basvandijk basvandijk added the security-review-passed IDX or InfraSec have concluded it's safe to run CI on the external PR. label Sep 8, 2026
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

@SafraNako
SafraNako marked this pull request as ready for review September 11, 2026 11:42
@SafraNako
SafraNako requested review from a team as code owners September 11, 2026 11:42
@SafraNako

Copy link
Copy Markdown
Contributor Author

Re-triggering checks now that the CLA has been signed (dfinity/cla#689).

@SafraNako SafraNako closed this Sep 11, 2026
@SafraNako SafraNako reopened this Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore @core-protocol @defi external-contributor security-review-passed IDX or InfraSec have concluded it's safe to run CI on the external PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants