LaconicNetwork/cosmos-sdk
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

docs: fix broken links in documentation files (#25025)

Browse Source 
Co-authored-by: Alex | Interchain Labs <alex@interchainlabs.io>
This commit is contained in:
MozirDmitriy 2025-07-29 22:32:52 +03:00 committed by GitHub
parent e5a7389a98
commit d10a672a65
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
5 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/build/building-modules/11-structure.md vendored
View File

@ -82,7 +82,7 @@ x/{module_name}
* `abci.go`: The module's `BeginBlocker` and `EndBlocker` implementations (this file is only required if `BeginBlocker` and/or `EndBlocker` need to be defined).
* `autocli.go`: The module [autocli](https://docs.cosmos.network/main/core/autocli) options.
* `simulation/`: The module's [simulation](./14-simulator.md) package defines functions used by the blockchain simulator application (`simapp`).
* `README.md`: The module's specification documents outlining important concepts, state storage structure, and message and event type definitions. Learn more how to write module specs in the [spec guidelines](../spec/SPEC_MODULE.md).
* `README.md`: The module's specification documents outlining important concepts, state storage structure, and message and event type definitions. Learn more how to write module specs in the [spec guidelines](../../spec/SPEC_MODULE.md).
* The root directory includes type definitions for messages, events, and genesis state, including the type definitions generated by Protocol Buffers.
* `codec.go`: The module's registry methods for interface types.
* `errors.go`: The module's sentinel errors.

8
docs/docs/build/tooling/00-protobuf.md vendored
View File

@ -61,7 +61,7 @@ https://github.com/cosmos/cosmos-sdk/blob/main/proto/buf.gen.gogo.yaml#L1-L9
```
:::tip
Example of how to define `gen` files can be found [here](https://docs.buf.build/tour/generate-go-code)
Example of how to define `gen` files can be found [here](https://docs.buf.build/generate/overview)
:::
#### `buf.gen.pulsar.yaml`
@ -73,7 +73,7 @@ https://github.com/cosmos/cosmos-sdk/blob/main/proto/buf.gen.pulsar.yaml#L1-L18
```
:::tip
Example of how to define `gen` files can be found [here](https://docs.buf.build/tour/generate-go-code)
Example of how to define `gen` files can be found [here](https://docs.buf.build/generate/overview)
:::
#### `buf.gen.swagger.yaml`
@ -85,7 +85,7 @@ https://github.com/cosmos/cosmos-sdk/blob/main/proto/buf.gen.swagger.yaml#L1-L6
```
:::tip
Example of how to define `gen` files can be found [here](https://docs.buf.build/tour/generate-go-code)
Example of how to define `gen` files can be found [here](https://docs.buf.build/generate/overview)
:::
#### `buf.lock`
@ -98,7 +98,7 @@ https://github.com/cosmos/cosmos-sdk/blob/main/proto/buf.lock#L1-L16
#### `buf.yaml`
`buf.yaml` defines the [name of your package](https://github.com/cosmos/cosmos-sdk/blob/main/proto/buf.yaml#L3), which [breakage checker](https://docs.buf.build/tour/detect-breaking-changes) to use and how to [lint your protobuf files](https://buf.build/docs/tutorials/getting-started-with-buf-cli#lint-your-api).
`buf.yaml` defines the [name of your package](https://github.com/cosmos/cosmos-sdk/blob/main/proto/buf.yaml#L3), which [breakage checker](https://docs.buf.build/breaking/overview) to use and how to [lint your protobuf files](https://buf.build/docs/tutorials/getting-started-with-buf-cli#lint-your-api).
```go reference
https://github.com/cosmos/cosmos-sdk/blob/main/proto/buf.yaml#L1-L24

4
docs/docs/build/tooling/README.md vendored
View File

@ -9,8 +9,8 @@ This includes tools for development, operating a node, and ease of use of a Cosm
## CLI Tools
* [Cosmovisor](./01-cosmovisor.md)
* [Confix](./02-confix.md)
* [Cosmovisor](../../../tools/cosmovisor/README.md)
* [Confix](../../../tools/confix/README.md)
## Other Tools

2
docs/docs/learn/beginner/01-tx-lifecycle.md
View File

@ -230,7 +230,7 @@ to during consensus. Under the hood, transaction execution is almost identical t
Instead of using their `checkState`, full-nodes use `finalizeblock`:
* **Decoding:** Since `FinalizeBlock` is an ABCI call, `Tx` is received in the encoded `[]byte` form.
Nodes first unmarshal the transaction, using the [`TxConfig`](./app-anatomy#register-codec) defined in the app, then call `runTx` in `execModeFinalize`, which is very similar to `CheckTx` but also executes and writes state changes.
Nodes first unmarshal the transaction, using the [`TxConfig`](./00-app-anatomy.md#register-codec) defined in the app, then call `runTx` in `execModeFinalize`, which is very similar to `CheckTx` but also executes and writes state changes.
* **Checks and `AnteHandler`:** Full-nodes call `validateBasicMsgs` and `AnteHandler` again. This second check
happens because they may not have seen the same transactions during the addition to Mempool stage

2
docs/docs/user/run-node/00-keyring.md
View File

@ -92,7 +92,7 @@ one you may want to use specifically to encrypt the password store.
The `kwallet` backend uses `KDE Wallet Manager`, which comes installed by default on the
GNU/Linux distributions that ships KDE as default desktop environment. Please refer to
[KWallet Handbook](https://docs.kde.org/stable5/en/kdeutils/kwallet5/index.html) for more
[KWallet API documentation](https://api.kde.org/frameworks/kwallet/html/index.html) for more
information.
### The `keyctl` backend