From 260974eae1cf21cd65bd926c9c0b6c1db2655a25 Mon Sep 17 00:00:00 2001 From: Gengar Date: Sun, 31 Aug 2025 13:00:04 +0300 Subject: [PATCH 1/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 09594100fe..9937b2c1fe 100644 --- a/README.md +++ b/README.md @@ -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). From a13b4625c41a7b41e0045de43dfa45f4aaca9c91 Mon Sep 17 00:00:00 2001 From: Gengar Date: Sun, 31 Aug 2025 13:02:23 +0300 Subject: [PATCH 2/3] Update CONTRIBUTING.md --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 90323e58ad..765f74fbb0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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, @@ -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 @@ -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 @@ -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 From 2a33d852c7bfe296603563fb9781896900004af9 Mon Sep 17 00:00:00 2001 From: Gengar Date: Sun, 31 Aug 2025 13:15:59 +0300 Subject: [PATCH 3/3] Update submitting.md --- docs/docs/governance/submitting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/governance/submitting.md b/docs/docs/governance/submitting.md index 81a1b28ecf..e347be03e8 100644 --- a/docs/docs/governance/submitting.md +++ b/docs/docs/governance/submitting.md @@ -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." } ```