minor fixes

docs.json

@@ -133,16 +133,11 @@
                 "pages": [
                   "build-on-celo/build-with-ai/8004",
                   "build-on-celo/build-with-ai/x402",
-                  "build-on-celo/build-with-ai/agent-skills"
-                ]
-              },
-              {
-                "group": "Development Tools",
-                "pages": [
-                  "build-on-celo/build-with-ai/vibe-coding",
-                  "build-on-celo/build-with-ai/tools"
+                  "build-on-celo/build-with-ai/agent-skills",
+                  "build-on-celo/build-with-ai/vibe-coding"
                 ]
               },
+
               {
                 "group": "MCP Servers",
                 "pages": [
@@ -331,7 +326,6 @@
                   "tooling/libraries-sdks/contractkit/odis"
                 ]
               },
-              "tooling/libraries-sdks/rainbowkit-celo/index",
               "tooling/libraries-sdks/web3/index"
             ]
           },
@@ -2957,7 +2951,7 @@
     },
     {
       "source": "/developer/rainbowkit-celo",
-      "destination": "/tooling/libraries-sdks/rainbowkit-celo"
+      "destination": "/tooling/libraries-sdks/celo-sdks"
     },
     {
       "source": "/developer/reown",
@@ -3062,6 +3056,10 @@
     {
       "source": "/tooling/plumo/verification-phase-2",
       "destination": "/home/index"
+    },
+    {
+      "source": "/community/developer-events",
+      "destination": "/contribute-to-celo/builders"
     }
   ],
   "footer": {

tooling/dev-environments/hardhat.mdx

@@ -30,20 +30,6 @@ Choose one of the following items to prepare a dApp to deploy on Celo.
 
 Open [hardhat.config.js](https://hardhat.org/config/) in a text editor and replace its contents with this [Celo configuration code](https://github.com/celo-org/celo-composer/blob/main/packages/hardhat/hardhat.config.ts). This code is similar to Hardhat settings with a few configuration updates needed to deploy to a Celo network. You will need to create a `.env` file in the project root directory and install `dotenv` with npm or yarn in order to read the `process.env.MNEMONIC` variable in the config file.
 
-### Connect to Local Network
-
-Using Celo Ganache CLI creates test accounts at the localhost on port 7545. The private network setup connects to your localhost on this port and gives you access to your accounts on ganache-cli.
-
-```js
-    localhost: {
-      url: "http://127.0.0.1:7545"
-    },
-```
-
-<Tip>
-If you choose to [Set up a Local Development Chain](/tooling/overview/setup/development-chain), your blockchain will also be hosted on a private network on localhost. This same configuration can be used to connect to the local development chain.
-</Tip>
-
 ### Connect to Testnet using Forno
 
 Using [Forno](/tooling/nodes/forno) allows you to connect to the Celo test blockchain without running a local node. The testnet configuration uses Forno to connect you to the Celo Sepolia Testnet using HDWalletProvider and the mnemonic stored in your **.env** file.

tooling/libraries-sdks/celo-sdks.mdx

@@ -11,14 +11,13 @@ Because Celo is compatible with Ethereum any ethereum package can be used with C
 
 ## Web3 Libraries
 
-- [viem](/developer/viem)
-- [ethers](/developer/ethers)
-- [thirdweb SDK](/developer/thirdweb-sdk)
-- [ContractKit (deprecated - only for internal use)](/developer/contractkit)
-- [Rainbowkit](/developer/rainbowkit-celo)
-- [web3.js (deprecated)](/developer/web3)
+- [viem](/tooling/libraries-sdks/viem)
+- [ethers](/tooling/libraries-sdks/ethers)
+- [thirdweb SDK](/tooling/libraries-sdks/thirdweb-sdk)
+- [ContractKit (deprecated - only for internal use)](/tooling/libraries-sdks/contractkit)
+- [web3.js (deprecated)](/tooling/libraries-sdks/web3)
 
 ## Wallet Libraries
 
-- [Reown](/developer/reown)
-- [Portal](/developer/portal)
+- [Reown](/tooling/libraries-sdks/reown)
+- [Portal](/tooling/libraries-sdks/portal)