fix broken links with redirects and update urls to external resources…

… that changed or are broken (#450)

docs/build/getting-started/explore-more.mdx

@@ -44,7 +44,7 @@ Below are some additional tutorials to help you get started with Flow:
   {
     type: 'link',
     label: 'NFT Guide',
-    href: 'https://academy.ecdao.org/en/quickstarts/1-non-fungible-token',
+    href: 'https://academy.ecdao.org/en/quickstarts/1-non-fungible-token-next',
     description: 'A DApp that lets users create an empty collection, mint some pre-loaded NFTs, and transfer them to another account on Flow testnet.',
     customProps: {
       icon: <FontAwesomeIcon icon={faGem} className="h-16" />,

docs/build/guides/smart-contracts/testing.md

@@ -191,7 +191,7 @@ The Cadence testing framework provides various features and techniques for writi
 
 - [**Code Coverage**](https://github.com/m-Peter/flow-code-coverage): You can use the `--cover` flag with the `flow test` command to view code coverage results when running your tests. This allows you to identify areas of your code that are not adequately covered by your test inputs.
 - **Test Helpers**: Test helpers are reusable functions that help you set up the initial state for your test files. You can define test helpers in a Cadence program and use them in your test files by importing it whenever needed.
-- [**Assertions**](https://cadence-lang.org/docs/testing-framework.mdx#assertions): The testing framework provides built-in assertion functions, such as `assertEqual`, `beNil`, `beEmpty`, `contain`, to help you verify the expected behavior of your smart contracts.
+- [**Assertions**](https://cadence-lang.org/docs/testing-framework#assertions): The testing framework provides built-in assertion functions, such as `assertEqual`, `beNil`, `beEmpty`, `contain`, to help you verify the expected behavior of your smart contracts.
 - **Test Suites**: You can organize your test files into test suites to improve the readability and maintainability of your test code. Test suites allow you to group related test cases and set up common test helpers for all the tests in the suite.
 - [**Integration tests**](https://github.com/bjartek/overflow): In our previous example, we would directly call the available methods on the contract under test. This is generally categorized as unit testing. You can also write integration tests, by executing scripts & transactions to interact with the contracts under testing. If you would like to write your tests in Go, instead of Cadence, you can use [Overflow tool](https://github.com/bjartek/overflow) to run integration tests against either an local emulator, testnet, mainnet or an in memory instance of the flow-emulator.
 

docs/tutorials/NFT-drop-styles.md

@@ -24,7 +24,7 @@ NFT buyers like this strategy because they don't have to trust the dapp to compl
 This strategy doesn't need a backend, which lowers the costs and complexity for developers.
 However, while the lack of Know Your Customer (KYC) makes this strategy frictionless for buyers and developers, it also leaves the dapp susceptible to bot attacks because the developer can't verify that the customers are real people.
 
-Real-world examples of dapps using this strategy include: [Viv3](https://viv3.com/), [BloctoBay](https://bay.blocto.app/), [Chainmonsters](https://chainmonsters.com/), and [NBA Topshot](https://nbatopshot.com/).
+Real-world examples of dapps using this strategy include: [Viv3](https://viv3.com/), [BloctoBay](https://bay.blocto.app/), [NBA Topshot](https://nbatopshot.com/).
 ![On-chain pre-minted NFT diagram](NFTimages/image1.png)
 
 ## Off-chain Sale of Pre-Minted NFTs

vercel.json

@@ -84,17 +84,17 @@
     },
     {
       "source": "/hybrid-custody/:path*",
-      "destination": "/concepts/account-linking/:path*",
+      "destination": "/build/advanced-concepts/account-linking/:path*",
       "permanent": true
     },
     {
       "source": "/concepts/hybrid-custody/:path*",
-      "destination": "/concepts/account-linking/:path*",
+      "destination": "/build/advanced-concepts/account-linking/:path*",
       "permanent": true
     },
     {
       "source": "/concepts/account-linking/guides/:path*",
-      "destination": "/concepts/account-linking/child-accounts",
+      "destination": "/build/advanced-concepts/account-linking/:path*",
       "permanent": true
     },
     {
@@ -237,6 +237,11 @@
       "destination": "/tools/clients/fcl-js",
       "permanent": true
     },
+    {
+      "source": "/tools/fcl-js/sdk-guidelines",
+      "destination": "/tools/clients/fcl-js/sdk-guidelines",
+      "permanent": true
+    }, 
     {
       "source": "/tools/fcl-js/reference/:path*",
       "destination": "/tools/clients/fcl-js/:path*",
@@ -264,7 +269,7 @@
     },
     {
       "source": "/account-linking/:path*",
-      "destination": "/concepts/account-linking/:path*",
+      "destination": "/build/advanced-concepts/account-linking/:path*",
       "permanent": true
     },
     {
@@ -722,8 +727,8 @@
       "permanent": true
     },
     {
-      "source": "/concepts/account-linking",
-      "destination": "/build/advanced-concepts/account-linking",
+      "source": "/concepts/account-linking/:path*",
+      "destination": "/build/advanced-concepts/account-linking/:path*",
       "permanent": true
     },
     {
@@ -776,11 +781,6 @@
       "destination": "/build/flow",
       "permanent": true
     },
-    {
-      "source": "/concepts/account-linking/child-accounts",
-      "destination": "/build/advanced-concepts/account-linking",
-      "permanent": true
-    },
     {
       "source": "/docs/node-roles",
       "destination": "/references/run-and-secure/node-operation/node-roles",