fixing comments

Author: mariamgerges

docs/core/enrichment/application-log-enricher.md

@@ -165,7 +165,7 @@ Here's a complete example showing how to set up the service log enricher:
 
 **Program.cs:**
 
-### [.NET 10+](#tab/net10-plus-config)
+### [.NET 10+](#tab/net10-plus-full-example)
 
 ```csharp
 using System.Text.Json;
@@ -193,7 +193,7 @@ logger.LogInformation("This is a sample log message");
 await host.RunAsync();
 ```
 
-### [.NET 9 and earlier](#tab/net9-earlier-config)
+### [.NET 9 and earlier](#tab/net9-earlier-full-example)
 
 :::code language="csharp" source="snippets/servicelogenricher/Program.cs" :::
 

docs/core/enrichment/custom-enricher.md

@@ -35,7 +35,7 @@ dotnet package add Microsoft.Extensions.Telemetry.Abstractions
 
 ---
 
-## `ILogEnricher` Implementation
+## ILogEnricher implementation
 
 Your custom enricher only needs to implement a single <xref:Microsoft.Extensions.Diagnostics.Enrichment.ILogEnricher.Enrich(Microsoft.Extensions.Diagnostics.Enrichment.IEnrichmentTagCollector)> method.
 During enrichment, this method is called and given an <xref:Microsoft.Extensions.Diagnostics.Enrichment.IEnrichmentTagCollector> instance. The enricher then calls one of the overloads of
@@ -94,7 +94,7 @@ builder.Services.AddLogEnricher(new AnotherEnricher("anotherKey", "anotherValue"
 
 ## Static log enrichers
 
-.NET provides <xref:Microsoft.Extensions.Diagnostics.Enrichment.IStaticLogEnricher> to enrich logs with immutable properties throughout the application lifecycle. Static enrichers execute once during startup initialization, delivering significant performance benefits over standard enrichers that execute for each log record. This approach is particularly advantageous in high-throughput logging scenarios, as it eliminates the overhead of redundant enrichment operations for data that remains constant, that doesn't change throughout the service's lifetime.
+.NET provides <xref:Microsoft.Extensions.Diagnostics.Enrichment.IStaticLogEnricher> to enrich logs with immutable properties throughout the application lifecycle. Static enrichers execute once during startup initialization, delivering significant performance benefits over standard enrichers that execute for each log record. This approach is particularly advantageous in high-throughput logging scenarios, as it eliminates the overhead of redundant enrichment operations for data that remains constant throughout the service's lifetime. Although executed only once at startup, the enrichment results are attached to every single log message produced by your application.
 
 ```csharp
 public class StaticEnricher : IStaticLogEnricher