Clean up connectors

Author: leemthompo

docs/reference/ingestion-tools/search-connectors/index.md

@@ -7,18 +7,18 @@ mapped_pages:
 
 # Search connectors
 
-% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
-
 $$$es-connectors-native$$$
 
 
-:::{tip}
-This page is about Search connectors that synchronize third-party data into Elasticsearch. If you’re looking for Kibana connectors to integrate with services like generative AI model providers, refer to [Kibana Connectors](docs-content://deploy-manage/manage-connectors.md).
+:::{note}
+This page is about Search connectors that synchronize third-party data into {{es}}. If you’re looking for Kibana connectors to integrate with services like generative AI model providers, refer to [Kibana Connectors](docs-content://deploy-manage/manage-connectors.md).
 :::
 
-A _connector_ is a type of [Elastic integration](https://www.elastic.co/integrations/data-integrations) that syncs data from an original data source to Elasticsearch. Each connector extracts the original files, records, or objects; and transforms them into documents within Elasticsearch.
+A _connector_ is an Elastic integration that syncs data from an original data source to {{es}}. Use connectors to create searchable, read-only replicas of your data in {{es}}.
+
+Each connector extracts the original files, records, or objects; and transforms them into documents within {{es}}.
 
-_Connector clients_ are **self-managed** connectors that you run on your own infrastructure. These connectors are written in Python and the source code is available in the [`elastic/connectors`](https://github.com/elastic/connectors/tree/main/connectors/sources) repo.
+These connectors are written in Python and the source code is available in the [`elastic/connectors`](https://github.com/elastic/connectors/tree/main/connectors/sources) repo.
 
 ## Available connectors
 
@@ -28,9 +28,7 @@ As of Elastic 9.0, managed connectors on Elastic Cloud Hosted are no longer avai
 ::::
 
 
-Connector clients are available for the following third-party data sources:
-
-The following connectors are available as self-managed connectors:
+Connectors are available for the following third-party data sources:
 
 - [Azure Blob Storage](/reference/ingestion-tools/search-connectors/es-connectors-azure-blob.md)
 - [Box](/reference/ingestion-tools/search-connectors/es-connectors-box.md)
@@ -86,7 +84,6 @@ In order to set up, configure, and run a connector you’ll be moving between yo
 
 ### Data source prerequisites
 
-
-The first decision you need to make before deploying a connector is which third party service (data source) you want to sync to Elasticsearch. See the list of [available connectors](#available-connectors).
+The first decision you need to make before deploying a connector is which third party service (data source) you want to sync to {{es}}. See the list of [available connectors](#available-connectors).
 
 Note that each data source will have specific prerequisites you’ll need to meet to authorize the connector to access its data. For example, certain data sources may require you to create an OAuth application, or create a service account. You’ll need to check the [individual connector documentation](connector-reference.md) for these details.

docs/reference/ingestion-tools/search-connectors/self-managed-connectors.md

@@ -10,22 +10,15 @@ Self-managed connectors were initially known as "connector clients". You might f
 
 ::::
 
-
 Self-managed [Elastic connectors](/reference/ingestion-tools/search-connectors/index.md) are run on your own infrastructure. This means they run outside of your Elastic deployment.
 
-You can run the [connectors service](#es-connectors-deploy-connector-service) from source or from a Docker container.
-
-We also have a quickstart option using **Docker Compose**, to spin up all the required services at once: Elasticsearch, Kibana, and the connectors service. Refer to [Docker Compose quickstart](/reference/ingestion-tools/search-connectors/es-connectors-docker-compose-quickstart.md) for more information.
-
-
 ## Availability and Elastic prerequisites [es-build-connector-prerequisites]
 
 ::::{note}
 Self-managed connectors currently don’t support Windows. Use this [compatibility matrix](https://www.elastic.co/support/matrix#matrix_os) to check which operating systems are supported by self-managed connectors. Find this information under **self-managed connectors** on that page.
 
 ::::
 
-
 :::::{dropdown} Expand for Elastic prerequisites information
 Your Elastic deployment must include the following Elastic services:
 
@@ -63,17 +56,16 @@ Note the following information regarding support for self-managed connectors:
 
 :::::
 
+## Workflow
 
-::::{admonition} Data source prerequisites
-:name: es-build-connector-data-source-prerequisites
-
-The first decision you need to make before deploying a connector is which third party service (data source) you want to sync to Elasticsearch. Note that each data source will have specific prerequisites you’ll need to meet to authorize the connector to access its data. For example, certain data sources may require you to create an OAuth application, or create a service account.
-
-You’ll need to check the individual connector documentation for these details.
-
-::::
-
+In order to set up, configure, and run a connector you’ll be moving between your third-party service, the Elastic UI, and your terminal. At a high-level, the workflow looks like this:
 
+1. Satisfy any data source prerequisites (e.g., create an OAuth application).
+2. Create a connector in the UI (or via the API).
+3. Deploy the connector service:
+    - [Option 1: Run with Docker](es-connectors-run-from-docker.md) (recommended)
+    - [Option 2: Run from source](es-connectors-run-from-source.md)
+4. Enter data source configuration details in the UI.
 
 ## Deploy the connector service [es-connectors-deploy-connector-service]
 
@@ -87,16 +79,14 @@ You can run the connector service from source or use Docker:
     * Refer to our [Docker Compose quickstart](/reference/ingestion-tools/search-connectors/es-connectors-docker-compose-quickstart.md) for a quick way to spin up all the required services at once.
 
 
-
 ## Tutorials [es-build-connector-example]
 
 * Follow our [UI-based tutorial](/reference/ingestion-tools/search-connectors/es-postgresql-connector-client-tutorial.md) to learn how run the self-managed connector service and a set up a self-managed connector, **using the UI**.
 * Follow our [API-based tutorial](/reference/ingestion-tools/search-connectors/api-tutorial.md) to learn how to set up a self-managed connector **using the** [**connector APIs**](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-connector).
 
 These examples use the PostgreSQL connector but the basic process is the same for all self-managed connectors.
 
-
-## Connector testing [es-build-connector-testing]
+## E2E testing [es-build-connector-testing]
 
 The connector framework enables you to run end-to-end (E2E) tests on your self-managed connectors, against a real data source.
 
@@ -105,7 +95,7 @@ To avoid tampering with a real Elasticsearch instance, E2E tests run an isolated
 E2E tests use **default** configuration values for the connector. Find instructions about testing in each connector’s documentation.
 
 
-## Connector framework [es-build-connector-framework]
+## Build or customize connectors [es-build-connector-framework]
 
 The Elastic connector framework enables you to: