refactor agent documentation: replace generic terms with specific "Torus" references for clarity and consistency across guides

Author: Sipher

astro.config.mjs

@@ -82,15 +82,15 @@ export default defineConfig({
             { label: "Balance Operations", slug: "cli/balance-operations" },
           ],
         },
-        {
-          label: "Web Apps",
-          items: [
-            { label: "Torus Portal", slug: "web-apps/torus-portal" },
-            { label: "Torus Allocator", slug: "web-apps/torus-allocator" },
-            { label: "Torus Wallet", slug: "web-apps/torus-wallet" },
-            { label: "Torus DAO", slug: "web-apps/torus-dao" },
-          ],
-        },
+        // {
+        //   label: "Web Apps",
+        //   items: [
+        //     { label: "Torus Portal", slug: "web-apps/torus-portal" },
+        //     { label: "Torus Allocator", slug: "web-apps/torus-allocator" },
+        //     { label: "Torus Wallet", slug: "web-apps/torus-wallet" },
+        //     { label: "Torus DAO", slug: "web-apps/torus-dao" },
+        //   ],
+        // },
         {
           label: "Development",
           items: [

src/content/docs/explanations/agent-client.mdx

@@ -7,19 +7,21 @@ import {
   Aside
 } from "@astrojs/starlight/components";
 
-## Agent Client Architecture
 
-Agent clients in Torus provide a standardized way to interact with agent servers across the network. They handle authentication automatically and provide consistent interfaces for capability discovery and usage.
+Agent clients in Torus provide a standardized way to interact with agent servers across the network.
+They handle authentication automatically and provide consistent interfaces for capability discovery and usage.
 
 ### Authentication Flow
 
-Agent clients use the caller's keypair to generate JWT tokens signed with SR25519 signatures. This creates a trustless authentication system where agent servers can verify the caller's identity without prior coordination or shared secrets.
+Agent clients use the caller's keypair to generate JWT tokens signed with SR25519 signatures.
+This creates a trustless authentication system where agent servers can verify the caller's identity without prior coordination or shared secrets.
 
 Each API call includes the caller's cryptographic identity, enabling fine-grained permission controls based on the Torus namespace system.
 
 ### Communication Patterns
 
-Clients provide structured success/error responses with consistent error handling across all agent interactions. This standardization enables reliable capability composition and error propagation in complex agent workflows.
+Clients provide structured success/error responses with consistent error handling across all agent interactions.
+This standardization enables reliable capability composition and error propagation in complex agent workflows.
 
 The client abstracts HTTP complexities while maintaining type safety and enabling automatic retries, circuit breaking, and other resilience patterns for distributed agent communication.
 

src/content/docs/explanations/agent-editing.mdx

@@ -12,21 +12,24 @@ import {
   TabItem,
 } from "@astrojs/starlight/components";
 
-## Agent Editing System
 
-Agent editing in Torus allows agents to update their metadata, endpoints, and social connections after initial registration. Only the original registering wallet maintains editing rights, ensuring agent integrity.
+Agent editing in Torus allows agents to update their metadata, endpoints, and social connections after initial registration.
+Only the original registering wallet maintains editing rights, ensuring agent integrity.
 
-Agents can modify display information (titles, descriptions), service endpoints, visual assets, and social media links. Core identifiers and cryptographic associations remain immutable once set during registration.
+Agents can modify display information (titles, descriptions), service endpoints, visual assets, and social media links.
+Core identifiers and cryptographic associations remain immutable once set during registration.
 
 ### Update Economics
 
-Updates require only standard transaction fees - no token burning like initial registration. This minimal cost structure encourages agents to maintain current, accurate information while preventing spam through basic network fees.
+Updates require only standard transaction fees - no token burning like initial registration.
+This minimal cost structure encourages agents to maintain current, accurate information while preventing spam through basic network fees.
 
 Regular updates improve discoverability and signal ongoing agent activity, building trust within the Torus ecosystem.
 
 ### Storage Architecture
 
-Agent information uses a hybrid model: core identifiers and ownership on-chain, with extended metadata and rich content stored off-chain via IPFS. This balances blockchain immutability with the flexibility needed for comprehensive agent profiles.
+Agent information uses a hybrid model: core identifiers and ownership on-chain, with extended metadata and rich content stored off-chain via IPFS.
+This balances blockchain immutability with the flexibility needed for comprehensive agent profiles.
 
 ### Related Concepts
 

src/content/docs/explanations/agent-registration.mdx

@@ -19,9 +19,9 @@ import {
   TabItem,
 } from "@astrojs/starlight/components";
 
-## Agent Registration System
 
-Agent registration in Torus creates discoverable entities that can receive, create, and delegate permissions within the network. Registration is immediate with no approval required, but involves burning tokens to prevent spam.
+Agent registration in Torus creates discoverable entities that can receive, create, and delegate permissions within the network.
+Registration is immediate with no approval required, but involves burning tokens to prevent spam.
 
 ### Registration Economics
 
@@ -36,7 +36,9 @@ The burn mechanism maintains network quality by creating economic barriers to sp
 
 ### Discovery and Capabilities
 
-Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator page](https://allocator.torus.network/). They can participate in the permission system, create named capabilities for other agents to invoke, and engage in governance proposals. Agent metadata is stored off-chain via IPFS but referenced on-chain through content hashes.
+Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator page](https://allocator.torus.network/).
+They can participate in the permission system, create named capabilities for other agents to invoke, and engage in governance proposals.
+Agent metadata is stored off-chain via IPFS but referenced on-chain through content hashes.
 
 ### Related Concepts
 

src/content/docs/explanations/agent-server.mdx

@@ -7,21 +7,24 @@ import {
   Aside
 } from "@astrojs/starlight/components";
 
-## Agent Server Architecture
 
-Agent servers in Torus enable agents to expose APIs that other agents can discover and interact with. They use blockchain-based authentication and automatic documentation generation to facilitate secure capability sharing across the network.
+Agent servers in Torus enable agents to expose APIs that other agents can discover and interact with.
+They use blockchain-based authentication and automatic documentation generation to facilitate secure capability sharing across the network.
 
 ### Authentication Model
 
-Agent servers use SR25519 signature-based JWT authentication, where each API call is authenticated using the caller's cryptographic identity. This eliminates traditional API keys while ensuring requests are verifiable on-chain.
+Agent servers use SR25519 signature-based JWT authentication, where each API call is authenticated using the caller's cryptographic identity.
+This eliminates traditional API keys while ensuring requests are verifiable on-chain.
 
 Namespace permissions control access to specific capabilities, allowing fine-grained authorization based on the Torus permission system.
 
 ### Documentation and Discovery
 
-Servers automatically generate OpenAPI documentation, making capabilities discoverable and self-documenting. This enables agents to understand available endpoints, required inputs, and expected outputs without manual coordination.
+Servers automatically generate OpenAPI documentation, making capabilities discoverable and self-documenting.
+This enables agents to understand available endpoints, required inputs, and expected outputs without manual coordination.
 
-The integration of Hono for HTTP routing and Zod for input validation ensures type-safe APIs with automatic schema validation, maintaining consistency between TypeScript types, runtime validation, and generated documentation.
+The integration of Hono for HTTP routing and Zod for input validation ensures type-safe APIs with automatic schema validation,
+maintaining consistency between TypeScript types, runtime validation, and generated documentation.
 
 ### Related Concepts
 

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

@@ -15,13 +15,15 @@ import {
   CardGrid,
 } from "@astrojs/starlight/components";
 
-## Capability Demand Signaling System
 
-The [Create Signal feature on the Portal](https://portal.torus.network/signals/create-signal) allows agents to express in a technical and economical way their demand for specialized capabilities from other agents.
+The [Create Signal feature on the Portal](https://portal.torus.network/signals/create-signal) allows 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.
+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.
 
-For example, if you have an agent specializing on finding predictions for the swarm memory and your accuracy and rewards suffer by failing to filter out irony, then you could signal a demand for an irony classifier that you integrate with your agent.
+For example, if you have an agent specializing on finding predictions for the swarm memory and your accuracy and rewards suffer by failing to filter out irony,
+then you could signal a demand for an irony classifier that you integrate with your agent.
 
 ### Suggestions
 

src/content/docs/explanations/root-agents.mdx

@@ -19,13 +19,14 @@ import {
   TabItem,
 } from "@astrojs/starlight/components";
 
-## Root Agent System
 
-Root Agents are DAO-approved agents that receive direct emissions from the stake root and can set network goals around which swarms of agents organize. Unlike standard agents, Root Agents access funding without intermediaries and guide network development in areas of unique expertise.
+Root Agents are DAO-approved agents that receive direct emissions from the stake root and can set network goals around which swarms of agents organize.
+Unlike standard agents, Root Agents access funding without intermediaries and guide network development in areas of unique expertise.
 
 ### DAO Approval Process
 
-Becoming a Root Agent requires DAO member approval through [whitelist applications](https://dao.torus.network/whitelist-applications). Applications need majority approval and are evaluated based on technical capability, unique value proposition, and community standing.
+Becoming a Root Agent requires DAO member approval through [whitelist applications](https://dao.torus.network/whitelist-applications).
+Applications need majority approval and are evaluated based on technical capability, unique value proposition, and community standing.
 
 Successful applicants demonstrate credible execution, active community participation, and non-overlapping scope that complements existing Root Agents.
 

src/content/docs/explanations/start-here.mdx

@@ -21,11 +21,12 @@ Whether you're curious about agent systems, DAO processes, or network economics,
 
 Understanding how agents work within Torus:
 
-- [Agent Registration](https://docs.torus.network/explanations/agent-registration/) — How agent discovery, costs, and burn mechanisms work
-- [Root Agents](https://docs.torus.network/explanations/root-agents/) — DAO approval process, community requirements, and emission access
+- [Agent Registration](https://docs.torus.network/explanations/agent-registration/) — Registration economics, burn mechanisms, and discovery
+- [Root Agents](https://docs.torus.network/explanations/root-agents/) — DAO approval process and direct emission access
 - [Agent Server](https://docs.torus.network/explanations/agent-server/) — API architecture, authentication, and capability sharing
 - [Agent Client](https://docs.torus.network/explanations/agent-client/) — Communication patterns and authentication flow
-- [Agent Editing](https://docs.torus.network/explanations/agent-editing/) — Update mechanics and agent lifecycle
+- [Agent Editing](https://docs.torus.network/explanations/agent-editing/) — Update mechanics and storage architecture
+- [Demand Signaling](https://docs.torus.network/explanations/demand-signaling/) — Capability coordination and economic incentives
 
 ---
 
@@ -40,13 +41,13 @@ Understanding the core systems that power Torus:
 
 ---
 
-## Additional Resources
+## Questions Not Covered Here?
 
-Want to dive even deeper? Explore our technical resources:
+Can't find the explanation you're looking for? The community is here to help:
 
-- **[Torus Discord](https://discord.gg/torus)** — Join technical discussions and ask questions about how things work.
-- **[Torus Telegram](https://t.me/torusnetwork)** — Community discussions and insights.
-- **[Torus Twitter](https://twitter.com/torus_network)** — Torus updates and ecosystem developments.
+- **[Discord](https://discord.gg/torus)** — Technical discussions, support, and announcements
+- **[Telegram](https://t.me/torusnetwork)** — General chat and announcements
+- **[Twitter](https://x.com/torus_network)** — Updates and ecosystem news
 
 ### Core Projects
 

src/content/docs/how-to-guides/become-a-root-agent.mdx

@@ -100,9 +100,15 @@ Root Agents receive emissions directly from the stake root and can set goals for
 </Steps>
 
 
-## Support and Resources
-   If you want to understand more about the core differences between a Registered agent and a Whitelisted agent, you can refer to the [Concepts & Terminology](https://docs.torus.network/getting-started/concepts/) section.  
-   You can also get help directly from the community via:
+## What's Next?
 
-   - [Torus Community Discord](https://discord.gg/torus)  
-   - [Torus Telegram Group](https://t.me/torusnetwork)  
+After submitting your Root Agent application:
+
+- **Join the community**: Be active in [Discord](https://discord.gg/torus) to share updates about your agent.
+- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/root-agents/) approval criteria and DAO governance
+- **Check application status**: Monitor [DAO whitelist applications](https://dao.torus.network/whitelist-applications) for voting progress
+
+ Connect with the community:
+- [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements
+- [Telegram](https://t.me/torusnetwork) — General chat and announcements
+- [Twitter](https://x.com/torus_network) — Updates and ecosystem news  

src/content/docs/how-to-guides/bridge-from-base.mdx

@@ -137,10 +137,16 @@ To keep things clear and concise, **Native TORUS** will be referred to as **TORU
 </Steps>
 
 
-## Support and Resources
-   By following these steps, you can successfully bridge your tokens between Torus, Torus EVM, and Base.
-   Holding native TORUS is required to interact with Torus, and currently, this is the only supported method for bridging.  
-   If you need help or have questions, you can reach out through the official community channels:
+## What's Next?
 
-   - [Torus Community Telegram](https://t.me/torusnetwork)
-   - [Torus Community Discord](https://discord.gg/torus)
+Now that you have TORUS tokens, you can:
+
+- **Start earning rewards**: [Stake your TORUS](https://docs.torus.network/how-to-guides/stake-your-torus/) to support agents and earn emissions
+- **Become an agent**: [Register an agent](https://docs.torus.network/how-to-guides/register-an-agent/) to provide services and earn directly
+- **Explore the ecosystem**: Browse agents and allocators on the [Torus Portal](https://portal.torus.network/)
+- **Understand tokenomics**: Learn about [TORUS economics](https://docs.torus.network/concepts/tokenomics/) and emission mechanisms
+
+ Connect with the community:
+- [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements
+- [Telegram](https://t.me/torusnetwork) — General chat and announcements
+- [Twitter](https://x.com/torus_network) — Updates and ecosystem news