chore: update documentation from cosmos-sdk/docs (#285)

chore: Sync docs from cosmos-sdk/docs

Co-authored-by: tac0turtle <[email protected]>

Author: github-actions[bot]

docs/build/abci/01-prepare-proposal.md

@@ -33,7 +33,7 @@ https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/baseapp/abci_utils.go
 ```
 
 This default implementation can be overridden by the application developer in
-favor of a custom implementation in [`app_di.go`](../building-apps/01-app-go-v2.md):
+favor of a custom implementation in [`app_di.go`](../building-apps/01-app-go-di.md):
 
 ```go
 prepareOpt := func(app *baseapp.BaseApp) {

docs/build/abci/02-process-proposal.md

@@ -18,7 +18,7 @@ https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/baseapp/abci_utils.go#L21
 ```
 
 Like `PrepareProposal`, this implementation is the default and can be modified by
-the application developer in [`app_di.go`](../building-apps/01-app-go-v2.md). If you decide to implement
+the application developer in [`app_di.go`](../building-apps/01-app-go-di.md). If you decide to implement
 your own `ProcessProposal` handler, you must ensure that the transactions
 provided in the proposal DO NOT exceed the maximum block gas and `maxtxbytes` (if set).
 

docs/build/building-apps/00-runtime.md

@@ -20,24 +20,23 @@ The runtime App struct contains several key components:
 ```go
 type App struct {
     *baseapp.BaseApp
-    ModuleManager      *module.Manager
-    UnorderedTxManager *unorderedtx.Manager
-    configurator      module.Configurator
+    ModuleManager    *module.Manager
+    configurator     module.Configurator
     config           *runtimev1alpha1.Module
     storeKeys        []storetypes.StoreKey
     // ... other fields
 }
 ```
 
-It is the struct that any Cosmos SDK application should embed to leverage the runtime module.
+Cosmos SDK applications should embed the `*runtime.App` struct to leverage the runtime module.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_di.go#L61-L62
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_di.go#L60-L61
 ```
 
 ### Configuration
 
-The runtime module is configured using App Wiring. The main configuration object is the [`Module` message](https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/proto/cosmos/app/runtime/v1alpha1/module.proto), which supports the following key settings:
+The runtime module is configured using App Wiring. The main configuration object is the [`Module` message](https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/proto/cosmos/app/runtime/v1alpha1/module.proto), which supports the following key settings:
 
 * `app_name`: The name of the application
 * `begin_blockers`: List of module names to call during BeginBlock
@@ -59,7 +58,7 @@ However it provides a flexible store key configuration through:
 Example configuration:
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/v2/app_config.go#L138-L147
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_config.go#L133-L138
 ```
 
 ## Key Features
@@ -68,7 +67,7 @@ https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/v2/app_config.go
 
 The runtime module integrates with the `BaseApp` and other core SDK components to provide a seamless experience for developers.
 
-The developer only needs to embed the `App` struct in their application to leverage the runtime module.
+The developer only needs to embed the `runtime.App` struct in their application to leverage the runtime module.
 The configuration of the module manager and other core components is handled internally via the [`AppBuilder`](#4-application-building).
 
 ### 2. Module Registration
@@ -77,7 +76,7 @@ Runtime has built-in support for [`depinject`-enabled modules](../building-modul
 Such modules can be registered through the configuration file (often named `app_config.go`), with no additional code required.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_config.go#L210-L215
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_config.go#L210-L216
 ```
 
 Additionally, the runtime package facilitates manual module registration through the `RegisterModules` method. This is the primary integration point for modules not registered via configuration.
@@ -94,30 +93,30 @@ The SDK recommends using the declarative approach with `depinject` for module re
 
 ### 3. Service Registration
 
-Runtime registers all [core services](../../learn/advanced/02-core.md) required by modules.
-These services include the `store`, the `event manager`, the `context`, and the `logger`.
-As runtime is doing the wiring of modules, it can ensure that the services are scoped to their respective modules.
+Runtime registers all [core services](https://pkg.go.dev/cosmossdk.io/core) required by modules.
+These services include `store`, `event manager`, `context`, and `logger`.
+Runtime ensures that services are scoped to their respective modules during the wiring process.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/runtime/module.go#L250-L279
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/runtime/module.go#L201-L235
 ```
 
-Additionally, runtime provides automatic registration of other essential (f.e gRPC routes) services, available to the App:
+Additionally, runtime provides automatic registration of other essential (i.e., gRPC routes) services available to the App:
 
 * AutoCLI Query Service
 * Reflection Service
 * Custom module services
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/runtime/builder.go#L74-L77
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/runtime/builder.go#L52-L54
 ```
 
 ### 4. Application Building
 
 The `AppBuilder` type provides a structured way to build applications:
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/runtime/builder.go#L22-L29
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/runtime/builder.go#L14-L19
 ```
 
 Key building steps:
@@ -131,14 +130,14 @@ Key building steps:
 An application only needs to call `AppBuilder.Build` to create a fully configured application (`runtime.App`).
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/runtime/builder.go#L36-L80
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/runtime/builder.go#L26-L57
 ```
 
-More information on building applications can be found in the [next section](./01-app-go-di.md).
+More information on building applications can be found in the [next section](./02-app-building.md).
 
 ## Best Practices
 
-1. **Module Order**: Carefully consider the order of modules in begin_blockers and end_blockers
+1. **Module Order**: Carefully consider the order of modules in begin_blockers, end_blockers, and pre_blockers.
 2. **Store Keys**: Use override_store_keys only when necessary to maintain clarity
 3. **Genesis Order**: Maintain correct initialization order in init_genesis
 4. **Migration Management**: Use order_migrations to control upgrade paths

docs/build/building-apps/01-app-go-di.md

@@ -29,39 +29,39 @@ The `app_config.go` file is the single place to configure all modules parameters
 1. Create the `AppConfig` variable:
 
     ```go reference
-    https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_di.go#L93-L99
+    https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_config.go#L289-L303
     ```
 
-    Where the `appConfig`, combine the [runtime](./00-runtime.md) and the modules configuration.
+    Where the `appConfig` combines the [runtime](./00-runtime.md) configuration and the (extra) modules configuration.
 
     ```go reference
-    https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_config.go#L107-L111
+    https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_di.go#L113-L161
     ```
 
 2. Configure the `runtime` module:
 
-    In this configuration, the order at which the modules are defined is important.
+    In this configuration, the order at which the modules are defined in PreBlockers, BeginBlocks, and EndBlockers is important.
     They are named in the order they should be executed by the module manager.
 
     ```go reference
-    https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_config.go#L110-L187
+    https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_config.go#L103-L188
     ```
 
 3. Wire the other modules:
 
     Next to runtime, the other (depinject-enabled) modules are wired in the `AppConfig`:
 
     ```go reference
-    https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_config.go#L196-L215
+    https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_config.go#L103-L286
     ```
 
     Note: the `tx` isn't a module, but a configuration. It should be wired in the `AppConfig` as well.
 
     ```go reference
-    https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_config.go#L188-L195
+    https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_config.go#L222-L227
     ```
 
-See the complete `app_config.go` file for `SimApp` [here](https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_config.go).
+See the complete `app_config.go` file for `SimApp` [here](https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_config.go).
 
 ### Alternative formats
 
@@ -100,18 +100,18 @@ modules:
       "@type": cosmos.staking.module.v1.Module
   - name: tx
     config:
-      "@type": cosmos.tx.config.v1.Config
+      "@type": cosmos.tx.module.v1.Module
 ```
 
-A more complete example of `app.yaml` can be found [here](https://github.com/cosmosregistry/chain-minimal/blob/mini-v050.2/app/app.yaml).
+A more complete example of `app.yaml` can be found [here](https://github.com/cosmos/cosmos-sdk/blob/release/v0.53.x/simapp/example_app.yaml).
 
 ## `app_di.go`
 
-`app_di.go` is the place where `SimApp` is constructed. `depinject.Inject` facilitates that by automatically wiring the app modules and keepers, provided an application configuration `AppConfig` is provided. `SimApp` is constructed, when calling the injected `*runtime.AppBuilder`, with `appBuilder.Build(...)`.    
+`app_di.go` is the place where `SimApp` is constructed. `depinject.Inject` automatically wires the app modules and keepers when provided with an application configuration (`AppConfig`). `SimApp` is constructed upon calling the injected `*runtime.AppBuilder` with `appBuilder.Build(...)`.    
 In short `depinject` and the [`runtime` package](./00-runtime.md) abstract the wiring of the app, and the `AppBuilder` is the place where the app is constructed. [`runtime`](./00-runtime.md) takes care of registering the codecs, KV store, subspaces and instantiating `baseapp`.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_di.go#L101-L290
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_di.go#L100-L270
 ```
 
 :::warning
@@ -121,16 +121,16 @@ When using `depinject.Inject`, the injected types must be pointers.
 ### Advanced Configuration
 
 In advanced cases, it is possible to inject extra (module) configuration in a way that is not (yet) supported by `AppConfig`.  
-In this case, use `depinject.Configs` for combining the extra configuration and `AppConfig`, and `depinject.Supply` to providing that extra configuration.
-More information on how work `depinject.Configs` and `depinject.Supply` can be found in the [`depinject` documentation](https://pkg.go.dev/cosmossdk.io/depinject).
+In this case, use `depinject.Configs` for combining the extra configuration, and `AppConfig` and `depinject.Supply` for providing the extra configuration.
+More information on how `depinject.Configs` and `depinject.Supply` function can be found in the [`depinject` documentation](https://pkg.go.dev/cosmossdk.io/depinject).
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app_di.go#L117-L161
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_di.go#L114-L162
 ```
 
 ### Registering non app wiring modules
 
-It is possible to combine app wiring / depinject enabled modules with non app wiring modules.
+It is possible to combine app wiring / depinject enabled modules with non-app wiring modules.
 To do so, use the `app.RegisterModules` method to register the modules on your app, as well as `app.RegisterStores` for registering the extra stores needed.
 
 ```go
@@ -149,7 +149,7 @@ if err := app.RegisterModules(&exampleAppModule); err != nil {
 ```
 
 :::warning
-When using AutoCLI and combining app wiring and non app wiring modules. The AutoCLI options should be manually constructed instead of injected.
+When using AutoCLI and combining app wiring and non-app wiring modules. The AutoCLI options should be manually constructed instead of injected.
 Otherwise it will miss the non depinject modules and not register their CLI.
 :::
 
@@ -160,5 +160,5 @@ Note that in the complete `SimApp` `app_di.go` file, testing utilities are also
 :::
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.2/simapp/app.go
+https://github.com/cosmos/cosmos-sdk/blob/v0.53.0-rc.2/simapp/app_di.go
 ```

docs/build/building-apps/02-app-mempool.md

@@ -29,7 +29,7 @@ Namely, the SDK provides the following mempools:
 * [Sender Nonce Mempool](#sender-nonce-mempool)
 * [Priority Nonce Mempool](#priority-nonce-mempool)
 
-The default SDK is a [No-op Mempool](#no-op-mempool), but it can be replaced by the application developer in [`app.go`](./01-app-go-v2.md):
+By default, the SDK uses the [No-op Mempool](#no-op-mempool), but it can be replaced by the application developer in [`app.go`](./01-app-go-di.md):
 
 ```go
 nonceMempool := mempool.NewSenderNonceMempool()

docs/build/building-modules/15-depinject.md

@@ -121,4 +121,4 @@ The module is now ready to be used with `depinject` by a chain developer.
 
 ## Integrate in an application
 
-The App Wiring is done in `app_config.go` / `app.yaml` and `app_v2.go` and is explained in detail in the [overview of `app_v2.go`](../building-apps/01-app-go-v2.md).
+The App Wiring is done in `app_config.go` / `app.yaml` and `app_v2.go` and is explained in detail in the [overview of `app_v2.go`](../building-apps/01-app-go-di.md).

docs/build/modules/authz/README.md

@@ -82,7 +82,7 @@ https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/x/bank/types/send_authoriz
 
 #### StakeAuthorization
 
-`StakeAuthorization` implements the `Authorization` interface for messages in the [staking module](https://docs.cosmos.network/v0.50/build/modules/staking). It takes an `AuthorizationType` to specify whether you want to authorise delegating, undelegating or redelegating (i.e. these have to be authorised separately). It also takes an optional `MaxTokens` that keeps track of a limit to the amount of tokens that can be delegated/undelegated/redelegated. If left empty, the amount is unlimited. Additionally, this Msg takes an `AllowList` or a `DenyList`, which allows you to select which validators you allow or deny grantees to stake with.
+`StakeAuthorization` implements the `Authorization` interface for messages in the [staking module](https://docs.cosmos.network/v0.53/build/modules/staking). It takes an `AuthorizationType` to specify whether you want to authorise delegating, undelegating or redelegating (i.e. these have to be authorised separately). It also takes an optional `MaxTokens` that keeps track of a limit to the amount of tokens that can be delegated/undelegated/redelegated. If left empty, the amount is unlimited. Additionally, this Msg takes an `AllowList` or a `DenyList`, which allows you to select which validators you allow or deny grantees to stake with.
 
 ```protobuf reference
 https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/staking/v1beta1/authz.proto#L11-L35