diff --git a/docs/organization/integrations/issue-tracking/jira/index.mdx b/docs/organization/integrations/issue-tracking/jira/index.mdx
index 833b735d1e15e..97446fdcecffd 100644
--- a/docs/organization/integrations/issue-tracking/jira/index.mdx
+++ b/docs/organization/integrations/issue-tracking/jira/index.mdx
@@ -52,42 +52,44 @@ openssl x509 -pubkey -noout -in jira_publickey.cer > jira_publickey.pem
1. In the resulting dialog, fill out the form as follows:
-
- Application Name |
- Sentry |
-
-
- Application Type |
- Generic Application |
-
-
- Service Provider Name |
- Sentry |
-
-
- Consumer Key |
- (your choice, but keep this handy for the next step) |
-
-
- Shared Secret |
- sentry |
-
-
- Request Token URL |
- https://sentry.io |
-
-
- Access Token URL |
- https://sentry.io |
-
-
- Authorize URL |
- https://sentry.io |
-
-
- Create Incoming Link |
- No |
-
+
+
+ Application Name |
+ Sentry |
+
+
+ Application Type |
+ Generic Application |
+
+
+ Service Provider Name |
+ Sentry |
+
+
+ Consumer Key |
+ (your choice, but keep this handy for the next step) |
+
+
+ Shared Secret |
+ sentry |
+
+
+ Request Token URL |
+ https://sentry.io |
+
+
+ Access Token URL |
+ https://sentry.io |
+
+
+ Authorize URL |
+ https://sentry.io |
+
+
+ Create Incoming Link |
+ No |
+
+
1. Click "Continue". This will return you to the **Configure Application Links** page, where you'll see an application called Sentry.
@@ -95,26 +97,28 @@ openssl x509 -pubkey -noout -in jira_publickey.cer > jira_publickey.pem
1. On the lefthand side of the resulting modal, click "Incoming Authentication". Fill out the form as follows, and press **Save**:
-
- Consumer Key |
- (the consumer key from Step II.4) |
-
-
- Consumer Name |
- Sentry |
-
-
- Public Key |
- (the public key you created in Section I) |
-
-
- Consumer Callback URL |
- https://sentry.io/extensions/jira-server/setup/ |
-
-
- Allow 2-Legged OAuth |
- no |
-
+
+
+ Consumer Key |
+ (the consumer key from Step II.4) |
+
+
+ Consumer Name |
+ Sentry |
+
+
+ Public Key |
+ (the public key you created in Section I) |
+
+
+ Consumer Callback URL |
+ https://sentry.io/extensions/jira-server/setup/ |
+
+
+ Allow 2-Legged OAuth |
+ no |
+
+
#### Connect your Jira Server application with Sentry
diff --git a/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx b/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx
index 503828ad80ba7..be9aa97024bfb 100644
--- a/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx
@@ -53,42 +53,44 @@ openssl x509 -pubkey -noout -in bitbucket_publickey.cer > bitbucket_publickey.p
4. In the resulting dialog, fill out the form as follows:
-
- Application Name |
- Sentry |
-
-
- Application Type |
- Generic Application |
-
-
- Service Provider Name |
- Sentry |
-
-
- Consumer Key |
- (your choice, but keep this handy for the next step) |
-
-
- Shared Secret |
- sentry |
-
-
- Request Token URL |
- https://sentry.io |
-
-
- Access Token URL |
- https://sentry.io |
-
-
- Authorize URL |
- https://sentry.io |
-
-
- Create Incoming Link |
- No |
-
+
+
+ Application Name |
+ Sentry |
+
+
+ Application Type |
+ Generic Application |
+
+
+ Service Provider Name |
+ Sentry |
+
+
+ Consumer Key |
+ (your choice, but keep this handy for the next step) |
+
+
+ Shared Secret |
+ sentry |
+
+
+ Request Token URL |
+ https://sentry.io |
+
+
+ Access Token URL |
+ https://sentry.io |
+
+
+ Authorize URL |
+ https://sentry.io |
+
+
+ Create Incoming Link |
+ No |
+
+
5. Click "Continue". This will return you to the **Configure Application Links** page, where you'll see an application called Sentry.
@@ -96,26 +98,28 @@ openssl x509 -pubkey -noout -in bitbucket_publickey.cer > bitbucket_publickey.p
7. On the lefthand side of the resulting modal, click "Incoming Authentication". Fill out the form as follows, and click "Save":
-
- Consumer Key |
- (the consumer key from Step II.4) |
-
-
- Consumer Name |
- Sentry |
-
-
- Public Key |
- (the public key you created in Section I) |
-
-
- Consumer Callback URL |
- https://sentry.io/extensions/bitbucket_server/setup/ |
-
-
- Allow 2-Legged OAuth |
- no |
-
+
+
+ Consumer Key |
+ (the consumer key from Step II.4) |
+
+
+ Consumer Name |
+ Sentry |
+
+
+ Public Key |
+ (the public key you created in Section I) |
+
+
+ Consumer Callback URL |
+ https://sentry.io/extensions/bitbucket_server/setup/ |
+
+
+ Allow 2-Legged OAuth |
+ no |
+
+
#### Connect your Bitbucket Server application with Sentry
diff --git a/docs/organization/integrations/source-code-mgmt/github/index.mdx b/docs/organization/integrations/source-code-mgmt/github/index.mdx
index a5aa1283b902c..205959f8a2678 100644
--- a/docs/organization/integrations/source-code-mgmt/github/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/github/index.mdx
@@ -61,87 +61,91 @@ If you're using GitHub Enterprise Cloud, follow the [instructions for GitHub](/o
2. Then in GitHub, fill out the form as follows and click "Create GitHub App".
-
- GitHub App Name |
- sentry-app |
-
-
- Homepage URL |
- https://sentry.io |
-
-
- User authorization callback URL |
- https://sentry.io/extensions/github-enterprise/setup/ |
-
-
- Setup URL |
- https://sentry.io/extensions/github-enterprise/setup/ |
-
-
- Webhook URL |
- https://sentry.io/extensions/github-enterprise/webhook/ |
-
-
- Webhook secret |
- `Input your secret from the previous step` |
-
-
- Repository Administration |
- Read-only |
-
-
- Commit Statuses |
- No Access |
-
-
- Deployments |
- No Access |
-
-
- Issues |
- Read & Write |
-
-
- Pages |
- No Access |
-
-
- Pull Requests |
- Read-only |
-
-
- Repository Contents |
- Read-only |
-
-
- Single File |
- No Access |
-
-
- Repository Projects |
- No Access |
-
-
- Organization members |
- Read-only |
-
-
- Organization projects |
- No Access |
-
+
+
+ GitHub App Name |
+ sentry-app |
+
+
+ Homepage URL |
+ https://sentry.io |
+
+
+ User authorization callback URL |
+ https://sentry.io/extensions/github-enterprise/setup/ |
+
+
+ Setup URL |
+ https://sentry.io/extensions/github-enterprise/setup/ |
+
+
+ Webhook URL |
+ https://sentry.io/extensions/github-enterprise/webhook/ |
+
+
+ Webhook secret |
+ `Input your secret from the previous step` |
+
+
+ Repository Administration |
+ Read-only |
+
+
+ Commit Statuses |
+ No Access |
+
+
+ Deployments |
+ No Access |
+
+
+ Issues |
+ Read & Write |
+
+
+ Pages |
+ No Access |
+
+
+ Pull Requests |
+ Read-only |
+
+
+ Repository Contents |
+ Read-only |
+
+
+ Single File |
+ No Access |
+
+
+ Repository Projects |
+ No Access |
+
+
+ Organization members |
+ Read-only |
+
+
+ Organization projects |
+ No Access |
+
+
**Subscribe to Events**
-
- Pull Request |
- Yes |
-
-
- Push |
- Yes |
-
+
+
+ Pull Request |
+ Yes |
+
+
+ Push |
+ Yes |
+
+
#### Install your GitHub App
diff --git a/docs/product/issues/issue-details/performance-issues/index.mdx b/docs/product/issues/issue-details/performance-issues/index.mdx
index 26bc06a24c18f..452c81cfb5727 100644
--- a/docs/product/issues/issue-details/performance-issues/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/index.mdx
@@ -35,103 +35,105 @@ The "Event Grouping Information" section provides details of how Sentry fingerpr
The following is a list of available performance issues:
-
- Browser |
-
-
- |
-
-
- Server |
-
-
- |
-
-
- Mobile |
-
-
- |
-
-
- Serverless |
-
-
- |
-
+
+
+ Browser |
+
+
+ |
+
+
+ Server |
+
+
+ |
+
+
+ Mobile |
+
+
+ |
+
+
+ Serverless |
+
+
+ |
+
+
## Performance Issue Limitations
diff --git a/docs/security-legal-pii/security/ai-ml-policy.mdx b/docs/security-legal-pii/security/ai-ml-policy.mdx
index 4e0da20372b24..c395af9c05de6 100644
--- a/docs/security-legal-pii/security/ai-ml-policy.mdx
+++ b/docs/security-legal-pii/security/ai-ml-policy.mdx
@@ -43,34 +43,36 @@ To ensure our BAA customers can remain HIPAA compliant and that data stays in yo
## Data Access Summary
-
- Access Type |
- Is the underlying data identifiable? |
- Will this data (or any output) be shared with others? |
- Will this data be used for training Sentry models? |
- Will this data be used to train 3rd party models? |
-
-
- Non-identifying data |
- No |
- Other Sentry customers |
- Yes |
- No |
-
-
- Aggregated identifying data |
- Yes |
- Sentry only |
- Yes |
- No |
-
-
- Identifying data for generative AI features |
- Yes |
- Approved feature-specific subprocessors |
- No |
- No |
-
+
+
+ Access Type |
+ Is the underlying data identifiable? |
+ Will this data (or any output) be shared with others? |
+ Will this data be used for training Sentry models? |
+ Will this data be used to train 3rd party models? |
+
+
+ Non-identifying data |
+ No |
+ Other Sentry customers |
+ Yes |
+ No |
+
+
+ Aggregated identifying data |
+ Yes |
+ Sentry only |
+ Yes |
+ No |
+
+
+ Identifying data for generative AI features |
+ Yes |
+ Approved feature-specific subprocessors |
+ No |
+ No |
+
+
## Data Handling