fix more broken links and references

Author: kings177

src/content/docs/agents/apply-root-agent.mdx

@@ -69,7 +69,7 @@ Root agent status is achieved through a DAO voting process.
 
 <Steps>
 
-1. Visit the [Whitelist Applications](https://dao.torus.network/whitelist-applications) tab in the [Torus DAO](https://dao.torus.network/k)
+1. Visit the [Whitelist Applications](https://dao.torus.network/whitelist-applications) tab in the [Torus DAO](https://dao.torus.network/)
 2. Connect your Torus wallet
 3. Click "Shape the Network" to open the application form
 4. Select "Whitelist an Agent" for root agent application

src/content/docs/agents/demand-signaling.mdx

@@ -21,8 +21,7 @@ import {
 
 ### Capability demand signaling system
 
-The ["create signal"](https://portal.torus.network/create-signal) feature on the Portal allows root agents to express in a technical and economical way their demand for specialized capabilities from other agents. 
-The ["create signal"](https://portal.torus.network/create-signal) feature on the Portal allows agents to technically and economically express their demand for specialized capabilities from other agents.
+The **"create signal"** feature on the Portal allows root agents to express in a technical and economical way their demand for specialized capabilities from other agents. 
 
 Standard agents are looking for opportunities to receive emission delegations by providing specialized capabilities. This means, you can define a problem and increase interest in solving it by proposing an allocation of your own emissions. 
 
@@ -34,7 +33,7 @@ You can let agents sub-specialize within your problem domain, similar to how you
 
 We expect root agents that apply this feature effectively to outcompete root agents who stay solo in rewards. 
 
-The text should clearly specify the semantics & goal, as well as the expected endpoint interface. Input-output examples are helpful. We strongly recommend to use the [agent API standard](/src/content/docs/agents/agent-api-standard), which your text can just refer to. If you are using a different schema, fully specify it. 
+The text should clearly specify the semantics & goal, as well as the expected endpoint interface. Input-output examples are helpful. We strongly recommend to use the example in the [agent setup server](server-setup.mdx), which your text can just refer to. If you are using a different schema, fully specify it. 
 
 ## Prerequisites
 

src/content/docs/getting-started/setup-cli.mdx

@@ -146,8 +146,7 @@ encouraged! :)
 
 To report a bug or request a feature, please [open an issue on GitHub].
 
-If you have any questions, feel free to ask on the [torus cli Discord channel] or
-post on our [GitHub discussions page].
+If you have any questions, feel free to ask on the [torus cli Discord channel].
 
 To contribute to the codebase, using Poetry you can install the development dependencies with:
 
@@ -160,6 +159,6 @@ it can [require some environment-specific binaries to be installed][ruff-install
 ---
 
 [open an issue on GitHub]: https://github.com/renlabs-dev/torus-cli/issues/new/choose
-[torus cli Discord channel]: https://go.renlabs-dev.org/torus-cli-channel
-[GitHub discussions page]: https://github.com/renlabs-dev/torus-cli/discussions
+[torus cli Discord channel]: https://discord.com/channels/1306654856286699590/1306654857046003716
 [ruff-installation]: https://docs.astral.sh/ruff/installation/
+ 

src/content/docs/network/running-node.mdx

@@ -18,7 +18,7 @@ This guide explains how to set up and run a local Torus Substrate node, noting t
 
 ### Dependencies
 
-The recommended way to install dependencies is [using Nix](docs/nix.md).
+The recommended way to install dependencies is [using Nix](https://github.com/renlabs-dev/torus-substrate/blob/main/docs/nix.md).
 
 If you don't want to use Nix, you should have the following dependencies:
 

src/content/docs/web-apps/torus-portal.mdx

@@ -25,7 +25,7 @@ Torus Portal is the web interface for managing permissions and capabilities. Use
 2. **Fill Form**: Configure delegator, recipient, scope, duration
 3. **Submit**: Create the permission
 
-For permission details, see [Emission Permissions](/advanced/emission-permissions) and [Capability Permissions](/advanced/namespace-permissions).
+For permission details, see [Permissions System](../v05/permissions.mdx).
 
 ## Managing Capabilities
 
@@ -41,7 +41,7 @@ For permission details, see [Emission Permissions](/advanced/emission-permission
 2. **Choose Granularity**: Delete specific method or entire capability
 3. **Confirm**: Delete (only works if no active delegations exist)
 
-For namespace concepts, see [Namespaces](../v05/permissions.mdx).
+For Capability concepts, see [Capability Permissions](../v05/capability-permissions.mdx).
 
 ## Network Operations