diff --git a/docs/admin/auth/index.mdx b/docs/admin/auth/index.mdx index 3df9e0c21..a60f00e10 100644 --- a/docs/admin/auth/index.mdx +++ b/docs/admin/auth/index.mdx @@ -143,7 +143,7 @@ The new user email, during their account creation, should match one of their Git Restricts sign-ins to members of the listed organizations. If empty or unset, no restriction will be applied. -If combined with `"allowSignup": true`, only members of the allowed orgs can create their accounts in Sourcegraph via GitHub authentitcation. +If combined with `"allowSignup": true`, only members of the allowed orgs can create their accounts in Sourcegraph via GitHub authentication. When combined with `"allowSignup": false` or unset, an admin should first create the user account so that the user can sign in with GitHub if they belong to the allowed orgs. @@ -284,7 +284,7 @@ When empty or unset, no restrictions will be applied. If combined with `"allowSignup": false`, an admin should first create the user account so that the user can sign in with GitLab. -If combined with `"allowSignup": true` or with `allowSignup` unset, only members of the allowed groups or subgroups can create their accounts in Sourcegraph via GitLab authentitcation. +If combined with `"allowSignup": true` or with `allowSignup` unset, only members of the allowed groups or subgroups can create their accounts in Sourcegraph via GitLab authentication. > WARNING: Users will require a minimum access level of `Guest` in at least one of the specified groups in order to gain access to Sourcegraph. GitLab offers a lower user permission level, [Minimal Access](https://docs.gitlab.com/ee/user/permissions.html#users-with-minimal-access), for Premium and Ultimate tier customers, which is often used to configure SAML SSO on GitLab. Sourcegraph does not currently support the `Minimal Access` access level, and users with this access level will not be allowed to sign in. In these cases it is recommended to create a subgroup and add all users that require access to Sourcegraph to that subgroup with a minimum access level of `Guest`, and then add that subgroup to the `allowGroups` list. diff --git a/docs/admin/auth/saml/okta.mdx b/docs/admin/auth/saml/okta.mdx index 95368a9b0..d5636c247 100644 --- a/docs/admin/auth/saml/okta.mdx +++ b/docs/admin/auth/saml/okta.mdx @@ -31,7 +31,7 @@ - Copy the URL from the new browser tab that will open. It will have the following format: ```sh - https://.okta.com/app//sso/saml/metadata + https://.okta.com/app//sso/saml/metadata ``` ## 2. Add the SAML auth provider to Sourcegraph site config diff --git a/docs/admin/code-hosts/gerrit.mdx b/docs/admin/code-hosts/gerrit.mdx index 1daa1857a..ce41110ec 100644 --- a/docs/admin/code-hosts/gerrit.mdx +++ b/docs/admin/code-hosts/gerrit.mdx @@ -72,7 +72,7 @@ To clone using SSH, provide `"gitSSHCredential"` in the configuration: ## Add Gerrit as an authentication provider -If the `"authorization": {}` option has been set on a Gerrit code host connection, a Gerrit authentication provider will be required so that authroized users are able to search for and browse the code mirrored by that code host connection. +If the `"authorization": {}` option has been set on a Gerrit code host connection, a Gerrit authentication provider will be required so that authorized users are able to search for and browse the code mirrored by that code host connection. 1. In the **Site Admin** settings area, select [**Site configuration**](/admin/config/site-config) from the options on the left. 2. Add a Gerrit configuration to the list of `"auth.providers"`. diff --git a/docs/admin/code-hosts/github.mdx b/docs/admin/code-hosts/github.mdx index 394bdc81f..a63419b0c 100644 --- a/docs/admin/code-hosts/github.mdx +++ b/docs/admin/code-hosts/github.mdx @@ -171,7 +171,7 @@ If you get an error message similar to following error while adding a GitHub App ``` -It means that the IP allowlist is enabled at the organisation level and you will need to add sourcegraph's IP addresseses to this allowlist in order for the app connection to work (see [GitHub's documentation](https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization#adding-an-allowed-ip-address)) +It means that the IP allowlist is enabled at the organisation level and you will need to add Sourcegraph's IP addresses to this allowlist in order for the app connection to work (see [GitHub's documentation](https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization#adding-an-allowed-ip-address)) ### Uninstalling an App diff --git a/docs/admin/code-hosts/src-serve-git.mdx b/docs/admin/code-hosts/src-serve-git.mdx index a3e06695c..6e57b2338 100644 --- a/docs/admin/code-hosts/src-serve-git.mdx +++ b/docs/admin/code-hosts/src-serve-git.mdx @@ -23,7 +23,7 @@ The most common use-case for `src serve-git` is to create git repos that do not - Using `git p4` to serve up Perforce repositories. - Serve up local repositories to Sourcegraph while trialling it. -> WARNING: `src serve-git` is not intended to be used to serve repos from a code host which is already configured to be synced by a seperate code host config. For instance if you have a self managed GitLab code host, it is not advised to use `src serve-git` to serve repos on the gitlab server. +> WARNING: `src serve-git` is not intended to be used to serve repos from a code host which is already configured to be synced by a separate code host config. For instance if you have a self managed GitLab code host, it is not advised to use `src serve-git` to serve repos on the gitlab server. ## Quickstart diff --git a/docs/admin/how-to/mutate-user-api.mdx b/docs/admin/how-to/mutate-user-api.mdx index 04a2d5f27..b643c99aa 100644 --- a/docs/admin/how-to/mutate-user-api.mdx +++ b/docs/admin/how-to/mutate-user-api.mdx @@ -55,7 +55,7 @@ This query will return the username after altering the user's username data as s } ``` -Learn more about the options available with the `updateUser` query in the graphQL API consule Documentation Explorer. +Learn more about the options available with the `updateUser` query in the graphQL API console Documentation Explorer. ## Remove a user diff --git a/docs/admin/how-to/repo-not-updated.mdx b/docs/admin/how-to/repo-not-updated.mdx index 18fc3d6bd..b0894b2ac 100644 --- a/docs/admin/how-to/repo-not-updated.mdx +++ b/docs/admin/how-to/repo-not-updated.mdx @@ -26,7 +26,7 @@ This document assumes that you are a [site admin](/admin) and **do not** have `d ### What is a bad repository? -A bad repository is simiply a repository that Sourcegraph cannot handle. For example: +A bad repository is simply a repository that Sourcegraph cannot handle. For example: 1. A large repository - This could result in gitserver running out of memory. diff --git a/docs/admin/how-to/site-admin-quickstart.mdx b/docs/admin/how-to/site-admin-quickstart.mdx index 4bd30c38a..cc9e1595a 100644 --- a/docs/admin/how-to/site-admin-quickstart.mdx +++ b/docs/admin/how-to/site-admin-quickstart.mdx @@ -14,7 +14,7 @@ If you need a deployment option that offers a higher level of scalability and av To help give you a starting point on choosing a deployment option and allocating resources to it, check out our [resource estimator](/self-hosted/deploy/resource-estimator). -For a comphrensive deployment guide for each option, check out our in-depth documentation for both [Docker Compose](/self-hosted/deploy/docker-compose/) and [Kubernetes](/self-hosted/deploy/kubernetes/). +For a comprehensive deployment guide for each option, check out our in-depth documentation for both [Docker Compose](/self-hosted/deploy/docker-compose/) and [Kubernetes](/self-hosted/deploy/kubernetes/). ### Deployment options diff --git a/docs/admin/permissions/api.mdx b/docs/admin/permissions/api.mdx index 45287d839..b438c9312 100644 --- a/docs/admin/permissions/api.mdx +++ b/docs/admin/permissions/api.mdx @@ -4,7 +4,7 @@ Sourcegraph's GraphQL API allows users to explicitly set repository permissions. ## Permissions mechanisms in parallel -If you want to use explicit permissions managmeent alongside permissions synchronised from code hosts, read section [permission mechanisms in parallel here](/admin/permissions/#permissions-mechanisms-in-parallel). +If you want to use explicit permissions management alongside permissions synchronised from code hosts, read section [permission mechanisms in parallel here](/admin/permissions/#permissions-mechanisms-in-parallel). ## Recommendations diff --git a/docs/admin/scim.mdx b/docs/admin/scim.mdx index c4e86a2f1..de73c43b8 100644 --- a/docs/admin/scim.mdx +++ b/docs/admin/scim.mdx @@ -16,7 +16,7 @@ Sourcegraph supports SCIM 2.0 for provisioning and de-provisioning _users_. SCIM integration requires your SCIM provider to have network connectivity to your Sourcegraph instance. For example, using Okta's SCIM service with a private Sourcegraph instance, you will need to implement an [Okta - privisioning + provisioning agent](https://help.okta.com/en-us/content/topics/provisioning/opp/opp-main.htm) within a network that can connect to both your Sourcegraph instance and Okta's cloud services before continuing this setup. diff --git a/docs/admin/telemetry/protocol.mdx b/docs/admin/telemetry/protocol.mdx index 8b25a7a42..131280be0 100644 --- a/docs/admin/telemetry/protocol.mdx +++ b/docs/admin/telemetry/protocol.mdx @@ -95,7 +95,7 @@ To learn more, refer to our [telemetry documentation](https://sourcegraph.com/do | Field | Type | Label | Description | | ----- | ---- | ----- | ----------- | -| flags | [EventFeatureFlags.FlagsEntry](#telemetrygateway-v1-EventFeatureFlags-FlagsEntry) | repeated |

Evaluated feature flags. In Soucegraph we currently only support boolean

feature flags, but in the API we allow arbitrary string values for future

extensibility.

This field should be hydrated by the Sourcegraph server, and not provided

by clients.

| +| flags | [EventFeatureFlags.FlagsEntry](#telemetrygateway-v1-EventFeatureFlags-FlagsEntry) | repeated |

Evaluated feature flags. In Sourcegraph we currently only support boolean

feature flags, but in the API we allow arbitrary string values for future

extensibility.

This field should be hydrated by the Sourcegraph server, and not provided

by clients.

| @@ -619,9 +619,9 @@ Sourcegraph Analytics features. {/* end HasExtensions */} - + -### TelemeteryGatewayService +### TelemetryGatewayService TelemetryGatewayService accepts telemetry and related data from Sourcegraph instances and managed services. @@ -629,7 +629,7 @@ instances and managed services. | ----------- | ------------ | ------------- | ------------| | RecordEvents | [RecordEventsRequest](#telemetrygateway-v1-RecordEventsRequest) stream | [RecordEventsResponse](#telemetrygateway-v1-RecordEventsResponse) stream |

RecordEvents streams telemetry events in batches to the Telemetry Gateway

service. Events should only be considered delivered if recording is

acknowledged in RecordEventsResponse.

This is the preferred mechanism for exporting large volumes of events in

bulk.

🚨 SECURITY: Callers exporting for single-tenant Sourcegraph should check

the attributes of the Event type to ensure that only the appropriate fields

are exported, as some fields should only be exported on an allowlist basis.

| | RecordEvent | [RecordEventRequest](#telemetrygateway-v1-RecordEventRequest) | [RecordEventResponse](#telemetrygateway-v1-RecordEventResponse) |

RecordEvent records a single telemetry event to the Telemetry Gateway service.

If the RPC succeeds, then the event was successfully published.

This RPC currently ONLY accepts events published by ManagedServiceIdentifier,

as this mechanism is intended for low-volume managed services. Higher-volume

use cases should implement a batching mechanism and use the RecordEvents

RPC instead.

🚨 SECURITY: Callers exporting for single-tenant Sourcegraph should check

the attributes of the Event type to ensure that only the appropriate fields

are exported, as some fields should only be exported on an allowlist basis.

| -| PublishInstanceUserMetadata | [PublishInstanceUserMetadataRequest](#telemetrygateway-v1-PublishInstanceUserMetadataRequest) stream | [PublishInstanceUserMetadataResponse](#telemetrygateway-v1-PublishInstanceUserMetadataResponse) |

PublishInstanceUserMetadata uploads additional user metadata from a

Sourcegraph instance. This matadata is used to enrich recorded events with

attributes that are considered sensitive and thus not part of the RecordEvents

and RecordEvent RPCs.

🚨 SECURITY: Callers exporting for single-tenant Sourcegraph should always

respect in-instance toggles for what user metadata should be exported.

| +| PublishInstanceUserMetadata | [PublishInstanceUserMetadataRequest](#telemetrygateway-v1-PublishInstanceUserMetadataRequest) stream | [PublishInstanceUserMetadataResponse](#telemetrygateway-v1-PublishInstanceUserMetadataResponse) |

PublishInstanceUserMetadata uploads additional user metadata from a

Sourcegraph instance. This metadata is used to enrich recorded events with

attributes that are considered sensitive and thus not part of the RecordEvents

and RecordEvent RPCs.

🚨 SECURITY: Callers exporting for single-tenant Sourcegraph should always

respect in-instance toggles for what user metadata should be exported.

| {/* end services */} diff --git a/docs/admin/webhooks/outgoing.mdx b/docs/admin/webhooks/outgoing.mdx index 2bdc7420a..740c3952e 100644 --- a/docs/admin/webhooks/outgoing.mdx +++ b/docs/admin/webhooks/outgoing.mdx @@ -88,7 +88,7 @@ The changeset webhook event payload mirrors the [GraphQL API](/api/graphql/) `Ex "created_at": "2023-03-19T05:41:24Z", // The date and time when the batch change was last updated. "title": "Hello World", - // The body of the changese (as Markdown). + // The body of the changeset (as Markdown). "body": "My first batch change!", // The username of the author of the changeset. Note that this is only available after the changeset has been published and is not available on some code hosts. "author_name": "my-username", @@ -110,7 +110,7 @@ The changeset webhook event payload mirrors the [GraphQL API](/api/graphql/) `Ex "check_state": "PASSED", // Any error that occurred when publishing or updating the changeset. "error": null, - // Any error that occured during the last sync of the changeset by Sourcegraph. + // Any error that occurred during the last sync of the changeset by Sourcegraph. "syncer_error": null, // The ID of the batch change that produced this changeset. "owning_batch_change_id": "QmF0Y2hDaGFuZ2U6MTcz" diff --git a/docs/api/index.mdx b/docs/api/index.mdx index f5e3ef353..804909e85 100644 --- a/docs/api/index.mdx +++ b/docs/api/index.mdx @@ -16,7 +16,7 @@ For specific types of integrations, Sourcegraph also offers the following APIs: - [Sourcegraph Analytics API](/analytics/api/), for accessing your Sourcegraph Analytics data - [Webhooks](/admin/webhooks/), for receiving event notifications from Sourcegraph -For diagnostics use cases, the [Sourcegraph GraphQL debug API](/api/graphql/) is also available without any compatibility guarauntees. +For diagnostics use cases, the [Sourcegraph GraphQL debug API](/api/graphql/) is also available without any compatibility guarantees.

The Sourcegraph GraphQL API has historically been an internal interface diff --git a/docs/batch-changes/batch-spec-cheat-sheet.mdx b/docs/batch-changes/batch-spec-cheat-sheet.mdx index 27b48fcff..29b8b5004 100644 --- a/docs/batch-changes/batch-spec-cheat-sheet.mdx +++ b/docs/batch-changes/batch-spec-cheat-sheet.mdx @@ -82,7 +82,7 @@ changesetTemplate: # [...] # If we have an `outputs.projectName` we use it, otherwise we append the path - # of the workspace. If the path is emtpy (as is the case in the root folder), + # of the workspace. If the path is empty (as is the case in the root folder), # we ignore it. branch: | ${{ if eq outputs.projectName "" }} diff --git a/docs/batch-changes/quickstart.mdx b/docs/batch-changes/quickstart.mdx index 8e22b1d8f..6e95b65fd 100644 --- a/docs/batch-changes/quickstart.mdx +++ b/docs/batch-changes/quickstart.mdx @@ -99,7 +99,7 @@ The batch change's **changesets** still need to be published, which means they e So far, nothing has been created on your code hosts. To do so, you can tell Sourcegraph to either **publish** or **push** a changeset. - **[Publishing](/batch-changes/publishing-changesets)** a changeset results in the creation of a merge request on your code host (e.g. a Pull Request on GitHub). -- **[Pushing](/batch-changes/push-only-changesets)** a changeset (available on GitHub and GitLab only) results in pushing your code changes to a new branch on your code host without also creating a merge request. You are able to see any CI feedback set to trigger upon code-pushes in the Batch Changs UI. +- **[Pushing](/batch-changes/push-only-changesets)** a changeset (available on GitHub and GitLab only) results in pushing your code changes to a new branch on your code host without also creating a merge request. You are able to see any CI feedback set to trigger upon code-pushes in the Batch Changes UI. ### Configure code host credentials diff --git a/docs/batch-changes/server-side.mdx b/docs/batch-changes/server-side.mdx index 59f9b318b..c301fa1d8 100644 --- a/docs/batch-changes/server-side.mdx +++ b/docs/batch-changes/server-side.mdx @@ -6,7 +6,7 @@ Running Batch Changes server-side is in Experimental stage and comes with - certains [limitations](#limitations). + certain [limitations](#limitations). Batch Changes can use the Sourcegraph CLI in your local environment to [compute diffs](/batch-changes/how-src-executes-a-batch-spec) and create changesets. Local execution can be impractical for batch changes affecting hundreds or thousands of repositories, with large numbers of workspaces, or when batch change steps require CPU, memory, or disk resources that are unavailable locally. diff --git a/docs/cli/explanations/env.mdx b/docs/cli/explanations/env.mdx index 3e8add5bd..574ed609c 100644 --- a/docs/cli/explanations/env.mdx +++ b/docs/cli/explanations/env.mdx @@ -93,6 +93,6 @@ src search -get-curl 'repogroup:swarm' curl \ -H 'Authorization: token ' \ -H 'authorization: Bearer What did the judge say to the dentist? Do you swear to pull the tooth, the whole tooth and nothing but the tooth?' \ - -d '{"query":"fragment FileMatchFields on FileMatch {\n\t\t\t\trepository {\n\t\t\t\t\tname\n\t\t\t\t\turl\n\t\t\t\t}\n\t\t\t\tfile {\n\t\t\t\t\tname\n\t\t\t\t\tpath\n\t\t\t\t\turl\n\t\t\t\t\tcontent\n\t\t\t\t\tcommit {\n\t\t\t\t\t\toid\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tlineMatches {\n\t\t\t\t\tpreview\n\t\t\t\t\tlineNumber\n\t\t\t\t\toffsetAndLengths\n\t\t\t\t\tlimitHit\n\t\t\t\t}\n\t\t\t}\n\n\t\t\tfragment CommitSearchResultFields on CommitSearchResult {\n\t\t\t\tmessagePreview {\n\t\t\t\t\tvalue\n\t\t\t\t\thighlights{\n\t\t\t\t\t\tline\n\t\t\t\t\t\tcharacter\n\t\t\t\t\t\tlength\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tdiffPreview {\n\t\t\t\t\tvalue\n\t\t\t\t\thighlights {\n\t\t\t\t\t\tline\n\t\t\t\t\t\tcharacter\n\t\t\t\t\t\tlength\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tlabel {\n\t\t\t\t\thtml\n\t\t\t\t}\n\t\t\t\turl\n\t\t\t\tmatches {\n\t\t\t\t\turl\n\t\t\t\t\tbody {\n\t\t\t\t\t\thtml\n\t\t\t\t\t\ttext\n\t\t\t\t\t}\n\t\t\t\t\thighlights {\n\t\t\t\t\t\tcharacter\n\t\t\t\t\t\tline\n\t\t\t\t\t\tlength\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tcommit {\n\t\t\t\t\trepository {\n\t\t\t\t\t\tname\n\t\t\t\t\t}\n\t\t\t\t\toid\n\t\t\t\t\turl\n\t\t\t\t\tsubject\n\t\t\t\t\tauthor {\n\t\t\t\t\t\tdate\n\t\t\t\t\t\tperson {\n\t\t\t\t\t\t\tdisplayName\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t}\n\n\t\t fragment RepositoryFields on Repository {\n\t\t\tname\n\t\t\turl\n\t\t\texternalURLs {\n\t\t\t serviceType\n\t\t\t url\n\t\t\t}\n\t\t\tlabel {\n\t\t\t\thtml\n\t\t\t}\n\t\t }\n\n\t\t query ($query: String!) {\n\t\t\tsite {\n\t\t\t\tbuildVersion\n\t\t\t}\n\t\t\tsearch(query: $query) {\n\t\t\t results {\n\t\t\t\tresults{\n\t\t\t\t __typename\n\t\t\t\t ... on FileMatch {\n\t\t\t\t\t...FileMatchFields\n\t\t\t\t }\n\t\t\t\t ... on CommitSearchResult {\n\t\t\t\t\t...CommitSearchResultFields\n\t\t\t\t }\n\t\t\t\t ... on Repository {\n\t\t\t\t\t...RepositoryFields\n\t\t\t\t }\n\t\t\t\t}\n\t\t\t\tlimitHit\n\t\t\t\tcloning {\n\t\t\t\t name\n\t\t\t\t}\n\t\t\t\tmissing {\n\t\t\t\t name\n\t\t\t\t}\n\t\t\t\ttimedout {\n\t\t\t\t name\n\t\t\t\t}\n\t\t\t\tmatchCount\n\t\t\t\telapsedMilliseconds\n\t\t\t\t...SearchResultsAlertFields\n\t\t\t }\n\t\t\t}\n\t\t }\n\t\t\n\tfragment SearchResultsAlertFields on SearchResults {\n\t\talert {\n\t\t\ttitle\n\t\t\tdescription\n\t\t\tproposedQueries {\n\t\t\t\tdescription\n\t\t\t\tquery\n\t\t\t}\n\t\t}\n\t}\n","variables":{"query":"repogroup:swarm"}}' \ + -d '{"query":"fragment FileMatchFields on FileMatch {\n\t\t\t\trepository {\n\t\t\t\t\tname\n\t\t\t\t\turl\n\t\t\t\t}\n\t\t\t\tfile {\n\t\t\t\t\tname\n\t\t\t\t\tpath\n\t\t\t\t\turl\n\t\t\t\t\tcontent\n\t\t\t\t\tcommit {\n\t\t\t\t\t\toid\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tlineMatches {\n\t\t\t\t\tpreview\n\t\t\t\t\tlineNumber\n\t\t\t\t\toffsetAndLengths\n\t\t\t\t\tlimitHit\n\t\t\t\t}\n\t\t\t}\n\n\t\t\tfragment CommitSearchResultFields on CommitSearchResult {\n\t\t\t\tmessagePreview {\n\t\t\t\t\tvalue\n\t\t\t\t\thighlights{\n\t\t\t\t\t\tline\n\t\t\t\t\t\tcharacter\n\t\t\t\t\t\tlength\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tdiffPreview {\n\t\t\t\t\tvalue\n\t\t\t\t\thighlights {\n\t\t\t\t\t\tline\n\t\t\t\t\t\tcharacter\n\t\t\t\t\t\tlength\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tlabel {\n\t\t\t\t\thtml\n\t\t\t\t}\n\t\t\t\turl\n\t\t\t\tmatches {\n\t\t\t\t\turl\n\t\t\t\t\tbody {\n\t\t\t\t\t\thtml\n\t\t\t\t\t\ttext\n\t\t\t\t\t}\n\t\t\t\t\thighlights {\n\t\t\t\t\t\tcharacter\n\t\t\t\t\t\tline\n\t\t\t\t\t\tlength\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t\tcommit {\n\t\t\t\t\trepository {\n\t\t\t\t\t\tname\n\t\t\t\t\t}\n\t\t\t\t\toid\n\t\t\t\t\turl\n\t\t\t\t\tsubject\n\t\t\t\t\tauthor {\n\t\t\t\t\t\tdate\n\t\t\t\t\t\tperson {\n\t\t\t\t\t\t\tdisplayName\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t\t\t}\n\t\t\t}\n\n\t\t fragment RepositoryFields on Repository {\n\t\t\tname\n\t\t\turl\n\t\t\texternalURLs {\n\t\t\t serviceType\n\t\t\t url\n\t\t\t}\n\t\t\tlabel {\n\t\t\t\thtml\n\t\t\t}\n\t\t }\n\n\t\t query ($query: String!) {\n\t\t\tsite {\n\t\t\t\tbuildVersion\n\t\t\t}\n\t\t\tsearch(query: $query) {\n\t\t\t results {\n\t\t\t\tresults{\n\t\t\t\t __typename\n\t\t\t\t ... on FileMatch {\n\t\t\t\t\t...FileMatchFields\n\t\t\t\t }\n\t\t\t\t ... on CommitSearchResult {\n\t\t\t\t\t...CommitSearchResultFields\n\t\t\t\t }\n\t\t\t\t ... on Repository {\n\t\t\t\t\t...RepositoryFields\n\t\t\t\t }\n\t\t\t\t}\n\t\t\t\tlimitHit\n\t\t\t\tcloning {\n\t\t\t\t name\n\t\t\t\t}\n\t\t\t\tmissing {\n\t\t\t\t name\n\t\t\t\t}\n\t\t\t\timedout {\n\t\t\t\t name\n\t\t\t\t}\n\t\t\t\tmatchCount\n\t\t\t\telapsedMilliseconds\n\t\t\t\t...SearchResultsAlertFields\n\t\t\t }\n\t\t\t}\n\t\t }\n\t\t\n\tfragment SearchResultsAlertFields on SearchResults {\n\t\talert {\n\t\t\ttitle\n\t\t\tdescription\n\t\t\tproposedQueries {\n\t\t\t\tdescription\n\t\t\t\tquery\n\t\t\t}\n\t\t}\n\t}\n","variables":{"query":"repogroup:swarm"}}' \ https://cse-k8s.sgdev.org/.api/graphql ``` diff --git a/docs/code-insights/explanations/current-limitations-of-code-insights.mdx b/docs/code-insights/explanations/current-limitations-of-code-insights.mdx index 1484686eb..510610108 100644 --- a/docs/code-insights/explanations/current-limitations-of-code-insights.mdx +++ b/docs/code-insights/explanations/current-limitations-of-code-insights.mdx @@ -112,7 +112,7 @@ Because these insights need to run dramatically fewer queries than insights over - **[Released] Editing data series queries after creation**: available in 3.35+ ~~for insights over all repositories, you must make a new insight if you wish to run a different query~~ - **[Released] "Diff click"**: available in 3.36+ ~~click a datapoint on your insight and be taken to a diff search showing any changes contributing to the difference between a datapoint and the prior one~~ -> NOTE: many of the above-listed features will become available for insights over all repositories as well. The above list is ordererd top-down, where items on the top of the list will arrive roughly sooner than items on the bottom. +> NOTE: many of the above-listed features will become available for insights over all repositories as well. The above list is ordered top-down, where items on the top of the list will arrive roughly sooner than items on the bottom. ### Limitations specific to "Detect and track patterns" insights (automatically generated data series) diff --git a/docs/code-navigation/auto-indexing-configuration.mdx b/docs/code-navigation/auto-indexing-configuration.mdx index f2e06f115..c89272953 100644 --- a/docs/code-navigation/auto-indexing-configuration.mdx +++ b/docs/code-navigation/auto-indexing-configuration.mdx @@ -88,7 +88,7 @@ Note: `sourcegraph/scip-typescript` does not define a Docker entrypoint, so we n "root": "editors/code" } ], - "indexer": "sourcegraph/scip-typescript:autoiondex", + "indexer": "sourcegraph/scip-typescript:autoindex", "indexer_args": ["scip-typescript", "index"], "root": "editors/code" } diff --git a/docs/code-navigation/writing-an-indexer.mdx b/docs/code-navigation/writing-an-indexer.mdx index b7131e927..176b42bc2 100644 --- a/docs/code-navigation/writing-an-indexer.mdx +++ b/docs/code-navigation/writing-an-indexer.mdx @@ -68,7 +68,7 @@ You can inspect the Protobuf output using `protoc`: protoc --decode=scip.Index scip.proto < index.scip ``` -For robust testing, it's recommended making sure that the result of indexing is deterministic. One potential source of issues here is non-determinstic iteration over the key-value pairs of a hash table. If re-running your indexer changes the order in which occurrences are emitted, snapshot testing may report different results. +For robust testing, it's recommended making sure that the result of indexing is deterministic. One potential source of issues here is non-deterministic iteration over the key-value pairs of a hash table. If re-running your indexer changes the order in which occurrences are emitted, snapshot testing may report different results. ## Snapshot testing with scip CLI diff --git a/docs/code-ownership/index.mdx b/docs/code-ownership/index.mdx index 6eb3a79ba..f1fa83f4a 100644 --- a/docs/code-ownership/index.mdx +++ b/docs/code-ownership/index.mdx @@ -23,7 +23,7 @@ Code ownership is set via [the `CODEOWNERS` format](/code-ownership/codeowners-f The ownership information is available for browsing once ownership data is available through [a `CODEOWNERS` file](#code-ownership). -When displaying a source file, there is an "Owernship" button at the bottom. Clicking it will open the "Owernship" panel. +When displaying a source file, there is an "Ownership" button at the bottom. Clicking it will open the "Ownership" panel. ![File view with the ownership tab selected in the bottom panel](https://storage.googleapis.com/sourcegraph-assets/docs/own/blob-view-panel-v2.png) diff --git a/docs/code-search/working/saved-searches.mdx b/docs/code-search/working/saved-searches.mdx index a9dafdbf2..8b3433978 100644 --- a/docs/code-search/working/saved-searches.mdx +++ b/docs/code-search/working/saved-searches.mdx @@ -8,7 +8,7 @@ Saved Searches lets you reuse and share search queries. You can create a saved s Saved Searches functionality is available to both Free and Enterprise Code Search users. To access or create new Saved Searches in the Sourcegraph web app, click the **Tools > Saved Searches** in the top navigation bar. -![saved-searhces](https://storage.googleapis.com/sourcegraph-assets/Docs/saved-searches-2025.png) +![saved-searches](https://storage.googleapis.com/sourcegraph-assets/Docs/saved-searches-2025.png) ## Creating saved searches diff --git a/docs/cody/clients/install-jetbrains.mdx b/docs/cody/clients/install-jetbrains.mdx index fe9451c9b..1d9d12b45 100644 --- a/docs/cody/clients/install-jetbrains.mdx +++ b/docs/cody/clients/install-jetbrains.mdx @@ -127,7 +127,7 @@ Cody's chat allows you to add files as context in your messages. The `@-file` also supports line numbers to query the context of large files. You can add ranges of large files to your context by @-mentioning a large file and appending a number range to the filename, for example, `@filepath/filename:1-10`. -When you `@-mention` files to add to Cody’s context window, the file lookup takes `files.exclude`, `search.exclude`, and `.gitgnore` files into account. This makes the file search faster as a result up to 100ms. +When you `@-mention` files to add to Cody’s context window, the file lookup takes `files.exclude`, `search.exclude`, and `.gitignore` files into account. This makes the file search faster as a result up to 100ms. Moreover, when you `@-mention` files, Cody will track the number of characters in those files against the context window limit of the selected chat model. As you `@-mention` multiple files, Cody will calculate how many tokens of the context window remain. When the remaining context window size becomes too small, you'll receive **File too large** errors when attempting to `@-mention` additional files. diff --git a/docs/cody/clients/install-vscode.mdx b/docs/cody/clients/install-vscode.mdx index 1b139eb48..ad3e5b321 100644 --- a/docs/cody/clients/install-vscode.mdx +++ b/docs/cody/clients/install-vscode.mdx @@ -164,7 +164,7 @@ Cody's chat allows you to add files and symbols as context in your messages. The `@-file` also supports line numbers to query the context of large files. You can add ranges of large files to your context by @-mentioning a large file and appending a number range to the filename, for example, `@filepath/filename:1-10`. -When you `@-mention` files to add to Cody’s context window, the file lookup takes `files.exclude`, `search.exclude`, and `.gitgnore` files into account. This makes the file search faster as a result up to 100ms. +When you `@-mention` files to add to Cody’s context window, the file lookup takes `files.exclude`, `search.exclude`, and `.gitignore` files into account. This makes the file search faster as a result up to 100ms. Moreover, when you `@-mention` files, Cody will track the number of characters in those files against the context window limit of the selected chat model. As you `@-mention` multiple files, Cody will calculate how many tokens of the context window remain. When the remaining context window size becomes too small, you'll receive **File too large** errors when attempting to `@-mention` additional files. diff --git a/docs/cody/enterprise/model-config-examples.mdx b/docs/cody/enterprise/model-config-examples.mdx index d9bc56e96..3a4735f69 100644 --- a/docs/cody/enterprise/model-config-examples.mdx +++ b/docs/cody/enterprise/model-config-examples.mdx @@ -803,7 +803,7 @@ See also [Debugging: running a latency test](#debugging-running-a-latency-test). ### Debugging: Running a latency test - Debugging latency optimizated inference is supported in Sourcegraph v6.5 and + Debugging latency-optimized inference is supported in Sourcegraph v6.5 and more. diff --git a/docs/cody/use-cases/vsc-tutorial.mdx b/docs/cody/use-cases/vsc-tutorial.mdx index 54cf6f384..829b58963 100644 --- a/docs/cody/use-cases/vsc-tutorial.mdx +++ b/docs/cody/use-cases/vsc-tutorial.mdx @@ -51,7 +51,7 @@ You can also use the default keyboard shortcut of `Opt+K`/`Alt+K`. **✨ Pro-tips for code editing with Cody** -- You can open the 💡 menu, with an "Cody: Edit Code" option, by selecting any line of code and using the keyboard short `Command` `.` on macOS or `Crtl` `.` on Windows & Linux. +- You can open the 💡 menu, with an "Cody: Edit Code" option, by selecting any line of code and using the keyboard short `Command` `.` on macOS or `Ctrl` `.` on Windows & Linux. - If you start an empty line and open the 💡 menu (using the keyboard short `Command` `.` on macOS or `Ctrl` `.` on Windows & Linux) you can use "Cody: Generate Code" to generate new lines of code based on instructions. - You define your own custom code editing commands using [Custom Commands (Beta)](https://sourcegraph.com/docs/cody/custom-commands), by setting the [`commands..mode` property](https://sourcegraph.com/docs/cody/capabilities/commands#commands-id-mode). @@ -83,7 +83,7 @@ Something wrong with your code? Use Cody’s "Ask Cody to Fix" command to fix it **✨ Pro-tips for fixing code with Cody** -- You can open the 💡 menu, with an "Ask Cody to Fix" option, by moving the cursor over any line of code with an error and using the keyboard short `Command` `.` on macOS or `Crtl` `.` on Windows & Linux. +- You can open the 💡 menu, with an "Ask Cody to Fix" option, by moving the cursor over any line of code with an error and using the keyboard short `Command` `.` on macOS or `Ctrl` `.` on Windows & Linux. - You can also right click on any items in the "Problems" tab of VS Code and select "Ask Cody to Fix" ## Keyboard Shortcuts diff --git a/docs/self-hosted/deploy/docker-compose/azure.mdx b/docs/self-hosted/deploy/docker-compose/azure.mdx index 27e0684a4..c3da09d1b 100644 --- a/docs/self-hosted/deploy/docker-compose/azure.mdx +++ b/docs/self-hosted/deploy/docker-compose/azure.mdx @@ -56,7 +56,7 @@ Click `Create and attach a new disk` to create **two** disks: #### Management -- RECOMMENDED Endable backup +- RECOMMENDED Enable backup #### Advanced diff --git a/docs/self-hosted/deploy/docker-compose/operations.mdx b/docs/self-hosted/deploy/docker-compose/operations.mdx index 7e48e0102..1e93ce31f 100644 --- a/docs/self-hosted/deploy/docker-compose/operations.mdx +++ b/docs/self-hosted/deploy/docker-compose/operations.mdx @@ -119,7 +119,7 @@ docker cp codeinsights_db.out codeinsights-db:/tmp/codeinsights_db.out ```bash docker exec pgsql sh -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/sourcegraph_db.out sg' -docker exec codeintel-db sh -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/condeintel_db.out sg' +docker exec codeintel-db sh -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/codeintel_db.out sg' docker exec codeinsights-db sh -c 'psql -v ERROR_ON_STOP=1 --username postgres -f /tmp/codeinsights_db.out postgres' ``` @@ -188,7 +188,7 @@ docker cp codeinsights_db.out codeinsights-db:/tmp/codeinsights_db.out ```bash docker exec pgsql sh -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/sourcegraph_db.out sg' -docker exec codeintel-db sh -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/condeintel_db.out sg' +docker exec codeintel-db sh -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/codeintel_db.out sg' docker exec codeinsights-db sh -c 'psql -v ERROR_ON_STOP=1 --username postgres -f /tmp/codeinsights_db.out postgres' ``` diff --git a/docs/self-hosted/deploy/kubernetes/kustomize/migrate.mdx b/docs/self-hosted/deploy/kubernetes/kustomize/migrate.mdx index 8991c6088..ed328c5c5 100644 --- a/docs/self-hosted/deploy/kubernetes/kustomize/migrate.mdx +++ b/docs/self-hosted/deploy/kubernetes/kustomize/migrate.mdx @@ -163,7 +163,7 @@ resources: Follow our [configuration guide](/self-hosted/deploy/kubernetes/configure) to recreate your running instance with the provided components. -It is recommended to refrain from introducing any changes to the characteristics of a running Kubernetes cluster during a migration. For example, if the cluster is currently running in privileged mode with root user access, deploying the instance in non-privileized mode could cause permission errors. +It is recommended to refrain from introducing any changes to the characteristics of a running Kubernetes cluster during a migration. For example, if the cluster is currently running in privileged mode with root user access, deploying the instance in non-privileged mode could cause permission errors. Ensure the following configurations are present/ consistent for your Sourcegraph instance during migrations: diff --git a/docs/self-hosted/deploy/kubernetes/operations.mdx b/docs/self-hosted/deploy/kubernetes/operations.mdx index cd1842eab..b3d960ca6 100644 --- a/docs/self-hosted/deploy/kubernetes/operations.mdx +++ b/docs/self-hosted/deploy/kubernetes/operations.mdx @@ -312,7 +312,7 @@ D. Restore the databases ```bash $ kubectl exec -it $pgsql_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/sourcegraph_db.out sg' -$ kubectl exec -it $codeintel-db_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/condeintel_db.out sg' +$ kubectl exec -it $codeintel-db_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/codeintel_db.out sg' $ kubectl exec -it $codeinsights-db_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username postgres -f /tmp/codeinsights_db.out postgres' ``` @@ -379,7 +379,7 @@ F. Restore the databases ```bash $ kubectl exec -it $pgsql_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/sourcegraph_db.out sg' -$ kubectl exec -it $codeintel-db_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/condeintel_db.out sg' +$ kubectl exec -it $codeintel-db_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username sg -f /tmp/codeintel_db.out sg' $ kubectl exec -it $codeinsights-db_POD_NAME -- bash -c 'psql -v ERROR_ON_STOP=1 --username postgres -f /tmp/codeinsights_db.out postgres' ``` diff --git a/docs/self-hosted/deploy/machine-images/aws-ami.mdx b/docs/self-hosted/deploy/machine-images/aws-ami.mdx index ad94fdf70..7fbd5d40c 100644 --- a/docs/self-hosted/deploy/machine-images/aws-ami.mdx +++ b/docs/self-hosted/deploy/machine-images/aws-ami.mdx @@ -80,7 +80,7 @@ helm upgrade -i -f ./override.yaml --version "$(cat /home/ec2-user/.sourcegraph- 1. Add the following to the site-admin config using the password you chose previously ``` -"executors.accessToken": "", +"executors.accessToken": "", "executors.frontendURL": "http://sourcegraph-frontend:30080", "codeIntelAutoIndexing.enabled": true ``` diff --git a/docs/self-hosted/deploy/machine-images/aws-oneclick.mdx b/docs/self-hosted/deploy/machine-images/aws-oneclick.mdx index 80075727d..1410b32e3 100644 --- a/docs/self-hosted/deploy/machine-images/aws-oneclick.mdx +++ b/docs/self-hosted/deploy/machine-images/aws-oneclick.mdx @@ -92,7 +92,7 @@ helm upgrade -i -f ./override.yaml --version "$(cat /home/ec2-user/.sourcegraph- 1. Adding the following to the site-admin config using the password you chose previously ```curl -"executors.accessToken": "", +"executors.accessToken": "", "executors.frontendURL": "http://sourcegraph-frontend:30080", "codeIntelAutoIndexing.enabled": true ``` diff --git a/docs/self-hosted/deploy/machine-images/gce.mdx b/docs/self-hosted/deploy/machine-images/gce.mdx index 8ffc83447..63b7e2b0e 100644 --- a/docs/self-hosted/deploy/machine-images/gce.mdx +++ b/docs/self-hosted/deploy/machine-images/gce.mdx @@ -132,7 +132,7 @@ helm upgrade -i -f ./override.yaml --version "$(cat /home/sourcegraph/.sourcegra 1. Add the following to the site-admin config using the password you chose previously: ``` -"executors.accessToken": "", +"executors.accessToken": "", "executors.frontendURL": "http://sourcegraph-frontend:30080", "codeIntelAutoIndexing.enabled": true ``` diff --git a/docs/self-hosted/deploy/scale.mdx b/docs/self-hosted/deploy/scale.mdx index 6dd0ef427..4ba657a1f 100644 --- a/docs/self-hosted/deploy/scale.mdx +++ b/docs/self-hosted/deploy/scale.mdx @@ -44,7 +44,7 @@ A list of services that can be externalized. See our docs on [Using external ser | :------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`codeinsights-db`](/self-hosted/deploy/scale#codeinsights-db) | A PostgreSQL instance for storing code insights data. | | [`codeintel-db`](/self-hosted/deploy/scale#codeintel-db) | A PostgreSQL instance for storing large-volume code graph data. | -| [`jaeger`](/self-hosted/deploy/scale#jeager) | A Jaeger instance for end-to-end distributed tracing. | +| [`jaeger`](/self-hosted/deploy/scale#jaeger) | A Jaeger instance for end-to-end distributed tracing. | | [`blobstore`](/self-hosted/deploy/scale#blobstore) | A blobstore instance that serves as a local S3-compatible object storage to hold user uploads for code-intel before they can be processed. | | [`pgsql`](/self-hosted/deploy/scale#pgsql) | A PostgreSQL instance for storing long-term information, such as user information when using Sourcegraph’s built-in authentication provider instead of an external one. | | [`redis-cache`](/self-hosted/deploy/scale#redis-cache) | A Redis instance for storing cache data. | @@ -281,7 +281,7 @@ It is shipped with customized dashboards for Sourcegraph services. --- -### jeager +### jaeger ``` A Jaeger instance for end-to-end distributed tracing @@ -627,7 +627,7 @@ Runs a collection of background jobs periodically in response to internal reques | Memory | | | :---------- | :------------------------------------------------------------- | -| `Overview` | Abulating search results to generate Code Insights time series | +| `Overview` | Tabulating search results to generate Code Insights time series | | `Factors` | Number of repositories | | | Number of insight series defined | | `Guideline` | Grow with the number of repositories and code-insight users | diff --git a/docs/self-hosted/observability/troubleshooting.mdx b/docs/self-hosted/observability/troubleshooting.mdx index 98ae3255f..4b0fa957b 100644 --- a/docs/self-hosted/observability/troubleshooting.mdx +++ b/docs/self-hosted/observability/troubleshooting.mdx @@ -202,7 +202,7 @@ $ sysctl -n vm.max_map_count 1. Calculate the number of repos in your deployment divided by the number of `indexed-search` replicas. For example: - - 250,000 repositories / 2 indexed-search repliacas = 125,000 repos to index per replica. + - 250,000 repositories / 2 indexed-search replicas = 125,000 repos to index per replica. 1. If the `vm.max_map_count` is lower than the result of the above calculation. Adjust the `vm.max_map_count` by executing: diff --git a/docs/self-hosted/updates/migrator/downgrading.mdx b/docs/self-hosted/updates/migrator/downgrading.mdx index 77ae206a3..f1fc219a7 100644 --- a/docs/self-hosted/updates/migrator/downgrading.mdx +++ b/docs/self-hosted/updates/migrator/downgrading.mdx @@ -8,7 +8,7 @@ Sourcegraph guarantees database backward compatibility to the most recent minor In practice downgrading a Sourcegraph instance should always be a last option. Some versions of Sourcegraph apply out of band migrations which are irreversible and data loss may result. **We highly recommend creating a database backup before proceeding with an upgrade**. -> Note: As a percaution its advised that after any downgrade the databases are checked with the `migrator` [`drift` command](/self-hosted/updates/migrator/migrator-operations#drift) to identify any problems reversing migrations. +> Note: As a precaution it's advised that after any downgrade the databases are checked with the `migrator` [`drift` command](/self-hosted/updates/migrator/migrator-operations#drift) to identify any problems reversing migrations. If ever you are uncertain about a downgrade please reach out to us at [support@sourcegraph.com](mailto:support@sourcegraph.com) @@ -51,7 +51,7 @@ $ ~/deploy-sourcegraph-docker/docker-compose/ v4.5.1* docker logs migrator Downgrade is run using a similar to procedure to a [multiversion upgrade](/self-hosted/updates/#upgrades-index): - Services that connect to the databases must be disabled before running `downgrade` -- Manifests must be reverted to the version you are downgrading to and reapplyed **after** the `downgrade` is complete. +- Manifests must be reverted to the version you are downgrading to and reapplied **after** the `downgrade` is complete. ## Rolling back a standard upgrade diff --git a/docs/self-hosted/updates/migrator/migrator-operations.mdx b/docs/self-hosted/updates/migrator/migrator-operations.mdx index ccf26e4d4..0598b482b 100644 --- a/docs/self-hosted/updates/migrator/migrator-operations.mdx +++ b/docs/self-hosted/updates/migrator/migrator-operations.mdx @@ -85,7 +85,7 @@ upgrade \ **Required arguments**: - `--from`: The current Sourcegraph release version (_without the patch_; e.g., `v3.36`) -- `--to`: The target Sorucegraph release version (_without the patch_; e.g., `v4.0`) +- `--to`: The target Sourcegraph release version (_without the patch_; e.g., `v4.0`) **Optional arguments**: @@ -143,7 +143,7 @@ downgrade \ **Required arguments**: - `--from`: The current Sourcegraph release version (_without the patch_; e.g., `v3.36`) -- `--to`: The target Sorucegraph release version (_without the patch_; e.g., `v4.0`) +- `--to`: The target Sourcegraph release version (_without the patch_; e.g., `v4.0`) **Optional arguments**: diff --git a/docs/self-hosted/updates/migrator/upgrading-early-versions.mdx b/docs/self-hosted/updates/migrator/upgrading-early-versions.mdx index 4079c15c0..601e32b70 100644 --- a/docs/self-hosted/updates/migrator/upgrading-early-versions.mdx +++ b/docs/self-hosted/updates/migrator/upgrading-early-versions.mdx @@ -9,7 +9,7 @@ Reminders: ## Before v4.0.0 -The `upgrade` `migrator` command is introduced in `v4.0.0`, just remember to use the latest version of the `migrator` image released during a multiversion upgrade and you'll have access to the most up to date `migtrator` commands. +The `upgrade` `migrator` command is introduced in `v4.0.0`, just remember to use the latest version of the `migrator` image released during a multiversion upgrade and you'll have access to the most up to date `migrator` commands. ## Before v3.37.0 diff --git a/src/components/Icon.tsx b/src/components/Icon.tsx index a487c2bc4..248cf4b57 100644 --- a/src/components/Icon.tsx +++ b/src/components/Icon.tsx @@ -8,7 +8,7 @@ import {ThemingIcon} from '@/components/icons/ThemingIcon'; import {WarningIcon} from '@/components/icons/WarningIcon'; import {CodyIcon} from '@/components/icons/CodyIcon'; import {CodeSearchIcon} from './icons/CodeSearchIcon'; -import {PluginsIcon} from './icons/PuginsIcon'; +import {PluginsIcon} from './icons/PluginsIcon'; import {CodeGraphIcon} from './icons/CodeGraphIcon'; import {LanguageModelsIcon} from './icons/LanguageModels'; import {SecurityIcon} from './icons/SecurityIcon'; diff --git a/src/components/icons/PuginsIcon.tsx b/src/components/icons/PluginsIcon.tsx similarity index 100% rename from src/components/icons/PuginsIcon.tsx rename to src/components/icons/PluginsIcon.tsx diff --git a/src/data/redirects.ts b/src/data/redirects.ts index 9b32767a7..e480a4195 100644 --- a/src/data/redirects.ts +++ b/src/data/redirects.ts @@ -4475,7 +4475,7 @@ const redirectsData = [ destination: '/cody/capabilities/prompts' }, - //Eclispe redirects + //Eclipse redirects { source: '/cody/clients/install-eclipse', destination: '/cody/clients' @@ -4554,13 +4554,13 @@ const redirectsData = [ destination: '/cody/capabilities/agentic-context-fetching' }, - //Rmv embeddings permanentaly:https://sourcegraph.com/docs/cody/core-concepts/embeddings + //Rmv embeddings permanently:https://sourcegraph.com/docs/cody/core-concepts/embeddings { source: '/cody/core-concepts/embeddings', destination: '/cody/' }, - //Rmv Query types permanentaly:https://sourcegraph.com/docs/cody/capabilities/query-types + //Rmv Query types permanently:https://sourcegraph.com/docs/cody/capabilities/query-types { source: '/cody/capabilities/query-types', destination: '/cody/capabilities/chat'