Simpligy setup instructions and refer to general onboarding page

Author: xrmx

docs/_edot-sdks/python/setup/index.md

@@ -39,40 +39,17 @@ After installing EDOT Python, configure and initialize it to start sending data
 <!-- ✅ Provide _minimal_ configuration/setup -->
 ### Configure EDOT Python
 
-To configure EDOT Python, at a minimum you'll need your Elastic Observability cloud OTLP endpoint and
-authorization data to set a few `OTLP_*` environment variables that will be available when running EDOT Python:
+Refer to [Observability quickstart](https://elastic.github.io/opentelemetry/quickstart/) documentation on how to setup your environment.
 
-* `OTEL_RESOURCE_ATTRIBUTES`: Use this to add a `service.name` and `deployment.environment` that will make it easier to recognize your application when reviewing data sent to Elastic.
-* `OTEL_EXPORTER_OTLP_ENDPOINT`: The full URL of the endpoint where data will be sent.
-* `OTEL_EXPORTER_OTLP_HEADERS`: A comma-separated list of `key=value` pairs that will
-be added to the headers of every request. This is typically used for authentication information.
-
-You can find the values of the endpoint and header variables in Kibana's APM tutorial. In Kibana:
-
-1. Go to **Setup guides**.
-1. Select **Observability**.
-1. Select **Monitor my application performance**.
-1. Scroll down and select the **OpenTelemetry** option.
-1. The appropriate values for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` are shown there.
-
-Here's an example for sending data to an Elastic Cloud deployment:
+To configure EDOT Python you need to set a few `OTLP_*` environment variables that will be available when running EDOT Python:
 
-```sh
-export OTEL_RESOURCE_ATTRIBUTES=service.name=<app-name>,service.version=<app-version>,deployment.environment=production
-export OTEL_EXPORTER_OTLP_ENDPOINT=https://my-deployment.apm.us-west1.gcp.cloud.es.io
-export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer P....l"
-```
+* `OTEL_RESOURCE_ATTRIBUTES`: Use this to add a `service.name` and `deployment.environment` that will make it easier to recognize your application when reviewing data sent to Elastic.
 
-And here's an example for sending data to an Elastic Cloud serverless project:
+The following environment variables are not required if you are sending data through a local EDOT Collector but will be provided in the Elastic Observability platform onboarding:
 
-```sh
-export OTEL_RESOURCE_ATTRIBUTES=service.name=<app-name>,service.version=<app-version>,deployment.environment=production
-export OTEL_EXPORTER_OTLP_ENDPOINT=https://my-deployment.apm.us-west1.gcp.cloud.es.io
-export OTEL_EXPORTER_OTLP_HEADERS="Authorization=ApiKey B....="
-```
+* `OTEL_EXPORTER_OTLP_ENDPOINT`: The full URL of the endpoint where data will be sent.
+* `OTEL_EXPORTER_OTLP_HEADERS`: A comma-separated list of `key=value` pairs that will be added to the headers of every request. This is typically used for authentication information.
 
-> [!NOTE]
-> You'll be prompted to create an API key during the Elastic Cloud serverless project onboarding. Refer to the [Api keys documentation](https://www.elastic.co/guide/en/serverless/current/api-keys.html) on how to manage them.
 
 ### Run EDOT Python
 
@@ -93,7 +70,7 @@ opentelemetry-instrument gunicorn main:app
 
 To confirm that EDOT Python has successfully connected to Elastic:
 
-1. Go to **APM** → **Services**
+1. Go to **Observability** → **Applications** → **Service Inventory**
 1. You should see the name of the service to which you just added EDOT Python. It can take several minutes after initializing EDOT Python for the service to show up in this list.
 1. Click on the name in the list to see trace data.
 

docs/_edot-sdks/python/setup/manual-instrumentation.md

@@ -17,16 +17,7 @@ This guide requires to have already added auto-instrumentation with OpenTelemetr
 <!-- ✅ Provide _minimal_ configuration/setup -->
 ### Configure EDOT Python
 
-To configure EDOT Python, at a minimum you'll need your Elastic Observability cloud deployment's OTLP endpoint and
-authorization data to set a few `OTLP_*` environment variables that will be available when running EDOT Python:
-
-```sh
-export OTEL_RESOURCE_ATTRIBUTES=service.name=<app-name>
-export OTEL_EXPORTER_OTLP_ENDPOINT=https://my-deployment.apm.us-west1.gcp.cloud.es.io
-export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer P....l"
-```
-
-Refer to our [Setup](./index) page for more details.
+Refer to our [Setup](./index#configure-EDOT-Python) page for more details.
 
 <!-- ✅ Manually instrument the application and start sending data to Elastic -->
 ### Manually instrument your auto instrumented Python application
@@ -107,7 +98,7 @@ def hello():
 
 To confirm that EDOT Python has successfully connected to Elastic:
 
-1. Go to **APM** → **Traces**.
+1. Go to **Observability** → **Applications** → **Service Inventory**
 1. You should see the name of the service to which you just added EDOT Python. It can take several minutes after initializing EDOT Python for the service to show up in this list.
 1. Click on the name in the list to see trace data.