Update OpenTelemetry documentation for clarity

Clarified the relationship between Microsoft.ApplicationInsights.WorkerService and Azure Monitor Exporter, emphasizing the use of the former for Application Insights configuration.

Author: ggailey777

articles/azure-functions/opentelemetry-howto.md

@@ -103,7 +103,7 @@ Examples in this article assume your app uses `IHostApplicationBuilder`, which i
     ### [Application Insights](#tab/app-insights)
 
     > [!NOTE]
-    > `Microsoft.ApplicationInsights.WorkerService (v3.0 or later)` package is essentially a shim on top of Azure Monitor Exporter. It provides an Application Insights–style configuration experience but internally uses the same Azure Monitor pipeline. You can choose `Microsoft.ApplicationInsights.WorkerService (v3.0 or later)` instead of `Azure.Monitor.OpenTelemetry.Exporter`.
+    > Starting with version 3.0, the `Microsoft.ApplicationInsights.WorkerService` package leverages Azure Monitor Exporter. You can use this package to maintain the existing Application Insights configuration behaviors while internally using the Azure Monitor pipeline, including the OpenTelemetry exporter. You can use the `Microsoft.ApplicationInsights.WorkerService` package (v3.0 or later) instead of the `Azure.Monitor.OpenTelemetry.Exporter` package, which is shown in the following example.
 
     ```cmd
     dotnet add package Microsoft.Azure.Functions.Worker.OpenTelemetry