Update links

docs/1.concepts/storage/storage-staking.md

@@ -18,7 +18,7 @@ On each incoming transaction that adds data.
 
 Let's walk through an example:
 
-1. You launch [a guest book app](https://examples.near.org/guest-book), deploying your app's smart contract to the account `example.near`
+1. You launch [a guest book app](../../3.tutorials/examples/guest-book.md), deploying your app's smart contract to the account `example.near`
 2. Visitors to your app can add messages to the guest book. This means your users will, [by default](/concepts/protocol/gas#understanding-gas-fees), pay a small gas fee to send their message to your contract.
 3. When such a call comes in, NEAR will check that `example.near` has a large enough balance that it can stake an amount to cover the new storage needs. If it does not, the transaction will fail.
 

docs/2.build/1.chain-abstraction/chain-signatures/chain-signatures.md

@@ -32,7 +32,7 @@ There are five steps to create a Chain Signature:
 1. [Deriving the Foreign Address](#1-deriving-the-foreign-address) - Construct the address that will be controlled on the target blockchain
 2. [Creating a Transaction](#2-creating-the-transaction) - Create the transaction or message to be signed
 3. [Requesting a Signature](#3-requesting-the-signature) - Call the NEAR `v1.signer` contract requesting it to sign the transaction
-4. [Formatting the Signature](#4-reconstructing-the-signature) - Reconstruct the signature from the MPC service's response
+4. [Formatting the Signature](#4-formatting-the-signature) - Reconstruct the signature from the MPC service's response
 5. [Relaying the Signed Transaction](#5-relaying-the-signature) - Send the signed transaction to the destination chain for execution
 
 ![chain-signatures](/docs/assets/welcome-pages/chain-signatures-overview.png)

docs/2.build/2.smart-contracts/security/storage.md

@@ -7,7 +7,7 @@ On NEAR, your contract pays for the storage it uses. This means that the more da
 
 Let's walk through an example:
 
-1. You launch [a guest book app](https://examples.near.org/guest-book-js), deploying your app's smart contract to the account `example.near`
+1. You launch [a guest book app](../../../3.tutorials/examples/guest-book.md), deploying your app's smart contract to the account `example.near`
 2. Visitors to your app can add messages to the guest book. This means your users will pay a small gas fee to **store** their message to your contract.
 3. When a new message comes in, NEAR will check if `example.near` has enough balance to cover the new storage needs. If it does not, the transaction will fail.
 

docs/3.tutorials/nfts/minting-nfts.md

@@ -396,7 +396,7 @@ To view tokens owned by an account you can call the NFT contract with the follow
 This basic example illustrates all the required steps to deploy an NFT smart contract, store media files on IPFS,
 and start minting your own non-fungible tokens.
 
-Now that you're familiar with the process, you can check out our [NFT Example](https://examples.near.org/NFT) and learn more about the smart contract code and how you can transfer minted tokens to other accounts.
+Now that you're familiar with the process, you can check out our [NFT Example](0-intro.md) and learn more about the smart contract code and how you can transfer minted tokens to other accounts.
 Finally, if you are new to Rust and want to dive into smart contract development, our [Quick-start guide](../../2.build/2.smart-contracts/quickstart.md) is a great place to start.
 
 **_Happy minting!_** 🪙