You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: RELEASE_PROCESS.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -242,7 +242,7 @@ The intention of the Stable Release Policy is to ensure that all major release s
242
242
are maintained with the following categories of fixes:
243
243
244
244
- Tooling improvements (including code formatting, linting, static analysis and updates to testing frameworks)
245
-
- Performance enhancements for running archival and synching nodes
245
+
- Performance enhancements for running archival and syncing nodes
246
246
- Test and benchmarking suites, ensuring that fixes are sound and there are no performance regressions
247
247
- Library updates including point releases for core libraries such as IBC-Go, Cosmos SDK, Tendermint and other dependencies
248
248
- General maintenance improvements, that are deemed necessary by the stewarding team, that help align different releases and reduce the workload on the stewarding team
Copy file name to clipboardexpand all lines: docs/docs/architecture/adr/adr-003-ica-controller.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Enabling the ICA Controller module on the Hub would support various use cases. O
18
18
19
19
## Decision
20
20
21
-
The ICA Controller module will be included in the application, so the Hub will have both ICA Host and Controller modules. The implementation will use the Controller module's built-in authentication mechanism, since we don't have a need for custom authentication logic. According to this, users will directly use `MsgRegisterInterchainAccount` and `MsgSendTx` messages defined by the Controller module. The possibility provided by the Controller module to define underlaying application to have custom processing of IBC messages exchanged by the Controller module (e.g. `OnChanOpenInit`, `OnAcknowledgementPacket`, etc.) will not be used, since there is currently no need for this.
21
+
The ICA Controller module will be included in the application, so the Hub will have both ICA Host and Controller modules. The implementation will use the Controller module's built-in authentication mechanism, since we don't have a need for custom authentication logic. According to this, users will directly use `MsgRegisterInterchainAccount` and `MsgSendTx` messages defined by the Controller module. The possibility provided by the Controller module to define underlying application to have custom processing of IBC messages exchanged by the Controller module (e.g. `OnChanOpenInit`, `OnAcknowledgementPacket`, etc.) will not be used, since there is currently no need for this.
Copy file name to clipboardexpand all lines: docs/docs/governance/best-practices.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ It will be important to balance two things: being detailed and being concise. Yo
77
77
78
78
Each major proposal type has a rough template available on the forum: [Text](https://forum.cosmos.network/t/about-the-signaling-text-category/5947), [community pool spend](https://forum.cosmos.network/t/about-the-community-spend-category/5949), [parameter change](https://forum.cosmos.network/t/about-the-parameter-change-category/5950), [software upgrade](https://forum.cosmos.network/t/about-the-software-upgrade-category/5951).
79
79
80
-
Each proposal should contain a summmary with key details about what the proposal hopes to change. If you were viewing only the summary with no other context, it should be a good start to being able to make a decision.
80
+
Each proposal should contain a summary with key details about what the proposal hopes to change. If you were viewing only the summary with no other context, it should be a good start to being able to make a decision.
81
81
82
82
Assume that many people will stop reading at this point. However it is important to provide in-depth information. The on-chain proposal text should also include a link to an un-editable version of the text, such as an IPFS pin, and a link to where discussion about the idea is happening.
0 commit comments