Update articles/azure-functions/dotnet-aspire-integration.md

Author: JillGrant615

articles/azure-functions/dotnet-aspire-integration.md

@@ -176,7 +176,7 @@ Consider the following points when evaluating Azure Functions with .NET Aspire:
 
 - Your `Program.cs` should use the `IHostApplicationBuilder` version of [host instance startup](./dotnet-isolated-process-guide.md#start-up-and-configuration). The `IHostApplicationBuilder` allows you to call `builder.AddServiceDefaults()` to add [.NET Aspire service defaults](/dotnet/aspire/fundamentals/service-defaults) to your Functions project.
 
-- Aspire uses OpenTelemetry for monitoring. You can configure Aspire to export telemetry to Azure Monitor through the service defaults project. In many other Azure Functions contexts, you might include direct integration with Application Insights by registering the telemetry worker service. Doing so is not recommended in Aspire. It can also lead to runtime errors with version 2.22.0 of `Microsoft.ApplicationInsights.WorkerService`, though this is addresssed in version 2.23.0. You should remove any direct Application Insights integrations from your Functions project when using Aspire.
+- Aspire uses OpenTelemetry for monitoring. You can configure Aspire to export telemetry to Azure Monitor through the service defaults project. In many other Azure Functions contexts, you might include direct integration with Application Insights by registering the telemetry worker service. Doing so is not recommended in Aspire. It can also lead to runtime errors with version 2.22.0 of `Microsoft.ApplicationInsights.WorkerService`, though this is addressed in version 2.23.0. You should remove any direct Application Insights integrations from your Functions project when using Aspire.
 
 - For Functions projects enlisted into an Aspire orchestration, most of the application configuration should come from the Aspire app host project. You should typically avoid setting things in `local.settings.json`, other than the `FUNCTIONS_WORKER_RUNTIME` setting. If you set the same environment variable in `local.settings.json` and Aspire, the system uses the Aspire version.