Removing third party hyperlinks from our docs

site/docs/concepts/captures.md

@@ -32,7 +32,7 @@ See the [source connector reference documentation](../reference/Connectors/captu
 
 ### Batch sources
 
-Flow supports running both first and third party connectors to batch sources including Singer, Meltano and Airbyte as well as natively-written Estuary connectors.  
+Flow supports running both first and third party connectors to batch sources as well as natively-written Estuary connectors.
 These connectors tend to focus on SaaS APIs, and do not offer real-time streaming integrations.
 Flow runs the connector at regular intervals to capture updated documents.
 

site/docs/reference/Connectors/capture-connectors/README.md

@@ -104,9 +104,6 @@ within the limitations set by the connector itself.
 
 Typically, we enable SaaS connectors from third parties to allow more diverse data flows.
 
-All the third-party connectors available currently were created by [Airbyte](https://airbyte.com/connectors).
-The versions made available in Flow have been adapted for compatibility.
-
 - Airtable
   - [Configuration](./airtable.md)
   - Package - ghrc.io/estuary/source-airtable.dev

site/docs/reference/Connectors/capture-connectors/Salesforce/salesforce-historical-data.md

@@ -10,8 +10,6 @@ This connector is available for use in the Flow web application.
 For local development or open-source workflows, [`ghcr.io/estuary/source-salesforce:dev`](https://ghcr.io/estuary/source-salesforce:dev) provides the latest connector image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/salesforce/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/airtable.md

@@ -6,8 +6,6 @@ This connector captures data from Airtable into Flow collections.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-airtable:dev`](https://ghcr.io/estuary/source-airtable:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/airtable/),
-but keep in mind that the two versions may be significantly different.
 
 ## Prerequisites
 

site/docs/reference/Connectors/capture-connectors/amazon-ads.md

@@ -6,8 +6,7 @@ This connector captures data from Amazon Ads into Flow collections via the [Amaz
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-amazon-ads:dev`](https://ghcr.io/estuary/source-amazon-ads:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/amazon-ads/),
-but keep in mind that the two versions may be significantly different.
+
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/amplitude.md

@@ -6,8 +6,6 @@ This connector captures data from Amplitude into Flow collections.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-amplitude:dev`](https://ghcr.io/estuary/source-amplitude:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/amplitude/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/bing-ads.md

@@ -6,8 +6,6 @@ This connector captures data from Bing Ads into Flow collections via the [Bing A
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-bing-ads:dev`](https://ghcr.io/estuary/source-bing-ads:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/bing-ads/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/braintree.md

@@ -6,8 +6,6 @@ This connector captures data from Braintree into Flow collections.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-braintree:dev`](https://ghcr.io/estuary/source-braintree:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/braintree/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/braze.md

@@ -6,8 +6,6 @@ This connector captures data from Braze into Flow collections.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-braze:dev`](https://ghcr.io/estuary/source-braze:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/braze/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/chargebee.md

@@ -6,8 +6,6 @@ This connector captures data from Chargebee into Flow collections.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-chargebee:dev`](https://ghcr.io/estuary/source-chargebee:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/chargebee/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/confluence.md

@@ -6,8 +6,6 @@ This connector captures data from Confluence into Flow collections via the Confl
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-confluence:dev`](https://ghcr.io/estuary/source-confluence:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/confluence/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 
@@ -17,11 +15,11 @@ From your selection, the following data resources are captured:
 
 ### resources
 
- - [Audit](https://developer.atlassian.com/cloud/confluence/rest/api-group-audit/#api-wiki-rest-api-audit-get) 
- - [Blog Posts](https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-wiki-rest-api-content-get) 
- - [Group](https://developer.atlassian.com/cloud/confluence/rest/api-group-group/#api-wiki-rest-api-group-get) 
- - [Pages](https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-wiki-rest-api-content-get) 
- - [Space](https://developer.atlassian.com/cloud/confluence/rest/api-group-space/#api-wiki-rest-api-space-get) 
+ - [Audit](https://developer.atlassian.com/cloud/confluence/rest/api-group-audit/#api-wiki-rest-api-audit-get)
+ - [Blog Posts](https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-wiki-rest-api-content-get)
+ - [Group](https://developer.atlassian.com/cloud/confluence/rest/api-group-group/#api-wiki-rest-api-group-get)
+ - [Pages](https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-wiki-rest-api-content-get)
+ - [Space](https://developer.atlassian.com/cloud/confluence/rest/api-group-space/#api-wiki-rest-api-space-get)
 
 Each resource is mapped to a Flow collection through a separate binding.
 
@@ -36,7 +34,7 @@ Each resource is mapped to a Flow collection through a separate binding.
 You configure connectors either in the Flow web app, or by directly editing the catalog specification file.
 See [connectors](../../../concepts/connectors.md#using-connectors) to learn more about using connectors. The values and specification sample below provide configuration details specific to the GitHub source connector.
 
-1. Create an API Token 
+1. Create an API Token
  - For detailed instructions on creating an Atlassian API Token, please refer to the [official documentation](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
 2. Set up the Confluence connector in Estuary Flow
  - Log into Estuary Flow and click "Captures".

site/docs/reference/Connectors/capture-connectors/exchange-rates.md

@@ -8,8 +8,6 @@ This simple connector is useful for educational and demonstration purposes.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-exchange-rates:dev`](https://ghcr.io/estuary/source-exchange-rates:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/exchangeratesapi),
-but keep in mind that the two versions differ.
 
 ## Prerequisites
 

site/docs/reference/Connectors/capture-connectors/facebook-marketing.md

@@ -7,8 +7,6 @@ It is available for use in the Flow web application. For local development or op
 
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/facebook-marketing/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/freshdesk.md

@@ -6,8 +6,6 @@ This connector captures Freshdesk data into Flow collections via the [Freshdesk
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-freshdesk:dev`](https://ghcr.io/estuary/source-freshdesk:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/freshdesk/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/github.md

@@ -6,8 +6,6 @@ This connector captures data from GitHub repositories and organizations into Flo
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-github:dev`](https://ghcr.io/estuary/source-github:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/github/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/gitlab.md

@@ -6,8 +6,6 @@ This connector captures data from GitLab repositories and organizations into Flo
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-gitlab:dev`](https://ghcr.io/estuary/source-gitlab:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/gitlab/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/google-ads.md

@@ -6,8 +6,6 @@ This connector captures data from [resources](https://developers.google.com/goog
 [`ghcr.io/estuary/source-google-ads:dev`](https://ghcr.io/estuary/source-google-ads:dev) provides the latest connector image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/google-ads/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/google-analytics-4.md

@@ -13,8 +13,6 @@ Universal Analytics is supported by a [separate connector](./google-analytics.md
 It’s available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-google-analytics-data-api:dev`](https://ghcr.io/estuary/source-google-analytics-data-api:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/google-analytics-v4/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/google-analytics.md

@@ -12,8 +12,6 @@ Google Analytics 4 is supported by a [separate connector](./google-analytics-4.m
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-google-analytics-ua:dev`](https://ghcr.io/estuary/source-google-analytics-ua:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/google-analytics-universal-analytics),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/google-search-console.md

@@ -6,8 +6,6 @@ This connector captures data from Google Search Console into Flow collections vi
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-google-search-console:dev`](https://ghcr.io/estuary/source-google-search-console:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/google-search-console/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/google-sheets.md

@@ -6,8 +6,6 @@ This connector captures data from a Google Sheets spreadsheet.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-google-sheets:dev`](https://ghcr.io/estuary/source-google-sheets:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/google-sheets),
-but keep in mind that the two versions may be significantly different.
 
 ## Prerequisites
 

site/docs/reference/Connectors/capture-connectors/greenhouse.md

@@ -7,8 +7,6 @@ It is available for use in the Flow web application. For local development or op
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
 
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/greenhouse/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/harvest.md

@@ -6,8 +6,6 @@ This connector captures data from Harvest into Flow collections.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-harvest:dev`](https://ghcr.io/estuary/source-harvest:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/harvest/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/hubspot.md

@@ -8,8 +8,6 @@ Estuary offers a in-house real time version of this connector. For more informat
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-hubspot:dev`](https://ghcr.io/estuary/source-hubspot:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/hubspot),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources
 

site/docs/reference/Connectors/capture-connectors/instagram.md

@@ -9,9 +9,6 @@ It is available for use in the Flow web application. For local development or op
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
 
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/instagram/),
-but keep in mind that the two versions may be significantly different.
-
 ## Supported data resources
 
 The following data resources are supported through the Instagram APIs:

site/docs/reference/Connectors/capture-connectors/intercom.md

@@ -6,8 +6,6 @@ This connector captures data from Intercom into Flow collections.
 It is available for use in the Flow web application. For local development or open-source workflows, [`ghcr.io/estuary/source-intercom:dev`](https://ghcr.io/estuary/source-intercom:dev) provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.
 
 This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system.
-You can find their documentation [here](https://docs.airbyte.com/integrations/sources/intercom/),
-but keep in mind that the two versions may be significantly different.
 
 ## Supported data resources