Improve documentation with proper internal links between pages and cross-references

- Remove .md extensions from links (per .clinerules guidelines)

- Add cross-references between related documentation sections

- Add links to newly created documentation pages

- Add reference to Context Window management in context mentions documentation

Author: Michaelzag

docs/advanced-usage/custom-instructions.md

@@ -9,7 +9,7 @@ Roo Code allows you to customize its behavior using custom instructions at both
 
 ## Preferred Language
 
-You can specify a preferred language for Roo Code to use. When set, this appears at the start of your custom instructions and directs Roo Code to communicate in your chosen language. You can set this in the **Prompts** tab.
+You can specify a preferred language for Roo Code to use. When set, this appears at the start of your custom instructions and directs Roo Code to communicate in your chosen language. You can set this in the **Prompts** tab. For more details on managing this and other settings, see [Managing Preferences and Settings](managing-preferences).
 
 ## Global Custom Instructions
 

docs/advanced-usage/custom-rules.md

@@ -12,7 +12,7 @@ Custom rules are guidelines stored in special files in your project's root direc
 - Error handling approaches
 - Project-specific conventions
 
-Unlike general custom instructions, rules are typically more structured and focused on specific technical requirements.
+Unlike general [custom instructions](custom-instructions), rules are typically more structured and focused on specific technical requirements.
 
 ## Rule File Types
 
@@ -237,7 +237,7 @@ Review and update your rules as your project evolves:
 
 For an even more tailored experience, you can:
 
-1. Create a custom mode with specific capabilities
+1. Create a [custom mode](custom-modes) with specific capabilities
 2. Create matching `.clinerules-[mode]` file
 3. Get specialized assistance that follows your guidelines
 

docs/advanced-usage/experimental-features.md

@@ -36,7 +36,7 @@ This is an alternate diff editing strategy to the standard search-and-replace al
 
 This will automatically save a checkpoint to git whenever you make changes to files.
 
-This lets you easily restore a previous state of the files if anything goes wrong.
+This lets you easily restore a previous state of the files if anything goes wrong. For more details, see [Checkpoints](checkpoints).
 
 **When to use it:** Enable this feature when:
 - You're making extensive changes to your codebase
@@ -72,7 +72,7 @@ Adds a new tool for inserting content at any position in a file.
 
 ### Power Steering
 
-When enabled, Roo will remind the model about the details of its current mode definition more frequently. This will lead to stronger adherence to role definitions and custom instructions, but will use more tokens per message.
+When enabled, Roo will remind the model about the details of its current mode definition more frequently. This will lead to stronger adherence to role definitions and custom instructions, but will use more tokens per message. For more on how this affects token usage, see [Managing the Context Window](managing-context-window).
 
 **When to use it:** Enable this feature when:
 - You need strict adherence to coding standards

docs/advanced-usage/managing-context-window.md

@@ -49,9 +49,9 @@ This limits how much terminal output Roo can see when you use `@terminal`:
 
 ### Power Steering (Experimental)
 
-**Setting**: `powerSteering` 
+**Setting**: `powerSteering`
 
-When enabled, Roo will remind itself about its current mode and instructions more frequently.
+When enabled, Roo will remind itself about its current mode and instructions more frequently. See [Experimental Features](experimental-features) for more information.
 - **Enabled**: Stronger adherence to instructions but uses more context space
 - **Disabled**: More context available for content but potentially less consistent adherence
 
@@ -61,7 +61,7 @@ When enabled, Roo will remind itself about its current mode and instructions mor
 
 **Setting**: `mcpEnabled`
 
-When enabled, Roo includes MCP server information in the context.
+When enabled, Roo includes [MCP](mcp) server information in the context.
 - **Enabled**: Access to MCP tools but uses some context space
 - **Disabled**: Saves context space but no MCP capabilities
 

docs/advanced-usage/managing-preferences.md

@@ -73,7 +73,7 @@ These control more technical aspects of Roo:
 
 ### Experimental Features
 
-As covered in [Experimental Features](experimental-features.md), these settings enable cutting-edge capabilities that are still under development.
+As covered in [Experimental Features](experimental-features), these settings enable cutting-edge capabilities that are still under development.
 
 ## Project-Specific Settings
 
@@ -162,6 +162,8 @@ Some settings significantly affect token usage:
 | Preferred Language | Minimal impact |
 | MCP Enabled | Increases if MCP servers are complex |
 
+For more detailed information on how these settings affect your context window, see [Managing the Context Window](managing-context-window).
+
 If you're concerned about token usage or costs, consider:
 - Disabling Power Steering
 - Reducing Max Open Tabs Context to 5-10

docs/advanced-usage/mcp.md

@@ -153,7 +153,7 @@ If server operations are slow:
 
 ## Disabling MCP Features
 
-Roo Code provides two settings to control the use of MCP servers, to help you manage token usage and security:
+Roo Code provides two settings to control the use of MCP servers, to help you manage token usage and security. For a complete overview of all settings, see [Managing Preferences and Settings](managing-preferences):
 
 ### 1. Disable MCP Servers Entirely
 

docs/basic-usage/context-mentions.md

@@ -1,6 +1,6 @@
 # Context Mentions
 
-Context mentions are a powerful way to provide Roo Code with specific information about your project, allowing it to perform tasks more accurately and efficiently.  You can use mentions to refer to files, folders, problems, and Git commits.  Context mentions start with the `@` symbol.
+Context mentions are a powerful way to provide Roo Code with specific information about your project, allowing it to perform tasks more accurately and efficiently. You can use mentions to refer to files, folders, problems, and Git commits. Context mentions start with the `@` symbol. Effective use of context mentions can help manage your available [context window](../advanced-usage/managing-context-window) more efficiently.
 
 ## Types of Mentions