Doc clean-ups (typos, links, etc.) #986
Merged
Conversation
This file contains 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
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.
merkelized → merkleized
per → peer
“provide clients with a solid reference how the known SSZ objects should be encoded” → “provide clients with a solid reference for how the known SSZ objects should be encoded”
live/stay-on-same-spec links for the python-poc, sharding faq, ssz_static references, fork_timelines & constant_presets formats
2/6 of the bls handler docs had periods after their encoding details; added the rest for standardization
commas added for clarity: “If there are two solutions(,) the one with higher imaginary component is favored; if both solutions have equal imaginary component(,) the one with higher real component is favored”