chore: Sync docs from cosmos-sdk/docs

Author: tac0turtle

docs/build/modules/README.md

@@ -14,16 +14,15 @@ proof-of-stake capabilities and governance.
 
 * [Auth](./auth/README.md) - Authentication of accounts and transactions for Cosmos SDK applications.
 * [Bank](./bank/README.md) - Token transfer functionalities.
-* [Circuit](./circuit/README.md) - Circuit breaker module for pausing messages.
 * [Consensus](./consensus/README.md) - Consensus module for modifying CometBFT's ABCI consensus params.
 * [Distribution](./distribution/README.md) - Fee distribution, and staking token provision distribution.
-* [Evidence](./evidence/README.md) - Evidence handling for double signing, misbehaviour, etc.
 * [Governance](./gov/README.md) - On-chain proposals and voting.
 * [Genutil](./genutil/README.md) - Genesis utilities for the Cosmos SDK.
 * [Mint](./mint/README.md) - Creation of new units of staking token.
 * [Slashing](./slashing/README.md) - Validator punishment mechanisms.
 * [Staking](./staking/README.md) - Proof-of-Stake layer for public blockchains.
 * [Upgrade](./upgrade/README.md) - Software upgrades handling and coordination.
+* [Evidence](./evidence/README.md) - Evidence handling for double signing, misbehaviour, etc.
 
 ## Supplementary Modules
 
@@ -38,13 +37,13 @@ capabilities of your blockchain or further specialize it.
 
 ## Deprecated Modules
 
-The following modules are deprecated.  They will no longer be maintained and eventually will be removed
-in an upcoming release of the Cosmos SDK per our [release process](https://github.com/cosmos/cosmos-sdk/blob/main/RELEASE_PROCESS.md).
+The following modules are deprecated.  They will no longer be maintained actively.
 
-* [Crisis](./crisis/README.md) - _Deprecated_ halting the blockchain under certain circumstances (e.g. if an invariant is broken).
+* [Crisis](../contrib/x/crisis/README.md) - _Deprecated_ halting the blockchain under certain circumstances (e.g. if an invariant is broken).
 * [Params](./params/README.md) - _Deprecated_ Globally available parameter store.
-* [NFT](./nft/README.md) - _Deprecated_ NFT module implemented based on [ADR43](https://docs.cosmos.network/main/build/architecture/adr-043-nft-module).  This module will be moved to the `cosmos-sdk-legacy` repo for use.
-* [Group](./group/README.md) - _Deprecated_ Allows for the creation and management of on-chain multisig accounts.  This module will be moved to the `cosmos-sdk-legacy` repo for legacy use.
+* [NFT](../contrib/x/nft/README.md) - _Deprecated_ NFT module implemented based on [ADR43](https://docs.cosmos.network/main/build/architecture/adr-043-nft-module).
+* [Group](../contrib/x/group/README.md) - _Deprecated_ Allows for the creation and management of on-chain multisig accounts.  
+* [Circuit](../contrib/x/circuit/README.md) _Deprecated_ - Circuit breaker module for pausing messages.
 
 To learn more about the process of building modules, visit the [building modules reference documentation](https://docs.cosmos.network/main/building-modules/intro).
 

docs/build/modules/circuit/README.md

@@ -21,7 +21,7 @@ https://github.com/cosmos/cosmos-sdk/blob/v0.50.1/baseapp/msg_service_router.go#
 ``` 
 
 :::note
-The `CircuitBreakerDecorator` works for most use cases, but [does not check the inner messages of a transaction](https://docs.cosmos.network/main/learn/beginner/tx-lifecycle#antehandler). This means some transactions (such as `x/authz` transactions or some `x/gov` transactions) may pass the ante handler. **This does not affect the circuit breaker** as the message router check will still fail the transaction.
+The `CircuitBreakerDecorator` works for most use cases, but [does not check the inner messages of a transaction](https://docs.cosmos.network/main/learn/beginner/tx-lifecycle#antehandler). This some transactions (such as `x/authz` transactions or some `x/gov` transactions) may pass the ante handler. **This does not affect the circuit breaker** as the message router check will still fail the transaction.
 This tradeoff is to avoid introducing more dependencies in the `x/circuit` module. Chains can re-define the `CircuitBreakerDecorator` to check for inner messages if they wish to do so.
 :::
 
@@ -91,7 +91,7 @@ Reset is called by an authorized account to enable execution for a specific msgU
 
 ```protobuf
   // ResetCircuitBreaker resumes processing of Msg's in the state machine that
-  // have been paused using TripCircuitBreaker.
+  // have been been paused using TripCircuitBreaker.
   rpc ResetCircuitBreaker(MsgResetCircuitBreaker) returns (MsgResetCircuitBreakerResponse);
 ```
 
@@ -168,92 +168,3 @@ The circuit module emits the following events:
 * `DisableListPrefix` -  `0x02`
 
 ## Client - list and describe CLI commands and gRPC and REST endpoints
-
-## Examples: Using Circuit Breaker CLI Commands
-
-This section provides practical examples for using the Circuit Breaker module through the command-line interface (CLI). These examples demonstrate how to authorize accounts, disable (trip) specific message types, and re-enable (reset) them when needed.
-
-### Querying Circuit Breaker Permissions
-
-Check an account's current circuit breaker permissions:
-
-```bash
-# Query permissions for a specific account
-<appd> query circuit account-permissions <account_address>
-
-# Example:
-simd query circuit account-permissions cosmos1...
-```
-
-Check which message types are currently disabled:
-
-```bash
-# Query all disabled message types
-<appd> query circuit disabled-list
-
-# Example:
-simd query circuit disabled-list
-```
-
-### Authorizing an Account as Circuit Breaker
-
-Only a super-admin or the module authority (typically the governance module account) can grant circuit breaker permissions to other accounts:
-
-```bash
-# Grant LEVEL_ALL_MSGS permission (can disable any message type)
-<appd> tx circuit authorize <grantee_address> --level=ALL_MSGS --from=<super_admin_key> --gas=auto --gas-adjustment=1.5
-
-# Grant LEVEL_SOME_MSGS permission (can only disable specific message types)
-<appd> tx circuit authorize <grantee_address> --level=SOME_MSGS --limit-type-urls="/cosmos.bank.v1beta1.MsgSend,/cosmos.staking.v1beta1.MsgDelegate" --from=<super_admin_key> --gas=auto --gas-adjustment=1.5
-
-# Grant LEVEL_SUPER_ADMIN permission (can disable messages and authorize other accounts)
-<appd> tx circuit authorize <grantee_address> --level=SUPER_ADMIN --from=<super_admin_key> --gas=auto --gas-adjustment=1.5
-```
-
-### Disabling Message Processing (Trip)
-
-Disable specific message types to prevent their execution (requires authorization):
-
-```bash
-# Disable a single message type
-<appd> tx circuit trip --type-urls="/cosmos.bank.v1beta1.MsgSend" --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-
-# Disable multiple message types
-<appd> tx circuit trip --type-urls="/cosmos.bank.v1beta1.MsgSend,/cosmos.staking.v1beta1.MsgDelegate" --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-
-# Disable all message types (emergency measure)
-<appd> tx circuit trip --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-```
-
-### Re-enabling Message Processing (Reset)
-
-Re-enable previously disabled message types (requires authorization):
-
-```bash
-# Re-enable a single message type
-<appd> tx circuit reset --type-urls="/cosmos.bank.v1beta1.MsgSend" --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-
-# Re-enable multiple message types
-<appd> tx circuit reset --type-urls="/cosmos.bank.v1beta1.MsgSend,/cosmos.staking.v1beta1.MsgDelegate" --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-
-# Re-enable all disabled message types
-<appd> tx circuit reset --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-```
-
-### Usage in Emergency Scenarios
-
-In case of a critical vulnerability in a specific message type:
-
-1. Quickly disable the vulnerable message type:
-
-   ```bash
-   <appd> tx circuit trip --type-urls="/cosmos.vulnerable.v1beta1.MsgVulnerable" --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-   ```
-
-2. After a fix is deployed, re-enable the message type:
-
-   ```bash
-   <appd> tx circuit reset --type-urls="/cosmos.vulnerable.v1beta1.MsgVulnerable" --from=<authorized_key> --gas=auto --gas-adjustment=1.5
-   ```
-
-This allows chains to surgically disable problematic functionality without halting the entire chain, providing time for developers to implement and deploy fixes.

docs/build/modules/crisis/README.md

@@ -4,8 +4,6 @@ sidebar_position: 1
 
 # `x/crisis`
 
-NOTE: `x/crisis` is deprecated as of Cosmos SDK v0.53 and will be removed in the next release.
-
 ## Overview
 
 The crisis module halts the blockchain under the circumstance that a blockchain
@@ -66,7 +64,7 @@ The crisis module emits the following events:
 
 ### Handlers
 
-#### MsgVerifyInvariant
+#### MsgVerifyInvariance
 
 | Type      | Attribute Key | Attribute Value  |
 |-----------|---------------|------------------|

docs/build/modules/gov/README.md

@@ -2532,7 +2532,7 @@ The gov module has two locations for metadata where users can provide further co
 
 ### Proposal
 
-Location: off-chain as json object stored on IPFS (mirrors [group proposal](../group/README.md#metadata))
+Location: off-chain as json object stored on IPFS (mirrors [group proposal](../../contrib/x/group/README.md#metadata))
 
 ```json
 {
@@ -2552,7 +2552,7 @@ In v0.46, the `authors` field is a comma-separated string. Frontends are encoura
 
 ### Vote
 
-Location: on-chain as json within 255 character limit (mirrors [group vote](../group/README.md#metadata))
+Location: on-chain as json within 255 character limit (mirrors [group vote](../../contrib/x/group/README.md#metadata))
 
 ```json
 {

docs/build/modules/group/README.md

@@ -4,8 +4,6 @@ sidebar_position: 1
 
 # `x/group`
 
-⚠️ **DEPRECATED**: This package is deprecated and will be removed in the next major release.  The `x/group` module will be moved to a separate repo `github.com/cosmos/cosmos-sdk-legacy`.
-
 ## Abstract
 
 The following documents specify the group module.
@@ -87,7 +85,7 @@ A decision policy is the mechanism by which members of a group can vote on
 proposals, as well as the rules that dictate whether a proposal should pass
 or not based on its tally outcome.
 
-All decision policies generally would have a minimum execution period and a
+All decision policies generally would have a mininum execution period and a
 maximum voting window. The minimum execution period is the minimum amount of time
 that must pass after submission in order for a proposal to potentially be executed, and it may
 be set to 0. The maximum voting window is the maximum time after submission that a proposal may
@@ -103,7 +101,7 @@ custom decision policies, as long as they adhere to the `DecisionPolicy`
 interface:
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/x/group/types.go#L27-L45
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/x/group/types.go#L27-L45
 ```
 
 #### Threshold decision policy
@@ -212,7 +210,7 @@ Proposals and votes are automatically pruned to avoid state bloat.
 Votes are pruned:
 
 * either after a successful tally, i.e. a tally whose result passes the decision
-  policy's rules, which can be triggered by a `Msg/Exec` or a
+  policy's rules, which can be trigged by a `Msg/Exec` or a
   `Msg/{SubmitProposal,Vote}` with the `Exec` field set,
 * or on `EndBlock` right after the proposal's voting period end. This applies to proposals with status `aborted` or `withdrawn` too.
 
@@ -339,7 +337,7 @@ The metadata has a maximum length that is chosen by the app developer, and
 passed into the group keeper as a config.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L67-L80
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L67-L80
 ```
 
 It's expected to fail if
@@ -352,7 +350,7 @@ It's expected to fail if
 Group members can be updated with the `UpdateGroupMembers`.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L88-L102
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L88-L102
 ```
 
 In the list of `MemberUpdates`, an existing member can be removed by setting its weight to 0.
@@ -367,7 +365,7 @@ It's expected to fail if:
 The `UpdateGroupAdmin` can be used to update a group admin.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L107-L120
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L107-L120
 ```
 
 It's expected to fail if the signer is not the admin of the group.
@@ -377,7 +375,7 @@ It's expected to fail if the signer is not the admin of the group.
 The `UpdateGroupMetadata` can be used to update a group metadata.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L125-L138
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L125-L138
 ```
 
 It's expected to fail if:
@@ -390,7 +388,7 @@ It's expected to fail if:
 A new group policy can be created with the `MsgCreateGroupPolicy`, which has an admin address, a group id, a decision policy and some optional metadata.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L147-L165
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L147-L165
 ```
 
 It's expected to fail if:
@@ -404,7 +402,7 @@ It's expected to fail if:
 A new group with policy can be created with the `MsgCreateGroupWithPolicy`, which has an admin address, a list of members, a decision policy, a `group_policy_as_admin` field to optionally set group and group policy admin with group policy address and some optional metadata for group and group policy.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L191-L215
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L191-L215
 ```
 
 It's expected to fail for the same reasons as `Msg/CreateGroup` and `Msg/CreateGroupPolicy`.
@@ -414,7 +412,7 @@ It's expected to fail for the same reasons as `Msg/CreateGroup` and `Msg/CreateG
 The `UpdateGroupPolicyAdmin` can be used to update a group policy admin.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L173-L186
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L173-L186
 ```
 
 It's expected to fail if the signer is not the admin of the group policy.
@@ -424,7 +422,7 @@ It's expected to fail if the signer is not the admin of the group policy.
 The `UpdateGroupPolicyDecisionPolicy` can be used to update a decision policy.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L226-L241
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L226-L241
 ```
 
 It's expected to fail if:
@@ -437,7 +435,7 @@ It's expected to fail if:
 The `UpdateGroupPolicyMetadata` can be used to update a group policy metadata.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L246-L259
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L246-L259
 ```
 
 It's expected to fail if:
@@ -451,7 +449,7 @@ A new proposal can be created with the `MsgSubmitProposal`, which has a group po
 An optional `Exec` value can be provided to try to execute the proposal immediately after proposal creation. Proposers signatures are considered as yes votes in this case.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L281-L315
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L281-L315
 ```
 
 It's expected to fail if:
@@ -464,7 +462,7 @@ It's expected to fail if:
 A proposal can be withdrawn using `MsgWithdrawProposal` which has an `address` (can be either a proposer or the group policy admin) and a `proposal_id` (which has to be withdrawn).
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L323-L333
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L323-L333
 ```
 
 It's expected to fail if:
@@ -478,7 +476,7 @@ A new vote can be created with the `MsgVote`, given a proposal id, a voter addre
 An optional `Exec` value can be provided to try to execute the proposal immediately after voting.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L338-L358
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L338-L358
 ```
 
 It's expected to fail if:
@@ -491,7 +489,7 @@ It's expected to fail if:
 A proposal can be executed with the `MsgExec`.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L363-L373
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L363-L373
 ```
 
 The messages that are part of this proposal won't be executed if:
@@ -504,7 +502,7 @@ The messages that are part of this proposal won't be executed if:
 The `MsgLeaveGroup` allows group member to leave a group.
 
 ```go reference
-https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/proto/cosmos/group/v1/tx.proto#L381-L391
+https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/group/v1/tx.proto#L381-L391
 ```
 
 It's expected to fail if:

docs/build/modules/nft/README.md

@@ -4,8 +4,6 @@ sidebar_position: 1
 
 # `x/nft`
 
-⚠️ **DEPRECATED**: This package is deprecated and will be removed in the next major release.  The `x/nft` module will be moved to a separate repo `github.com/cosmos/cosmos-sdk-legacy`.
-
 ## Contents
 
 ## Abstract