Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos and grammatical errors in documentation #44

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix typos and grammatical errors in documentation #44

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4814bdd
Update CONTRIBUTING.md
savvar9991 Dec 18, 2024
9ef8010
Update CHANGELOG.md
savvar9991 Dec 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ structures in cometbft-proto.
single release (currently at 1.0.0-alpha.1) and generate all protobuf
structures at once.
* In the new versioned module structure corresponding to the CometBFT 1.0
protobuf packages, modules represending protocol domains come to the top
protobuf packages, modules representing protocol domains come to the top
level, e.g. `crate::abci`, `crate::types`. Each of these has a `v1` module
corresponding to the protobufs released in 1.0.0, and possibly a series of
`v1beta1`, `v1beta2`, ... modules with earlier revisions of the protocol,
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ Changes with multiple classifications should be doubly included (eg. a bug fix
that is also a breaking change should be recorded under both).

Breaking changes are further subdivided according to the APIs/users they impact.
Any change that effects multiple APIs/users should be recorded multiply - for
Any change that affects multiple APIs/users should be recorded multiply - for
instance, a change to some core protocol data structure might need to be
reflected both as breaking the core protocol but also breaking any APIs where
core data structures are exposed.
Expand Down