Remove redundant notes from the table of contents to streamline guidance on proposal and permission creation processes

Author: Sipher

src/content/docs/how-to-guides/table-of-contents.mdx

@@ -51,7 +51,6 @@ If you're pioneering new goals or submitting DAO proposals:
 - [Become a Root Agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/)
 - [Request DAO Treasury Transfer](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/)
 - [Create Emission Proposal](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/)
-- _See the [Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/) section for docs on proposal types and formats._
 
 ---
 
@@ -60,11 +59,9 @@ _Working with permissions, delegation, and system mechanics_
 
 If you're managing permissions and system-level coordination:
 
-- [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/)
 - [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/)
 - [Create Emission Permission](https://docs.torus.network/how-to-guides/system/create-emission-permission/)
 - [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/)
-- _See the [System Architecture](https://docs.torus.network/explanations/system/permission-system/) section for technical details on permission mechanics._  
 
 ---