docs: update tooling link (backport #21973) (#21974)

Co-authored-by: Wukingbow <40993922+Wukingbow@users.noreply.github.com>
Co-authored-by: marbar3778 <marbar3778@yahoo.com>

docs/build/building-apps/03-app-upgrade.md

@@ -41,7 +41,7 @@ and gracefully exit.
 Generally the application binary will restart on exit, but then will execute this BeginBlocker
 again and exit, causing a restart loop. Either the operator can manually install the new software,
 or you can make use of an external watcher daemon to possibly download and then switch binaries,
-also potentially doing a backup. The SDK tool for doing such, is called [Cosmovisor](https://docs.cosmos.network/main/tooling/cosmovisor).
+also potentially doing a backup. The SDK tool for doing such, is called [Cosmovisor](https://docs.cosmos.network/main/build/tooling/cosmovisor).
 
 When the binary restarts with the upgraded version (here v0.40.0), it will detect we have registered the
 "testnet-v2" upgrade handler in the code, and realize it is the new version. It then will run the upgrade handler
@@ -131,7 +131,7 @@ to lose connectivity with the exiting nodes, thus this module prefers to just ha
 
 ## Automation
 
-Read more about [Cosmovisor](https://docs.cosmos.network/main/tooling/cosmovisor), the tool for automating upgrades.
+Read more about [Cosmovisor](https://docs.cosmos.network/main/build/tooling/cosmovisor), the tool for automating upgrades.
 
 ## Canceling Upgrades
 

docs/build/packages/README.md

@@ -9,7 +9,7 @@ It lists all standalone Go modules that are part of the Cosmos SDK.
 
 :::tip
 For more information on SDK modules, see the [SDK Modules](https://docs.cosmos.network/main/modules) section.
-For more information on SDK tooling, see the [Tooling](https://docs.cosmos.network/main/tooling) section.
+For more information on SDK tooling, see the [Tooling](https://docs.cosmos.network/main/build/tooling) section.
 :::
 
 ## Core