From 4fd27a72601281e189e30bc1fece442e56854702 Mon Sep 17 00:00:00 2001
From: eyesofish <110754016+eyesofish@users.noreply.github.com>
Date: Fri, 21 Aug 2026 12:31:07 +0800
Subject: [PATCH] docs: Fix duplicate word in organization setup guide

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 docs/organization/getting-started/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/organization/getting-started/index.mdx b/docs/organization/getting-started/index.mdx
index 2c117634b7424..3794c0849ff5e 100644
--- a/docs/organization/getting-started/index.mdx
+++ b/docs/organization/getting-started/index.mdx
@@ -80,7 +80,7 @@ If you're using a different SCM provider or don't want Sentry to connect to your
 
 Enabling an integration with your issue tracking solution allows you to create a new issue from within the **Issue Details** page in [sentry.io](https://sentry.io), or link to an existing one. GitHub, GitLab, and Bitbucket issues are associated with their respective SCM integrations. Sentry also integrates with [Azure DevOps](/integrations/source-code-mgmt/azure-devops/), [Shortcut](/integrations/issue-tracking/shortcut/), [Jira](/integrations/issue-tracking/jira/), and others.
 
-For a list of all supported integrations, check out out our [full Integrations documentation](/integrations/).
+For a list of all supported integrations, check out our [full Integrations documentation](/integrations/).
 
 You can set up automated issue management when you create alerts that route to [Azure DevOps](/integrations/source-code-mgmt/azure-devops/#automatically) and [Jira](/integrations/issue-tracking/jira/#automatically). External issues will be created for new Sentry issues on your behalf, and these issues will use the configured fields in your Azure DevOps or Jira workspace. For other issue tracking solutions, you can manually link Sentry issues.