Merge branch 'feat/example-tutorial-sync' of https://github.com/cosmos/docs into feat/example-tutorial-sync

Author: evanorti

sdk/next/learn/intro/sdk-app-architecture.mdx

@@ -190,7 +190,7 @@ In the Cosmos SDK, a **transaction** is a signed, serialized container that wrap
 
 Modules define message types using [Protocol Buffers (Protobuf)](/sdk/next/learn/concepts/encoding), which provide type-safe, cross-language serialization. Since CometBFT treats transactions as raw bytes and [KV stores](#kv-stores-and-multistore) only accept byte arrays, Protobuf serializes structured messages and state data into bytes for transmission and storage. Modules also define state schemas (what data the module stores), state transitions (how messages modify state), queries (allowing clients to read module state), and optional lifecycle hooks for tasks that run at block boundaries.
 
-To learn more about the transactions and messages, visit the [Transactions page](/sdk/next/learn/advanced/transactions). For more in-depth information on modules, visit the [Intro to Modules page] or check out [the Module Tutorial](/sdk/next/tutorials/example/00-overview) to learn how to build a module from scratch.
+To learn more about the transactions and messages, visit the [Transactions page](/sdk/next/learn/advanced/transactions). For more in-depth information on modules, visit the [Intro to Modules page](/sdk/next/learn/concepts/modules) or check out [the Module Tutorial](/sdk/next/tutorials/example/00-overview) to learn how to build a module from scratch.
 
 ### Block Lifecycle Hooks