From 058fd33a74324351606b0a45de9bbf088d716788 Mon Sep 17 00:00:00 2001 From: Carlos Rodriguez Date: Thu, 28 Sep 2023 21:20:50 +0200 Subject: [PATCH] docs: fix links (#4787) --- docs/docs/02-apps/02-interchain-accounts/05-messages.md | 2 +- docs/docs/05-migrations/04-v2-to-v3.md | 2 +- .../02-apps/02-interchain-accounts/06-transactions.md | 2 +- docs/versioned_docs/version-v4.4.x/04-migrations/04-v2-to-v3.md | 2 +- .../02-apps/02-interchain-accounts/06-transactions.md | 2 +- docs/versioned_docs/version-v5.3.x/04-migrations/04-v2-to-v3.md | 2 +- .../02-apps/02-interchain-accounts/05-messages.md | 2 +- docs/versioned_docs/version-v6.2.x/04-migrations/04-v2-to-v3.md | 2 +- .../02-apps/02-interchain-accounts/05-messages.md | 2 +- docs/versioned_docs/version-v7.3.x/05-migrations/04-v2-to-v3.md | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/docs/02-apps/02-interchain-accounts/05-messages.md b/docs/docs/02-apps/02-interchain-accounts/05-messages.md index bcc37319e83..119c740e03e 100644 --- a/docs/docs/02-apps/02-interchain-accounts/05-messages.md +++ b/docs/docs/02-apps/02-interchain-accounts/05-messages.md @@ -73,6 +73,6 @@ The packet `Sequence` is returned in the message response. ## Atomicity -As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/core/store.html#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/core/context.html) type. +As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/learn/advanced/store#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/learn/advanced/context.html) type. This provides atomic execution of transactions when using Interchain Accounts, where state changes are only committed if all `Msg`s succeed. diff --git a/docs/docs/05-migrations/04-v2-to-v3.md b/docs/docs/05-migrations/04-v2-to-v3.md index 4e2a704f27d..9c6433e0e49 100644 --- a/docs/docs/05-migrations/04-v2-to-v3.md +++ b/docs/docs/05-migrations/04-v2-to-v3.md @@ -72,7 +72,7 @@ For example, if a chain chooses not to integrate a controller submodule, it may #### Add `StoreUpgrades` for ICS27 module -For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/v0.45/core/upgrade.html#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: +For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/main/learn/advanced/upgrade#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: ```go if upgradeInfo.Name == "v3" && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) { diff --git a/docs/versioned_docs/version-v4.4.x/02-apps/02-interchain-accounts/06-transactions.md b/docs/versioned_docs/version-v4.4.x/02-apps/02-interchain-accounts/06-transactions.md index 05586d3678e..394d374989f 100644 --- a/docs/versioned_docs/version-v4.4.x/02-apps/02-interchain-accounts/06-transactions.md +++ b/docs/versioned_docs/version-v4.4.x/02-apps/02-interchain-accounts/06-transactions.md @@ -22,6 +22,6 @@ Transactions are executed via the ICS27 [`SendTx` API](02-auth-modules.md#trysen ## Atomicity -As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/core/store.html#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/core/context.html) type. +As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/learn/advanced/store#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/learn/advanced/context.html) type. This provides atomic execution of transactions when using Interchain Accounts, where state changes are only committed if all `Msg`s succeed. diff --git a/docs/versioned_docs/version-v4.4.x/04-migrations/04-v2-to-v3.md b/docs/versioned_docs/version-v4.4.x/04-migrations/04-v2-to-v3.md index ceddf14c360..fca445b0554 100644 --- a/docs/versioned_docs/version-v4.4.x/04-migrations/04-v2-to-v3.md +++ b/docs/versioned_docs/version-v4.4.x/04-migrations/04-v2-to-v3.md @@ -72,7 +72,7 @@ For example, if a chain chooses not to integrate a controller submodule, it may #### Add `StoreUpgrades` for ICS27 module -For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/v0.45/core/upgrade.html#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: +For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/main/learn/advanced/upgrade#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: ```go if upgradeInfo.Name == "v3" && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) { diff --git a/docs/versioned_docs/version-v5.3.x/02-apps/02-interchain-accounts/06-transactions.md b/docs/versioned_docs/version-v5.3.x/02-apps/02-interchain-accounts/06-transactions.md index 05586d3678e..394d374989f 100644 --- a/docs/versioned_docs/version-v5.3.x/02-apps/02-interchain-accounts/06-transactions.md +++ b/docs/versioned_docs/version-v5.3.x/02-apps/02-interchain-accounts/06-transactions.md @@ -22,6 +22,6 @@ Transactions are executed via the ICS27 [`SendTx` API](02-auth-modules.md#trysen ## Atomicity -As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/core/store.html#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/core/context.html) type. +As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/learn/advanced/store#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/learn/advanced/context.html) type. This provides atomic execution of transactions when using Interchain Accounts, where state changes are only committed if all `Msg`s succeed. diff --git a/docs/versioned_docs/version-v5.3.x/04-migrations/04-v2-to-v3.md b/docs/versioned_docs/version-v5.3.x/04-migrations/04-v2-to-v3.md index 6b6a7972777..34d87b46862 100644 --- a/docs/versioned_docs/version-v5.3.x/04-migrations/04-v2-to-v3.md +++ b/docs/versioned_docs/version-v5.3.x/04-migrations/04-v2-to-v3.md @@ -72,7 +72,7 @@ For example, if a chain chooses not to integrate a controller submodule, it may #### Add `StoreUpgrades` for ICS27 module -For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/v0.45/core/upgrade.html#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: +For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/main/learn/advanced/upgrade#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: ```go if upgradeInfo.Name == "v3" && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) { diff --git a/docs/versioned_docs/version-v6.2.x/02-apps/02-interchain-accounts/05-messages.md b/docs/versioned_docs/version-v6.2.x/02-apps/02-interchain-accounts/05-messages.md index 93172d04517..e9d6c517752 100644 --- a/docs/versioned_docs/version-v6.2.x/02-apps/02-interchain-accounts/05-messages.md +++ b/docs/versioned_docs/version-v6.2.x/02-apps/02-interchain-accounts/05-messages.md @@ -72,6 +72,6 @@ The packet `Sequence` is returned in the message response. ## Atomicity -As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/core/store.html#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/core/context.html) type. +As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/learn/advanced/store#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/learn/advanced/context.html) type. This provides atomic execution of transactions when using Interchain Accounts, where state changes are only committed if all `Msg`s succeed. diff --git a/docs/versioned_docs/version-v6.2.x/04-migrations/04-v2-to-v3.md b/docs/versioned_docs/version-v6.2.x/04-migrations/04-v2-to-v3.md index 5d9153594a3..cf4e1c1b8e3 100644 --- a/docs/versioned_docs/version-v6.2.x/04-migrations/04-v2-to-v3.md +++ b/docs/versioned_docs/version-v6.2.x/04-migrations/04-v2-to-v3.md @@ -72,7 +72,7 @@ For example, if a chain chooses not to integrate a controller submodule, it may #### Add `StoreUpgrades` for ICS27 module -For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/v0.45/core/upgrade.html#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: +For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/main/learn/advanced/upgrade#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: ```go if upgradeInfo.Name == "v3" && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) { diff --git a/docs/versioned_docs/version-v7.3.x/02-apps/02-interchain-accounts/05-messages.md b/docs/versioned_docs/version-v7.3.x/02-apps/02-interchain-accounts/05-messages.md index 5f1e636b89b..0c29e7364c5 100644 --- a/docs/versioned_docs/version-v7.3.x/02-apps/02-interchain-accounts/05-messages.md +++ b/docs/versioned_docs/version-v7.3.x/02-apps/02-interchain-accounts/05-messages.md @@ -73,6 +73,6 @@ The packet `Sequence` is returned in the message response. ## Atomicity -As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/core/store.html#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/core/context.html) type. +As the Interchain Accounts module supports the execution of multiple transactions using the Cosmos SDK `Msg` interface, it provides the same atomicity guarantees as Cosmos SDK-based applications, leveraging the [`CacheMultiStore`](https://docs.cosmos.network/main/learn/advanced/store#cachemultistore) architecture provided by the [`Context`](https://docs.cosmos.network/main/learn/advanced/context.html) type. This provides atomic execution of transactions when using Interchain Accounts, where state changes are only committed if all `Msg`s succeed. diff --git a/docs/versioned_docs/version-v7.3.x/05-migrations/04-v2-to-v3.md b/docs/versioned_docs/version-v7.3.x/05-migrations/04-v2-to-v3.md index 30465660d59..d32237692ae 100644 --- a/docs/versioned_docs/version-v7.3.x/05-migrations/04-v2-to-v3.md +++ b/docs/versioned_docs/version-v7.3.x/05-migrations/04-v2-to-v3.md @@ -72,7 +72,7 @@ For example, if a chain chooses not to integrate a controller submodule, it may #### Add `StoreUpgrades` for ICS27 module -For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/v0.45/core/upgrade.html#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: +For ICS27 it is also necessary to [manually add store upgrades](https://docs.cosmos.network/main/learn/advanced/upgrade#add-storeupgrades-for-new-modules) for the new ICS27 module and then configure the store loader to apply those upgrades in `app.go`: ```go if upgradeInfo.Name == "v3" && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) {