Update uninstallation, add to index page

Author: ceorourke

src/_assets/img/vercel/vercel_delete.png

@@ -1108,7 +1108,7 @@ Vercel is an all-in-one platform with Global CDN supporting static and JAMstack
 
     [{% asset vercel/vercel_link_project.png alt="Sentry modal showing linking Sentry project to Vercel project." %}]({% asset vercel/vercel_link_project.png @path %})
 
-  * This step will generate environment variables in the selected Vercel project. Having these set means you can skip the [CLI Configuration step](https://github.com/getsentry/sentry-webpack-plugin#cli-configuration) in the Sentry Webpack Plugin setup. You can see these in Vercel in **Project Settings** > **General** > **Environment Variables**.
+    * This step will generate environment variables in the selected Vercel project. Having these set means you can skip the [CLI Configuration step](https://github.com/getsentry/sentry-webpack-plugin#cli-configuration) in the Sentry Webpack Plugin setup. You can see these in Vercel in **Project Settings** > **General** > **Environment Variables**.
 
 
     [{% asset vercel/vercel_env_vars.png alt="Sentry modal showing linking Sentry project to Vercel project." %}]({% asset vercel/vercel_env_vars.png @path %})
@@ -1119,20 +1119,25 @@ Vercel is an all-in-one platform with Global CDN supporting static and JAMstack
     * `NEXT_PUBLIC_SENTRY_DSN` - the linked Sentry project's DSN
     * `VERCEL_GITHUB_COMMIT_SHA`, `VERCEL_GITLAB_COMMIT_SHA`, or `VERCEL_BITBUCKET_COMMIT_SHA` - your source code provider's commit SHA, used for creating releases and associating commits
 
+  2. Redeploy your Vercel project in order to trigger a release.
+
 **Usage**
 
 * If you have not already done so, [instrument your code with Sentry]({%- link _documentation/error-reporting/quickstart.md -%}).
 * Ensure you have [installed a repository integration]({%- link _documentation/workflow/releases/index.md -%}#install-repo-integration) and added the relevant repository.
 * Add the [Sentry Webpack Plugin](https://github.com/getsentry/sentry-webpack-plugin) to your configuration. For NextJS, use `next.config.js`.
 
+* If you already have a Vercel project integrated with Sentry, ensure the Sentry project you link is the one you're already using to report errors.
+
 **Uninstallation**
 
-1. From the Vercel integration configuration page (**Organization Settings** > **Integrations** > **Vercel**) you can uninstall the integration. 
+1. The integration must be uninstalled from Vercel. Visit the Vercel integration configuration page (**Organization Settings** > **Integrations** > **Vercel** > **Configurations**) and click "Uninstall" then "Visit Vercel" in the modal that pops up. 
 
-    [{% asset vercel/vercel_delete.png alt="Sentry modal showing uninstalling Vercel integration." %}]({% asset vercel/vercel_delete.png @path %})
+    [{% asset vercel/vercel_uninstall.png alt="Sentry modal showing uninstalling Vercel integration." %}]({% asset vercel/vercel_uninstall.png @path %})
 
+2. Click "Remove Configuration"
 
-2. Delete the internal integration that was created by navigating to **Organization Settings** > **Developer Settings** and clicking the trash can icon next to **Vercel Internal Integration**. You will be prompted to confirm the deletion by entering a string provided in the modal. Enter the string and click "Confirm" to finalize the deletion.
+3. Delete the internal integration that was created by navigating to **Organization Settings** > **Developer Settings** and clicking the trash can icon next to **Vercel Internal Integration**. You will be prompted to confirm the deletion by entering a string provided in the modal. Enter the string and click "Confirm" to finalize the deletion.
 
     [{% asset vercel/vercel_delete_internal_integration.png alt="Sentry modal showing uninstalling Vercel integration." %}]({% asset vercel/vercel_delete_internal_integration.png @path %})
 

src/_assets/img/vercel/vercel_uninstall.png

@@ -3,3 +3,67 @@ title: Integrations
 sidebar_order: 6
 gatsby: true
 ---
+<<<<<<< HEAD
+=======
+
+Sentry integrates seamlessly with your favorite apps and services.
+
+### Global Integrations
+
+These integrations are set up once per organization, and are then usable in all projects.
+
+-   [_Azure DevOps_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#azure-devops)
+-   [_Bitbucket_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#bitbucket)
+-   [_Bitbucket Server_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#bitbucket-server)
+-   [_GitHub_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#github)
+-   [_GitHub Enterprise_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#github-enterprise)
+-   [_GitLab_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#gitlab)
+-   [_JIRA_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#jira)
+-   [_JIRA Server_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#jira-server)
+-   [_PagerDuty_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#pagerduty)
+-   [_Slack_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#slack)
+-   [_Vercel_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#vercel)
+
+These integrations are maintained and supported by the companies that created them. See [integration platform]({%- link _documentation/workflow/integrations/integration-platform/index.md -%}).
+
+-   [_Amixr_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#amixr)
+-   [_ClickUp_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#clickup)
+-   [_Clubhouse_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#clubhouse)
+-   [_Rookout_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#rookout)
+-   [_Split_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#split)
+
+### Per-Project Integrations
+
+These integrations are set up once per project, and are only usable in projects in which they've been set up. 
+
+{% include components/alert.html
+  title="* Community Integrations"
+  content="These integrations are [maintained and supported](https://forum.sentry.io) by the Sentry community."
+  level="info"
+%}
+
+-   [_Amazon SQS_]({%- link _documentation/data-management/data-forwarding.md -%})
+-   [_Asana_]({%- link _documentation/workflow/integrations/legacy-integrations.md -%}#asana)
+-   Campfire*
+-   Flowdock
+-   [_GitLab_]({%- link _documentation/workflow/integrations/global-integrations.md -%}#gitlab)
+-   [_Heroku_]({%- link _documentation/workflow/integrations/legacy-integrations.md -%}#heroku)
+-   [_HipChat_]({%- link _documentation/workflow/integrations/legacy-integrations.md -%}#hipchat)
+-   Lighthouse*
+-   OpsGenie
+-   PagerDuty
+-   Phabricator
+-   Pivotal Tracker
+-   Pushover
+-   Redmine
+-   [_Splunk_]({%- link _documentation/workflow/integrations/legacy-integrations.md -%}#splunk)
+-   Taiga
+-   Teamwork
+-   Trello*
+-   Twilio
+
+
+### Integration Platform
+
+Sentry’s [Integration Platform]({%- link _documentation/workflow/integrations/integration-platform/index.md -%}) provides a way for external services to interact with the Sentry SaaS service using the REST API and webhooks. Integrations utilizing this platform are first-class actors within Sentry, and you can build them for [public]({%- link _documentation/workflow/integrations/integration-platform/index.md -%}#public-integrations) as well as [internal]({%- link _documentation/workflow/integrations/integration-platform/index.md -%}#internal-integrations) use cases.
+>>>>>>> Update uninstallation, add to index page