Fix typos across core, iOS and Android - #865
Merged
Merged
Conversation
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.
Fixes 27 misspellings, three of them in filenames.
Most are comments and string literals, but a few were identifiers. Android's
Asset.isStackableandgetStackedAmount()hadstakemisspelled asstack— the property's own body callsStakeChain.isStaked()and the function sumsstaked, and both iOS and core already useisStakeable/stakedAmount/is_stakeable, so it was a parity gap too.gem_hypercore/src/core/hahser.rsbecomeshasher.rs, which clears the known-issue entry incore/skills/common-issues.md.Deliberately untouched: chain address literals in test vectors, Apple's own SecBase spellings in
Keychain/Status.swift, and external API field names (Mayanrecepient, HashDitacountAddress, Chatwootreferer_url).No behaviour change.