diff --git a/app/not-found.tsx b/app/not-found.tsx index 901e6a71adf81..a08daad34eb14 100644 --- a/app/not-found.tsx +++ b/app/not-found.tsx @@ -35,7 +35,7 @@ export default function NotFound() {
diff --git a/develop-docs/engineering-practices/code-review.mdx b/develop-docs/engineering-practices/code-review.mdx index 54719abffb6c4..4e14e9bea2324 100644 --- a/develop-docs/engineering-practices/code-review.mdx +++ b/develop-docs/engineering-practices/code-review.mdx @@ -204,7 +204,7 @@ Please be pragmatic, and consider the cost of each incremental request for chang - We’re a team – *[we ride together, we die together](https://www.youtube.com/watch?v=1d5Q0vXbODs)* – and you need to unblock other developers so that we can all move forward. - We recommend checking for open code reviews at the start and end of every day. -- [Github's Review Requests tab](https://github.com/pulls/review-requested) can be a helpful place to keep track of these. +- [GitHub's Review Requests tab](https://github.com/pulls/review-requested) can be a helpful place to keep track of these. ### Example of a *pretty good* code review diff --git a/develop-docs/integrations/github.mdx b/develop-docs/integrations/github.mdx index 095165c1b88b8..314cb494ca424 100644 --- a/develop-docs/integrations/github.mdx +++ b/develop-docs/integrations/github.mdx @@ -5,7 +5,7 @@ sidebar_title: GitHub ## Create a GitHub App -To configure the GitHub integration you'll need to create a GitHub app and obtain credentials. Installation will fail if your Github App's name contains spaces. +To configure the GitHub integration you'll need to create a GitHub app and obtain credentials. Installation will fail if your GitHub App's name contains spaces. The GitHub App name and GitHub Org Slug must not contain any spaces. diff --git a/develop-docs/sdk/platform-specifics/javascript-sdks/index.mdx b/develop-docs/sdk/platform-specifics/javascript-sdks/index.mdx index c5da93494c6c2..096e34dd0ee5e 100644 --- a/develop-docs/sdk/platform-specifics/javascript-sdks/index.mdx +++ b/develop-docs/sdk/platform-specifics/javascript-sdks/index.mdx @@ -9,7 +9,7 @@ This Section contains JavaScript SDK-specific information that's useful for deve If you're looking to contribute new features to the SDK or want to understand what data you can consume from the JS SDK, this is the right place to start. The JS SDK team encourages community or cross-team contributions to the SDK and is happy to help you get started. -Please reach out to the SDK team (on [Github](https://github.com/getsentry/sentry-javascript) or internally in Slack `#discuss-javascript`) if you have questions, concerns or plan on building a larger feature. +Please reach out to the SDK team (on [GitHub](https://github.com/getsentry/sentry-javascript) or internally in Slack `#discuss-javascript`) if you have questions, concerns or plan on building a larger feature. diff --git a/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx b/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx index 2a0fd1d074031..218c9e1cf657a 100644 --- a/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx +++ b/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx @@ -47,7 +47,7 @@ Both these layers include the latest Sentry JavaScript SDK (or Python SDK). ### Building of the Python Layer The contents of the Layer directory for the Python layer are built during the -"CI" workflow in Github actions. The steps necessary can be found +"CI" workflow in GitHub actions. The steps necessary can be found [here](https://github.com/getsentry/sentry-python/blob/master/.github/workflows/ci.yml). This will prepare the Lambda layer directory, compress everything and upload the resulting zip file as @@ -65,7 +65,7 @@ release of the Python SDK. ### Building of the JavaScript/Node Layer The contents of the Layer directory for the JavaScript/Node layer are built during the -"Build & Test" workflow in Github actions. The steps necessary can be found +"Build & Test" workflow in GitHub actions. The steps necessary can be found [here](https://github.com/getsentry/sentry-javascript/blob/master/.github/workflows/build.yml). This will prepare the Lambda layer directory, compress everything and upload the resulting zip file as diff --git a/docs/organization/integrations/source-code-mgmt/github/index.mdx b/docs/organization/integrations/source-code-mgmt/github/index.mdx index ad285bf05ae15..455bedd72cd54 100644 --- a/docs/organization/integrations/source-code-mgmt/github/index.mdx +++ b/docs/organization/integrations/source-code-mgmt/github/index.mdx @@ -280,15 +280,15 @@ This feature requires [code mappings](/product/issues/suspect-commits/#2-set-up- ### Missing Member Detection -If there are users committing to Github repositories linked to Sentry and they're not members of your organization, Sentry detects them as missing members. Once a month, Sentry sends organization owners and managers an email reminding them to invite those users to join their org. Sentry also shows a banner to invite missing members in the **Settings > Members** page. +If there are users committing to GitHub repositories linked to Sentry and they're not members of your organization, Sentry detects them as missing members. Once a month, Sentry sends organization owners and managers an email reminding them to invite those users to join their org. Sentry also shows a banner to invite missing members in the **Settings > Members** page. -![Github missing members invite banner](./img/github-missing-members-banner.png) +![GitHub missing members invite banner](./img/github-missing-members-banner.png) The banner shows the 5 most active contributors that are not yet in the organization. To see all missing members (up to 50), click "View All" in the banner. To snooze the banner, click the ellipsis, then select "Hide Missing Members". Clicking "View All" on the invite banner will display the invite modal. From here, you can select multiple users and assign roles and teams before inviting them. -![Github missing members invite modal](./img/github-missing-members-modal.png) +![GitHub missing members invite modal](./img/github-missing-members-modal.png) By default, this feature is automatically enabled once your GitHub integration has been set up. To disable it, go to **Settings > Integrations > GitHub** and toggle it off. diff --git a/docs/platforms/javascript/common/session-replay/configuration.mdx b/docs/platforms/javascript/common/session-replay/configuration.mdx index afd2c7703dd21..eae501177f66b 100644 --- a/docs/platforms/javascript/common/session-replay/configuration.mdx +++ b/docs/platforms/javascript/common/session-replay/configuration.mdx @@ -125,7 +125,7 @@ To solve these problems, we provide the ability to use a custom worker script. T Follow these steps in order to use a custom compression worker: -1. Download the [example worker script](https://github.com/getsentry/sentry-javascript/blob/develop/packages/replay-worker/examples/worker.min.js) from our Github repository. +1. Download the [example worker script](https://github.com/getsentry/sentry-javascript/blob/develop/packages/replay-worker/examples/worker.min.js) from our GitHub repository. 2. Host this worker script on the same domain as your application. For example, if your application is hosted at `https://example.com`, you could host the worker script at `https://example.com/assets/worker.min.js`. 3. Configure your custom worker script in Replay: diff --git a/docs/product/index.mdx b/docs/product/index.mdx index aa79177d015ab..ffc34c82904db 100644 --- a/docs/product/index.mdx +++ b/docs/product/index.mdx @@ -67,7 +67,7 @@ Our [**LLM Monitoring**](/product/insights/llm-monitoring/) feature gives you in Sentry provides many [**integrations**](/organization/integrations/) to support a seamless developer workflow, including: - [Source code management](/organization/integrations/source-code-mgmt/), code mapping, code owners, and suspect commits with GitHub, GitLab, Azure DevOps, and Bitbucket. -- [Issue tracking](/organization/integrations/issue-tracking/) with Jira, Github, and many other tools. +- [Issue tracking](/organization/integrations/issue-tracking/) with Jira, GitHub, and many other tools. - [Alerts and notifications](/organization/integrations/notification-incidents/) with Slack, Discord, PagerDuty, and more. ### SDK Support for Over 100 Platforms diff --git a/docs/product/insights/frontend/assets.mdx b/docs/product/insights/frontend/assets.mdx index e82220d285571..192dc203e0d4f 100644 --- a/docs/product/insights/frontend/assets.mdx +++ b/docs/product/insights/frontend/assets.mdx @@ -120,7 +120,7 @@ The following tokens will be replaced with \* within a asset url Asset parametrization is still a work-in-progress. As these improvements are made, you will will temporarily see instances of the new and old groupings in your Asset Module. -Let us know of any feedback through Github Issues. +Let us know of any feedback through GitHub Issues. diff --git a/includes/feature-stage-beta-uptime.mdx b/includes/feature-stage-beta-uptime.mdx index e1a6a3aaece43..18e61f42c2bac 100644 --- a/includes/feature-stage-beta-uptime.mdx +++ b/includes/feature-stage-beta-uptime.mdx @@ -1,6 +1,6 @@ Sentry Uptime Monitoring is currently in open beta, so be gentle - features are still in-progress and may have bugs. We recognize the irony. -For any questions or feedback, you can reach us on [Github Discussions](https://github.com/getsentry/sentry/discussions/78100). +For any questions or feedback, you can reach us on [GitHub Discussions](https://github.com/getsentry/sentry/discussions/78100).