Skip to content

docs: multiple textual corrections #3861

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+6 −6
Open

docs: multiple textual corrections #3861

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
260974e
Update README.md
CreeptoGengar Aug 31, 2025
a13b462
Update CONTRIBUTING.md
CreeptoGengar Aug 31, 2025
2a33d85
Update submitting.md
CreeptoGengar Aug 31, 2025
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
8 changes: 4 additions & 4 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ To ensure a smooth workflow for all contributors, a general procedure for contri
1. If you want to propose something new that requires specification or an additional design, or you would like to change a process, start with a [new discussion](https://github.com/cosmos/gaia/discussions/new/choose). With discussions, we can better handle the design process using discussion threads. A discussion usually leads to one or more issues.
2. If the issue you want addressed is a specific proposal or a bug, then open a [new issue](https://github.com/cosmos/gaia/issues/new/choose).
3. Review existing [issues](https://github.com/cosmos/gaia/issues) to find an issue you'd like to help with.
3. Participate in thoughtful discussion on that issue.
3. Participate in a thoughtful discussion on that issue.
4. If you would like to contribute:
1. Ensure that the proposal has been accepted.
2. Ensure that nobody else has already begun working on this issue. If they have,
Expand All @@ -91,7 +91,7 @@ To ensure a smooth workflow for all contributors, a general procedure for contri
See [development procedure guidelines](#development-procedure) below.

**Note:** For very small or trivial issues such as typos, you are not required to open an issue before submitting a PR.
For complex problems or features, please make sure to open an issue and provide context and problem description.
For complex problems or features, please make sure to open an issue and provide context and a problem description.
PRs opened before adequate design discussion has taken place in a GitHub issue have a high likelihood of being rejected without review.

## Project Board
Expand Down Expand Up @@ -220,7 +220,7 @@ items. In addition, use the following review explanations:

* `LGTM` without an explicit approval means that the changes look good, but you haven't thoroughly reviewed the reviewer checklist items.
* `Approval` means that you have completed some or all of the reviewer checklist items. If you only reviewed selected items, you must add your handle next to the items that you have reviewed. In addition, follow these guidelines:
* You must also think through anything which ought to be included but is not
* You must also think through anything that ought to be included but is not
* You must think through whether any added code could be partially combined (DRYed) with existing code
* You must think through any potential security issues or incentive-compatibility flaws introduced by the changes
* Naming must be consistent with conventions and the rest of the codebase
Expand Down Expand Up @@ -285,7 +285,7 @@ To generate the protobuf stubs, you can run `make proto-gen`.

User-facing repos should adhere to the trunk based development branching model: https://trunkbaseddevelopment.com. User branches should start with a user name, example: `{moniker}/{issue#}-branch-name`.

Gaia follows [semantic versioning](https://semver.org), but with the some deviations to account for state-machine and API breaking changes. See [RELEASE_PROCESS.md](./RELEASE_PROCESS.md) for details.
Gaia follows [semantic versioning](https://semver.org), but with some deviations to account for state-machine and API breaking changes. See [RELEASE_PROCESS.md](./RELEASE_PROCESS.md) for details.

### PR Targeting

Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ The Cosmos Hub is built using the [Cosmos SDK](https://github.com/cosmos/cosmos-

## Documentation

For the most up to date documentation please visit [hub.cosmos.network](https://hub.cosmos.network).
For the most up-to-date documentation please visit [hub.cosmos.network](https://hub.cosmos.network).

For an overview of the Interchain Stack (the Cosmos SDK, IBC, etc.), as well as examples and exercises to help developers get a quick start, please visit [tutorials.cosmos.network](https://tutorials.cosmos.network).

Expand Down
2 changes: 1 addition & 1 deletion docs/docs/governance/submitting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ Here is an example of the `draft_proposal.json` file:
],
"metadata": "ipfs://CID",
"deposit": "1000000uatom",
"title": "Updating the staking params (min_comission_rate)",
"title": "Updating the staking params (min_commission_rate)",
"summary": "This proposal will attempt to update the min_commission_rate staking parameter. During proposal creation and submission **all** proposal fields must be specified. Pay attention that you don't unintentionally specify different values for fields that you did not intend to change."
}
```
Expand Down