mirror of
https://github.com/tendermint/tendermint.git
synced 2026-09-20 23:14:37 +00:00
Update to markdown links (#9384)
* first correction of markdown links * Review updates
This commit is contained in:
+2
-2
@@ -9,10 +9,10 @@ The `.proto` files within this section are core to the protocol and updates must
|
||||
### Steps
|
||||
|
||||
1. Make an issue with the proposed change.
|
||||
- Within in the issue members from both the Tendermint-go and Tendermint-rs team will leave comments. If there is not consensus on the change an [RFC](../rfc/README.md) may be requested.
|
||||
- Within in the issue members from both the Tendermint-go and Tendermint-rs team will leave comments. If there is not consensus on the change an [RFC](../docs/rfc/README.md) may be requested.
|
||||
1a. Submission of an RFC as a pull request should be made to facilitate further discussion.
|
||||
1b. Merge the RFC.
|
||||
2. Make the necessary changes to the `.proto` file(s), [core data structures](../spec/core/data_structures.md) and/or [ABCI protocol](../spec/abci/apps.md).
|
||||
2. Make the necessary changes to the `.proto` file(s), [core data structures](../spec/core/data_structures.md) and/or [ABCI protocol](../spec/abci).
|
||||
3. Open issues within Tendermint-go and Tendermint-rs repos. This is used to notify the teams that a change occurred in the spec.
|
||||
1. Tag the issue with a spec version label. This will notify the team the changed has been made on master but has not entered a release.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user