docs: fix invalid multiple links

docs/learn/advanced/08-events.md

@@ -56,7 +56,7 @@ The following examples show how to query Events using the Cosmos SDK.
 | `tx.height=23`                                   | Query all transactions at height 23                                                                                                                  |
 | `message.action='/cosmos.bank.v1beta1.Msg/Send'` | Query all transactions containing an x/bank `Send` [Service `Msg`](../../build/building-modules/03-msg-services.md). Note the `'`s around the value. |
 | `message.module='bank'`                          | Query all transactions containing messages from the x/bank module. Note the `'`s around the value.                                                   |
-| `create_validator.validator='cosmosval1...'`     | x/staking-specific Event, see [x/staking SPEC](../../build/modules/staking/README.md).                                                                 |
+| `create_validator.validator='cosmosval1...'`     | x/staking-specific Event, see [x/staking SPEC](/x/staking/README.md).                                                                 |
 <!-- markdown-link-check-enable -->
 ## EventManager
 

docs/learn/beginner/02-query-lifecycle.md

@@ -17,7 +17,7 @@ This document describes the lifecycle of a query in a Cosmos SDK application, fr
 
 A [**query**](../../build/building-modules/02-messages-and-queries.md#queries) is a request for information made by end-users of applications through an interface and processed by a full-node. Users can query information about the network, the application itself, and application state directly from the application's stores or modules. Note that queries are different from [transactions](../advanced/01-transactions.md) (view the lifecycle [here](./01-tx-lifecycle.md)), particularly in that they do not require consensus to be processed (as they do not trigger state-transitions); they can be fully handled by one full-node.
 <!-- markdown-link-check-disable -->
-For the purpose of explaining the query lifecycle, let's say the query, `MyQuery`, is requesting a list of delegations made by a certain delegator address in the application called `simapp`. As is to be expected, the [`staking`](../../build/modules/staking/README.md) module handles this query. But first, there are a few ways `MyQuery` can be created by users.
+For the purpose of explaining the query lifecycle, let's say the query, `MyQuery`, is requesting a list of delegations made by a certain delegator address in the application called `simapp`. As is to be expected, the [`staking`](/x/staking/README.md) module handles this query. But first, there are a few ways `MyQuery` can be created by users.
 <!-- markdown-link-check-enable -->
 ### CLI
 
@@ -27,7 +27,7 @@ The main interface for an application is the command-line interface. Users conne
 simd query staking delegations <delegatorAddress>
 ```
 <!-- markdown-link-check-disable-next-line -->
-This query command was defined by the [`staking`](../../build/modules/staking/README.md) module developer and added to the list of subcommands by the application developer when creating the CLI.
+This query command was defined by the [`staking`](/x/staking/README.md) module developer and added to the list of subcommands by the application developer when creating the CLI.
 
 Note that the general format is as follows:
 

x/auth/README.md

@@ -32,7 +32,7 @@ This module is used in the Cosmos Hub.
 
 ## Concepts
 
-**Note:** The auth module is different from the [authz module](../modules/authz/).
+**Note:** The auth module is different from the [authz module](../authz/).
 
 The differences are:
 

x/authz/README.md

@@ -40,7 +40,7 @@ on behalf of one account to other accounts. The design is defined in the [ADR 03
 A *grant* is an allowance to execute a Msg by the grantee on behalf of the granter.
 Authorization is an interface that must be implemented by a concrete authorization logic to validate and execute grants. Authorizations are extensible and can be defined for any Msg service method, even if the Msg method is defined outside of the module. See the `SendAuthorization` example in the next section for more details.
 
-**Note:** The authz module is different from the [auth (authentication)](../modules/auth/) module, which is responsible for specifying the base transaction and account types.
+**Note:** The authz module is different from the [auth (authentication)](../auth/) module, which is responsible for specifying the base transaction and account types.
 
 ```go reference
 https://github.com/cosmos/cosmos-sdk/blob/v0.52.0-beta.1/x/authz/authorizations.go#L14-L28