diff --git a/docs/customization/prompts.mdx b/docs/customization/prompts.mdx index 6ca6e1917c9..695df29a278 100644 --- a/docs/customization/prompts.mdx +++ b/docs/customization/prompts.mdx @@ -6,7 +6,7 @@ description: "These are the specialized instructions that shape how models respo - **Define interaction patterns** for specific tasks or frameworks - **Encode domain expertise** for particular technologies - **Ensure consistent guidance** aligned with organizational practices -- **Can be shared and reused** across multiple assistants +- **Can be shared and reused** across multiple configs - **Act as automated code reviewers** that ensure consistency across teams ![Prompts Overview](/images/customization/images/prompts-blocks-overview-17194d870840576f9a0dde548f2c70ec.png) diff --git a/docs/customization/rules.mdx b/docs/customization/rules.mdx index d1b528ffdc7..73920b0fbd5 100644 --- a/docs/customization/rules.mdx +++ b/docs/customization/rules.mdx @@ -20,7 +20,7 @@ Your agent detects rules and applies the specified rules while in [Agent](/ide-e - Create files in `.continue/rules` folder -- Automatically appear with Hub assistants +- Automatically appear with Hub configs - Edit directly in your file system - Version controlled alongside your code - Best for project-specific rules (e.g., "remember to generate migrations after modifying the db") diff --git a/docs/customize/deep-dives/rules.mdx b/docs/customize/deep-dives/rules.mdx index a065a158d24..af2ad17ebec 100644 --- a/docs/customize/deep-dives/rules.mdx +++ b/docs/customize/deep-dives/rules.mdx @@ -31,7 +31,7 @@ Continue supports two types of rules with different behaviors: - **Location**: `.continue/rules` folder in your workspace -- **Visibility**: Automatically visible when using Hub assistants +- **Visibility**: Automatically visible when using Hub configs - **Creation**: Add rules button in VSCode or manual file creation - **File Management**: Creates actual `.md` files you can edit directly @@ -53,7 +53,7 @@ When using Continue, rules are loaded in this order: 4. **Global rules** (from `~/.continue/rules` folder) -**TL;DR**: Local rules show up automatically when using Hub assistants. Hub rules show up automatically when referenced in your config. +**TL;DR**: Local rules show up automatically when using Hub configs. Hub rules show up automatically when referenced in your config. ## Quick Start: How to Create Your First Rule File @@ -228,7 +228,7 @@ globs: ["**/*.ts", "**/*.tsx"] **Solution**: - **Hub rules** only appear when referenced in your config.yaml using the `uses:` syntax -- **Local rules** automatically appear when using Hub assistants +- **Local rules** automatically appear when using Hub configs - There's currently no automatic bidirectional sync ### Issue: "Edit" Links Point to Wrong Location diff --git a/docs/customize/model-providers/top-level/bedrock.mdx b/docs/customize/model-providers/top-level/bedrock.mdx index d4008469f2a..5b3d581ef36 100644 --- a/docs/customize/model-providers/top-level/bedrock.mdx +++ b/docs/customize/model-providers/top-level/bedrock.mdx @@ -90,8 +90,8 @@ You can also use an AWS `accessKeyId` and `secretAccessKey` for authentication i model: env: region: us-east-1 - accessKeyId: ${{ secrets.AWS_ACCESS_KEY_ID }} # can also enter key inline here for local assistants - secretAccessKey: ${{ secrets.AWS_SECRET_ACCESS_KEY }} # can also enter key inline here for local assistants + accessKeyId: ${{ secrets.AWS_ACCESS_KEY_ID }} # can also enter key inline here for local configs + secretAccessKey: ${{ secrets.AWS_SECRET_ACCESS_KEY }} # can also enter key inline here for local configs roles: - chat ``` diff --git a/docs/getting-started/extensions.mdx b/docs/getting-started/extensions.mdx index 54a490aca5a..326ba339223 100644 --- a/docs/getting-started/extensions.mdx +++ b/docs/getting-started/extensions.mdx @@ -1,6 +1,6 @@ --- title: "Understanding Configs" -description: "Continue offers two ways to configure your AI assistants" +description: "Continue offers two ways to configure your AI agents" --- This content has moved to our comprehensive guide: [Understanding Hub vs Local Configuration](/guides/understanding-configs) diff --git a/docs/guides/dlt-mcp-continue-cookbook.mdx b/docs/guides/dlt-mcp-continue-cookbook.mdx index 40346d9e4f8..f25b11bee19 100644 --- a/docs/guides/dlt-mcp-continue-cookbook.mdx +++ b/docs/guides/dlt-mcp-continue-cookbook.mdx @@ -444,7 +444,7 @@ After completing this guide, you have a complete **AI-powered data pipeline deve icon="newspaper" href="https://dlthub.com/blog/deep-dive-assistants-mcp-continue" > - Learn about AI assistants, MCP, and Continue integration + Learn about AI agents, MCP, and Continue integration - Browse the [Continue Mission Control](https://hub.continue.dev/explore?type=assistants) to see what configs others have built + Browse the [Continue Mission Control](https://hub.continue.dev/explore?type=configs) to see what configs others have built diff --git a/docs/mission-control/governance/org-permissions.mdx b/docs/mission-control/governance/org-permissions.mdx index 4bdb8e82faa..da0cd601b6d 100644 --- a/docs/mission-control/governance/org-permissions.mdx +++ b/docs/mission-control/governance/org-permissions.mdx @@ -3,8 +3,8 @@ title: "Organization Permissions" description: "Users can have the following roles within an organization:" --- -1. Admins are users who can manage members, secrets, blocks, assistants, etc. -2. Members are users who can use assistants, blocks, secrets, etc. +1. Admins are users who can manage members, secrets, blocks, configs, etc. +2. Members are users who can use configs, blocks, secrets, etc. **User permissions for each role depend on the pricing plan:** diff --git a/docs/mission-control/secrets/secret-resolution.mdx b/docs/mission-control/secrets/secret-resolution.mdx index 72638da7be0..00bf36affbe 100644 --- a/docs/mission-control/secrets/secret-resolution.mdx +++ b/docs/mission-control/secrets/secret-resolution.mdx @@ -1,6 +1,6 @@ --- title: "Secret Resolution" -description: "User or Org secrets should be used depending on how users want them to be shared within their organization and assistants." +description: "User or Org secrets should be used depending on how users want them to be shared within their organization and configs." --- For individual users and [Solo](/hub/governance/pricing#solo) organizations, secret resolution is performed in the following order: