Apply suggestions from code review

Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>

Author: xrmx

docs/_edot-sdks/python/index.md

@@ -7,7 +7,7 @@ nav_order: 6
 ## EDOT Python
 
 The [Elastic Distribution of OpenTelemetry Python (EDOT Python)](https://github.com/elastic/elastic-otel-python) is a customized version of [OpenTelemetry Python](https://opentelemetry.io/docs/languages/python).
-EDOT Python makes it easier to get started using OpenTelemetry in your Python applications through strictly OpenTelemetry native means, while also providing a smooth and rich out of the box experience with [Elastic Observability](https://www.elastic.co/observability). It's an explicit goal of this distribution to introduce **no new concepts** in addition to those defined by the wider OpenTelemetry community.
+EDOT Python makes it easier to get started using OpenTelemetry in your Python applications through strictly OpenTelemetry native means, while also providing a smooth and rich out of the box experience with [Elastic Observability](https://www.elastic.co/observability). It's an explicit goal of this distribution **to avoid introducing proprietary concepts** in addition to those defined by the wider OpenTelemetry community. For any additional features introduced we aim for contributing them back to the upstream OpenTelemetry Python project.
 
 With EDOT Python you have access to all the features of the OpenTelemetry Python agent plus:
 

docs/_edot-sdks/python/migration.md

@@ -14,7 +14,7 @@ For step-by-step instructions on setting up EDOT Python refer to the [Setup](./s
 
 As a distribution of OpenTelemetry, EDOT Python follows certain standards, but there is still some space for innovation.
 
-## Bold on autoinstrumentation
+## Bold on auto-instrumentation
 
 We have chosen to make autoinstrumentation as simple as possible so you can just focus on your code; we favored an experience that requires minimal changes to your application code. The upstream OpenTelemetry configuration has more options than the distribution requires. Our default configuration is listed [here](https://github.com/elastic/elastic-otel-python?tab=readme-ov-file#configuration).
 
@@ -25,10 +25,10 @@ We provide a tool to discover available instrumentations automatically that can
 
 ## Performance comparison
 
-Any instrumentation agent will incur in a performance penalty for your application because more work will be done. How much really depends
+Every instrumentation agent comes with a (small) performance overhead for your application. How much really depends
 on your application and on the instrumentations used.
 
-While we can't provide generically applicable, accurate numbers about the performance penalty, here you can find some measurement taken
+While we can't provide generically applicable, accurate numbers about the performance overhead, here you can find some measurement taken
 from a sample web application which allows to provide a comparison between agents and an order of magnitude of the effective overhead.
 
 Those numbers are only provided as indicators, and you should not attempt to extrapolate them. You should however use

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

@@ -42,7 +42,7 @@ After installing EDOT Python, configure and initialize it to start sending data
 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:
 
-* `OTEL_RESOURCE_ATTRIBUTES`: Use this to add a service name that will make it easier to recognize your application when reviewing data sent to Elastic.
+* `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.
@@ -93,9 +93,9 @@ opentelemetry-instrument gunicorn main:app
 
 To confirm that EDOT Python has successfully connected to Elastic:
 
-1. Go to **APM** → **Traces**.
+1. Go to **APM** → **Services**
 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.
 
 > [!NOTE]
-> There may be no trace data to visualize unless you have _used_ your application since initializing EDOT Python.
+> There may be no trace data to visualize unless you have _invoked_ your application since initializing EDOT Python.