Merge branch 'main' of github.com:cosmos/ibc-go into colin/1863-genes…

…is-migrations

README.md

@@ -35,7 +35,9 @@
     <img alt="E2E Status" src="https://github.com/cosmos/ibc-go/workflows/Tests%20/%20E2E/badge.svg" />
 </div>
 
-The [Inter-Blockchain Communication protocol (IBC)](https://ibcprotocol.org/) allows blockchains to talk to each other. IBC handles transport across different sovereign blockchains. This end-to-end, connection-oriented, stateful protocol provides reliable, ordered, and authenticated communication between heterogeneous blockchains. This IBC implementation in Golang is built as a Cosmos SDK module.
+The [Inter-Blockchain Communication protocol (IBC)](https://ibcprotocol.dev/) allows blockchains to talk to each other. This end-to-end, connection-oriented, stateful protocol provides reliable, ordered, and authenticated communication between heterogeneous blockchains. 
+
+This IBC implementation in Golang is built as a Cosmos SDK module. To understand more about how to use the `ibc-go` module as well as about the IBC protocol, please check out the Interchain Developer Academy [section on IBC](https://tutorials.cosmos.network/academy/3-ibc/), or [our docs](https://ibc.cosmos.network/main/ibc/overview.html).
 
 ## Roadmap
 
@@ -120,6 +122,6 @@ To report a security vulnerability, see our [bug bounty program](https://hackero
 
 ## Documentation and Resources
 
-- [IBC Website](https://ibcprotocol.org/)
+- [IBC Website](https://ibcprotocol.dev/)
 - [IBC Specification](https://github.com/cosmos/ibc)
 - [Documentation](https://ibc.cosmos.network/main/ibc/overview.html)

docs/.vuepress/config.js

@@ -462,8 +462,8 @@ module.exports = {
         text: "Chat with IBC developers in <a href='https://discord.gg/W8trcGV' target='_blank'>Discord</a>.",
       },
       textLink: {
-        text: "ibcprotocol.org",
-        url: "https://ibcprotocol.org",
+        text: "ibcprotocol.dev",
+        url: "https://ibcprotocol.dev",
       },
       services: [
         {

docs/ibc/apps/ibcmodule.md

@@ -209,7 +209,7 @@ Just as IBC expects modules to implement callbacks for channel handshakes, it al
 
 Once a module A and module B are connected to each other, relayers can start relaying packets and acknowledgements back and forth on the channel.
 
-![IBC packet flow diagram](https://ibcprotocol.org/_nuxt/img/packet_flow.1d89ee0.png)
+![IBC packet flow diagram](https://ibcprotocol.dev/_nuxt/img/packet_flow.1d89ee0.png)
 
 Briefly, a successful packet flow works as follows: