Update casdk-docs/blog/2024-05-16-dotnet8/index.md

Co-authored-by: Vaughan Knight <[email protected]>
Signed-off-by: Yasumasa Suenaga <[email protected]>

casdk-docs/blog/2024-05-16-dotnet8/index.md

@@ -67,7 +67,7 @@ While the .NET 8 upgrade was done, some unexpected issues surfaced.
 
 To help onboard newcomers to the Carbon Aware SDK, a sample running on Azure Functions is provided.
 
-Azure Functions for .NET is transitioning one of its execution modes (the In-process model) for the Isolated worker model ([more details here](https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-in-process-differences)). Moreover, .NET 8 did not provide yet an option to use the former model in its initial release (cf. [roadmap of Azure Functions](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/net-on-azure-functions-august-2023-roadmap-update/ba-p/3910098)).
+Azure Functions for .NET is transitioning one of its execution modes (the In-process model) to the Isolated worker model ([more details here](https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-in-process-differences)). Moreover, .NET 8 did not yet provide an option to use the former model in its initial release (cf. [roadmap of Azure Functions](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/net-on-azure-functions-august-2023-roadmap-update/ba-p/3910098)).
 
 As our sample was still implementing the in-process model (to be deprecated and not available in .NET 8 at this time), it made sense to migrate to the isolated worker model.