update naming (docs files)

Author: colleenmcginnis

README.md

@@ -1,18 +1,18 @@
 [![Pull Request Validation](https://github.com/elastic/elastic-otel-dotnet/actions/workflows/ci.yml/badge.svg)](https://github.com/elastic/elastic-otel-dotnet/actions/workflows/ci.yml)
 
-# Elastic Distribution for OpenTelemetry .NET
+# Elastic Distribution of OpenTelemetry .NET
 
 > [!WARNING]
-> The Elastic Distribution for OpenTelemetry .NET is not yet recommended for production use. Functionality may be changed or removed in future releases. Alpha releases are not subject to the support SLA of official GA features.
+> The Elastic Distribution of OpenTelemetry .NET is not yet recommended for production use. Functionality may be changed or removed in future releases. Alpha releases are not subject to the support SLA of official GA features.
 >
 > We welcome your feedback! You can reach us by [opening a GitHub issue](https://github.com/elastic/elastic-otel-dotnet/issues) or starting a discussion thread on the [Elastic Discuss forum](https://discuss.elastic.co/tags/c/observability/apm/58/dotnet).
 
-The Elastic Distribution for OpenTelemetry .NET (the distro) provides a zero code change extension of the [OpenTelemetry SDK for .NET](https://opentelemetry.io/docs/languages/net). The distro makes it easier to get started using OpenTelemetry in your .NET 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.
+The Elastic Distribution of OpenTelemetry .NET (EDOT .NET) provides a zero code change extension of the [OpenTelemetry SDK for .NET](https://opentelemetry.io/docs/languages/net). EDOT .NET makes it easier to get started using OpenTelemetry in your .NET 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.
 
 > [!NOTE]
 > For more details about OpenTelemetry distributions in general, visit the [OpenTelemetry documentation](https://opentelemetry.io/docs/concepts/distributions).
 
-With the distro you have access to all the features of the OpenTelemetry SDK for .NET plus:
+With EDOT .NET you have access to all the features of the OpenTelemetry SDK for .NET plus:
 
 * Access to SDK improvements and bug fixes contributed by the Elastic team _before_ the changes are available upstream in OpenTelemetry repositories.
 * Elastic-specific processors that ensure optimal compatibility when exporting OpenTelemetry signal data to an Elastic backend like an Elastic Observability deployment.
@@ -23,7 +23,7 @@ With the distro you have access to all the features of the OpenTelemetry SDK for
 
 ## Install
 
-To get started with the Elastic Distribution for OpenTelemetry .NET, you must add the
+To get started with the Elastic Distribution of OpenTelemetry .NET, you must add the
 [`Elastic.OpenTelemetry`](https://www.nuget.org/packages/Elastic.OpenTelemetry)
 NuGet package to your project. This can be achieved by adding the package reference to your project file.
 
@@ -41,7 +41,7 @@ NuGet package to your project. This can be achieved by adding the package refere
 
 <!-- ## Getting started
 
-As the distribution is a lightweight extension of the OpenTelemetry SDK, you should be broadly
+As EDOT .NET is a lightweight extension of the OpenTelemetry SDK, you should be broadly
 familiar with the OpenTelemetry SDK concepts and instrumenting applications using the Microsoft
 diagnostic APIs. If you are not, we recommend you read the
 [OpenTelemetry SDK documentation](https://opentelemetry.io/docs/languages/net) first.
@@ -63,25 +63,25 @@ Before continuing, ensure that you have a supported
 > **_NOTE:_** Replace the `<LATEST>` placeholder with the latest available package from
 [NuGet.org](https://www.nuget.org/packages/Elastic.OpenTelemetry).
 
-After adding the package reference, you can start using the Elastic Distribution for OpenTelemetry .NET
-in your application. The distribution includes a transitive dependency on the OpenTelemetry SDK,
+After adding the package reference, you can start using the Elastic Distribution of OpenTelemetry .NET
+in your application. EDOT .NET includes a transitive dependency on the OpenTelemetry SDK,
 so you do not need to add the OpenTelemetry SDK package to your project, although doing so will
-cause no harm and may be used to opt into newer SDK versions before the Elastic Distribution for OpenTelemetry .NET
+cause no harm and may be used to opt into newer SDK versions before the Elastic Distribution of OpenTelemetry .NET
 references them.
 
-The Elastic Distribution for OpenTelemetry .NET is designed to be easy to use and integrate into your
+The Elastic Distribution of OpenTelemetry .NET is designed to be easy to use and integrate into your
 applications. This includes applications which have previously used the OpenTelemetry SDK directly.
 In situations where the OpenTelemetry SDK is already used, the only required change is
 to add the [`Elastic.OpenTelemetry`](https://www.nuget.org/packages/Elastic.OpenTelemetry) NuGet
 package to the project. Doing so will automatically switch to the opinionated configuration provided
-by the Elastic Distribution for OpenTelemetry .NET.
+by the Elastic Distribution of OpenTelemetry .NET.
 
 ### ASP.NET Core usage
 
 A common requirement is to instrument ASP.NET Core applications based on the `Microsoft.Extensions.Hosting`
 libraries which provide dependency injection via an `IServiceProvider`.
 
-The OpenTelemetry SDK and the Elastic Distribution for OpenTelemetry .NET provide extension methods to enable observability
+The OpenTelemetry SDK and the Elastic Distribution of OpenTelemetry .NET provide extension methods to enable observability
 features in your application by adding a few lines of code.
 
 In this section, we'll focus on instrumenting an ASP.NET Core minimal API application using the Elastic
@@ -101,7 +101,7 @@ NuGet package to your project:
 
 This package includes instrumentation to collect traces for requests handled by ASP.NET Core endpoints.
 
-> **_NOTE:_** The ASP.NET Core instrumentation is not included by default in the Elastic Distribution for OpenTelemetry .NET.
+> **_NOTE:_** The ASP.NET Core instrumentation is not included by default in the Elastic Distribution of OpenTelemetry .NET.
 As with all optional instrumentation libraries, you can choose to include them in your application by
 adding a suitable package reference.
 
@@ -113,7 +113,7 @@ using OpenTelemetry.Trace;
 ```
 
 The OpenTelemetry SDK provides extension methods on the `IServiceCollection` to support enabling the
-providers and configuring the SDK. The Elastic Distribution for OpenTelemetry .NET overrides the default SDK registration,
+providers and configuring the SDK. The Elastic Distribution of OpenTelemetry .NET overrides the default SDK registration,
 adding several opinionated defaults.
 
 In the minimal API template, the `WebApplicationBuilder` exposes a `Services` property that can be used
@@ -133,12 +133,12 @@ injection container. This is NOT required to enable OpenTelemetry, but the examp
 send an HTTP request.
 
 <2> The `AddOpenTelemetry` method registers the OpenTelemetry SDK with the dependency injection
-container. When available, the Elastic Distribution for OpenTelemetry .NET will override this to add opinionated defaults.
+container. When available, the Elastic Distribution of OpenTelemetry .NET will override this to add opinionated defaults.
 
 <3> Configure tracing to instrument requests handled by ASP.NET Core.
 
 With these limited changes to the `Program.cs` file, the application is now configured to use the
-OpenTelemetry SDK and the Elastic Distribution for OpenTelemetry .NET to collect traces and metrics, which are exported via
+OpenTelemetry SDK and the Elastic Distribution of OpenTelemetry .NET to collect traces and metrics, which are exported via
 OTLP.
 
 To demonstrate the tracing capabilities, add a simple endpoint to the application:
@@ -157,7 +157,7 @@ app.MapGet("/", async (IHttpClientFactory httpClientFactory) =>
 ```
 <1> Using this URL will require two redirects, allowing us to see multiple spans in the trace.
 
-The Elastic Distribution for OpenTelemetry .NET will automatically enable the exporting of signals via the OTLP exporter. This
+The Elastic Distribution of OpenTelemetry .NET will automatically enable the exporting of signals via the OTLP exporter. This
 exporter requires that endpoint(s) are configured. A common mechanism for configuring endpoints is
 via environment variables.
 

docs/configure.md

@@ -9,6 +9,8 @@ Assumptions we're comfortable making about the reader:
 
 # Configure
 
+Configure the Elastic Distribution of OpenTelemetry .NET (EDOT .NET) to send data to Elastic.
+
 <!-- ✅ How users set configuration options -->
 ## Configuration methods
 
@@ -17,7 +19,7 @@ including:
 
 * Setting [environment variables](#environment-variables)
 * Using the [`IConfiguration` integration](#iconfiguration-integration)
-* [Manually configuring](#manual-configuration) the Elastic distribution
+* [Manually configuring](#manual-configuration) EDOT .NET
 
 <!-- Order of precedence -->
 Configuration options set manually in the code take precedence over environment variables, and
@@ -26,18 +28,18 @@ environment variables take precedence over configuration options set using the `
 ### Environment variables
 
 <!-- ✅ What and why -->
-The distro can be configured using environment variables.
-This is a cross-platform way to configure the distro and is especially useful in containerized environments.
+EDOT .NET can be configured using environment variables.
+This is a cross-platform way to configure EDOT .NET and is especially useful in containerized environments.
 
 <!-- ✅ How -->
-Environment variables are read at startup and can be used to configure the Elastic distribution.
+Environment variables are read at startup and can be used to configure EDOT .NET.
 For details of the various options available and their corresponding environment variable names,
 see [Configuration options](#configuration-options)
 
 ### `IConfiguration` integration
 
 <!-- ✅ What and why -->
-In applications that use the "host" pattern, such as ASP.NET Core and worker service, the distro
+In applications that use the "host" pattern, such as ASP.NET Core and worker service, EDOT .NET
 can be configured using the `IConfiguration` integration.
 
 <!-- ✅ How -->
@@ -55,10 +57,10 @@ var currentConfig = builder.Configuration;
 
 By default, at this stage, the configuration will be populated from the default configuration sources,
 including the `appsettings.json` file(s) and command-line arguments. You may use these sources to define
-the configuration for the Elastic Distribution for OpenTelemetry .NET.
+the configuration for the Elastic Distribution of OpenTelemetry .NET.
 
 <!-- ✅ Example -->
-For example, you can define the configuration for the Elastic Distribution for OpenTelemetry .NET in the `appsettings.json` file:
+For example, you can define the configuration for the Elastic Distribution of OpenTelemetry .NET in the `appsettings.json` file:
 
 ```json
 {
@@ -74,23 +76,23 @@ For example, you can define the configuration for the Elastic Distribution for O
 > This example sets the file log directory to `C:\Logs` which enables diagnostic file logging.
 
 Configuration from the "Elastic:OpenTelemetry" section of the `IConfiguration` instance will be
-bound to the `ElasticOpenTelemetryOptions` instance used to configure the Elastic distribution.
+bound to the `ElasticOpenTelemetryOptions` instance used to configure EDOT .NET.
 
 To learn more about the Microsoft configuration system, see
 [Configuration in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration).
 
 ### Manual configuration
 
 <!-- ✅ What and why -->
-In all other scenarios, you can configure the distro manually in code.
+In all other scenarios, you can configure EDOT .NET manually in code.
 
 <!-- ✅ How -->
 Create an instance of `ElasticOpenTelemetryBuilderOptions` and pass it to the `ElasticOpenTelemetryBuilder`
 constructor or an overload of the `AddElasticOpenTelemetry` extension method on the `IServiceCollection`.
 
 <!-- ✅ Example -->
 For example, in traditional console applications, you can configure the
-Elastic Distribution for OpenTelemetry .NET like this:
+Elastic Distribution of OpenTelemetry .NET like this:
 
 ```csharp
 using Elastic.OpenTelemetry;
@@ -115,7 +117,7 @@ var builderOptions = new ElasticOpenTelemetryBuilderOptions
 };
 
 // Pass the `ElasticOpenTelemetryBuilderOptions` instance to the
-// `ElasticOpenTelemetryBuilder` constructor to configure the distro.
+// `ElasticOpenTelemetryBuilder` constructor to configure EDOT .NET.
 await using var session = new ElasticOpenTelemetryBuilder(builderOptions)
 	.WithTracing(b => b.AddSource("MySource"))
 	.Build();
@@ -124,25 +126,25 @@ await using var session = new ElasticOpenTelemetryBuilder(builderOptions)
 <!-- ✅ List all available configuration options -->
 ## Configuration options
 
-Because the Elastic Distribution for OpenTelemetry .NET ("the distro") is an extension of the [OpenTelemetry .NET agent](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation), it supports both:
+Because the Elastic Distribution of OpenTelemetry .NET (EDOT .NET) is an extension of the [OpenTelemetry .NET agent](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation), it supports both:
 
 * General OpenTelemetry SDK configuration options
-* Elastic-specific configuration options that are only available when using the distro
+* Elastic-specific configuration options that are only available when using EDOT .NET
 
 ### OpenTelemetry SDK configuration options
 
-The distro supports all configuration options listed in the [OpenTelemetry General SDK Configuration documentation](https://opentelemetry.io/docs/languages/sdk-configuration/general/).
+EDOT .NET supports all configuration options listed in the [OpenTelemetry General SDK Configuration documentation](https://opentelemetry.io/docs/languages/sdk-configuration/general/).
 
 ### Elastic-specific configuration options
 
-The distro supports the following Elastic-specific options.
+EDOT .NET supports the following Elastic-specific options.
 
 #### `FileLogDirectory`
 
 * _Type_: String
 * _Default_: `string.Empty`
 
-A string specifying the directory where the Elastic Distribution for OpenTelemetry .NET will write diagnostic log files.
+A string specifying the directory where the Elastic Distribution of OpenTelemetry .NET will write diagnostic log files.
 When not provided, no file logging will occur. Each new .NET process will create a new log file in the
 specified directory.
 
@@ -156,7 +158,7 @@ specified directory.
 * _Type_: String
 * _Default_: `Information`
 
-Sets the logging level for the distribution.
+Sets the logging level for EDOT .NET.
 
 Valid options: `Critical`, `Error`, `Warning`, `Information`, `Debug`, `Trace` and `None` (`None` disables the logging).
 
@@ -170,7 +172,7 @@ Valid options: `Critical`, `Error`, `Warning`, `Information`, `Debug`, `Trace` a
 * _Type_: Bool
 * _Default_: `false`
 
-Allows the distribution to used with its defaults, but without enabling the export of telemetry data to
+Allows EDOT .NET to used with its defaults, but without enabling the export of telemetry data to
 an OTLP endpoint. This can be useful when you want to test applications without sending telemetry data.
 
 | Configuration method | Key |
@@ -184,21 +186,21 @@ an OTLP endpoint. This can be useful when you want to test applications without
 * _Default_: `string.Empty`
 
 A comma-separated list of Elastic defaults to enable. This can be useful when you want to enable
-only some of the Elastic Distribution for OpenTelemetry .NET opinionated defaults.
+only some of the Elastic Distribution of OpenTelemetry .NET opinionated defaults.
 
 Valid options: `None`, `Traces`, `Metrics`, `Logs`, `All`.
 
 Except for the `None` option, all other options can be combined.
 
-When this setting is not configured or the value is `string.Empty`, all Elastic Distribution for OpenTelemetry .NET defaults will be enabled.
+When this setting is not configured or the value is `string.Empty`, all Elastic Distribution of OpenTelemetry .NET defaults will be enabled.
 
-When `None` is specified, no Elastic Distribution for OpenTelemetry .NET defaults will be enabled, and you will need to manually
-configure the OpenTelemetry SDK to enable collection of telemetry signals. In this mode, the Elastic distribution
+When `None` is specified, no Elastic Distribution of OpenTelemetry .NET defaults will be enabled, and you will need to manually
+configure the OpenTelemetry SDK to enable collection of telemetry signals. In this mode, EDOT .NET
 does not provide any opinionated defaults, nor register any processors, allowing you to start with the "vanilla"
 OpenTelemetry SDK configuration. You may then choose to configure the various providers and register processors
 as required.
 
-In all other cases, the Elastic Distribution for OpenTelemetry .NET will enable the specified defaults. For example, to enable only
+In all other cases, the Elastic Distribution of OpenTelemetry .NET will enable the specified defaults. For example, to enable only
 Elastic defaults only for tracing and metrics, set this value to `Traces,Metrics`.
 
 | Configuration method | Key |
@@ -238,7 +240,7 @@ export OTEL_EXPORTER_OTLP_HEADERS="Authorization=ApiKey TkpXUkx...dVZGQQ=="
 
 <!-- ✅ What is this -->
 <!-- ✅ Why use this -->
-[Secret tokens](https://www.elastic.co/guide/en/observability/current/apm-secret-token.html) are used to authorize requests to the APM Server. Both the distro and APM Server must be configured with the same secret token for the request to be accepted.
+[Secret tokens](https://www.elastic.co/guide/en/observability/current/apm-secret-token.html) are used to authorize requests to the APM Server. Both EDOT .NET and APM Server must be configured with the same secret token for the request to be accepted.
 
 <!-- ✅ How do you authenticate using this method? -->
 You can find the values of these variables in Kibana's APM tutorial.