Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: TechWatching

content/1.posts/66.developer-experience-thoughts.md

@@ -56,4 +56,4 @@ With [Pulumi](https://www.pulumi.com/product/infrastructure-as-code/) you can au
 
 I’m not saying you should use these technologies, it depends on your context and preferences. These are just 2 examples of technologies that I love, partly due to their developer experience and why it matters.
 
-So, what’s next ? I want to start a new series of articles “Aspirations” talking about [Aspire](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview?wt.mc_id=MVP_430820). Aspire primarily aims at improving the local development experience when developing modern .NET applications (distributed or not). That seems an interesting topic to keep talking about developer experience. See you in the next article, and keep learning.
+So, what’s next? I want to start a new series of articles “Aspirations” talking about [Aspire](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview?wt.mc_id=MVP_430820). Aspire primarily aims at improving the local development experience when developing modern .NET applications (distributed or not). That seems an interesting topic to keep talking about developer experience. See you in the next article, and keep learning.

content/1.posts/71.aspire-open-telemetry.md

@@ -27,7 +27,7 @@ That's great, but if we want to see telemetry from our web application, we first
 
 The [OpenTelemetry SDK for .NET](https://github.com/open-telemetry/opentelemetry-dotnet) includes everything we need to collect the telemetry data (logs, traces, metrics). So we could directly install the nuget packages in the `WebApi` project, and implement the code to configure the instrumentation and use the Aspire dashboard OTLP endpoint. It would work, and if you already have an app using OpenTelemetry, you likely only need to make a few configuration changes to make it compatible with the Aspire dashboard.
 
-In our case, we will use instead a [Aspire service defaults project](https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/service-defaults?wt.mc_id=MVP_430820) to set everything up easily. The purpose of using this Aspire Shared project is to offer predefined extension methods that help configure things like OpenTelemetry, health check endpoints, retry policies, and more across the various services and resources that make up the application. Let’s create this project using the `aspire-servicedefaults` template (from the [Aspire template](https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/aspire-sdk-templates?pivots=dotnet-cli&wt.mc_id=MVP_430820)) and reference it in the `WebApi` project.
+In our case, we will use instead an [Aspire service defaults project](https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/service-defaults?wt.mc_id=MVP_430820) to set everything up easily. The purpose of using this Aspire Shared project is to offer predefined extension methods that help configure things like OpenTelemetry, health check endpoints, retry policies, and more across the various services and resources that make up the application. Let’s create this project using the `aspire-servicedefaults` template (from the [Aspire template](https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/aspire-sdk-templates?pivots=dotnet-cli&wt.mc_id=MVP_430820)) and reference it in the `WebApi` project.
 
 ```bash
 dotnet new aspire-servicedefaults -o ServiceDefaults
@@ -218,7 +218,7 @@ And with just that, we can now see both the traces from the `WebApi` and the `We
 
 ![Traces of the WebApi and WebApp in the Aspire dashboard.](/posts/images/71.aspire-otel_7.png){.rounded-lg.mx-auto}
 
-![Details of a traces in the Aspire dashboard.](/posts/images/71.aspire-otel_8.png){.rounded-lg.mx-auto}
+![Details of a trace in the Aspire dashboard.](/posts/images/71.aspire-otel_8.png){.rounded-lg.mx-auto}
 
 ::callout{icon="i-heroicons-light-bulb"}
 Please note that traces are correlated when using client side rendering (like on the screenshot above), but not when using server side rendering. There is probably an additional thing to configure in the Nuxt instrumentation.

content/1.posts/73.aspire-devcert.md

@@ -56,7 +56,7 @@ What we would need instead is to use environment variables that contain these pa
 
 That seems better. But now we need a way to ensure the certificate files exist, generate them if they don’t, and automatically inject these environment variables. Ideally, this would be configured in the `AppHost` by calling a specific method when defining the `WebApp` resource.
 
-And guess what, there is an [issue](https://github.com/dotnet/aspire/issues/6890) on the Aspire GitHub repository discussing exactly such a method. Unfortunately, at the time of writing this method is not built-in but can be found in the [`aspire-samples` repository](https://github.com/dotnet/aspire-samples/blob/0c27e4e3bac5f102db1002fd2e0e1ba894e1009a/samples/Shared/DevCertHostingExtensions.cs). We just need to copy it and place it in our `AppHost` project
+And guess what, there is an [issue](https://github.com/dotnet/aspire/issues/6890) on the Aspire GitHub repository discussing exactly such a method. Unfortunately, at the time of writing this method is not built-in but can be found in the [`aspire-samples` repository](https://github.com/dotnet/aspire-samples/blob/0c27e4e3bac5f102db1002fd2e0e1ba894e1009a/samples/Shared/DevCertHostingExtensions.cs). We just need to copy it and place it in our `AppHost` project.
 
 ::collapsible{openText="Show the code of the" closeText="Hide the code of the" name="DevCertHostingExtensions.cs file"}