Remove localized urls

Signed-off-by: Marc Duiker <marcduiker@users.noreply.github.com>

Author: marcduiker

sdkdocs/dotnet/content/en/dotnet-sdk-contributing/dotnet-contributing.md

@@ -102,7 +102,7 @@ squashing the PR locally and resubmitting to ensure that the sign-off statement
 # Languages, Tools and Processes
 All source code in the Dapr .NET SDK is written in C# and targets the latest language version available to the earliest
 supported .NET SDK. As of v1.16, this means that both .NET 8 and .NET 9 are supported. The latest language version available
-is [C# version 12](https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-version-history#c-version-12)
+is [C# version 12](https://learn.microsoft.com/dotnet/csharp/whats-new/csharp-version-history#c-version-12)
 
 Contributors are welcome to use whatever IDE they're most comfortable developing in, but please do not submit 
 IDE-specific preference files along with your contributions as these will be rejected.

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-actors/dotnet-actors-serialization.md

@@ -44,9 +44,9 @@ internal class MyActor : Actor, IMyActor, IRemindable
 }
 ```
 
-An actor type should have a single `public` constructor. The actor infrastructure uses the [`ActivatorUtilities`](https://docs.microsoft.com/en-us/dotnet/core/extensions/dependency-injection#constructor-injection-behavior) pattern for constructing actor instances.
+An actor type should have a single `public` constructor. The actor infrastructure uses the [`ActivatorUtilities`](https://docs.microsoft.com/dotnet/core/extensions/dependency-injection#constructor-injection-behavior) pattern for constructing actor instances.
 
-You can register types with dependency injection in `Startup.cs` to make them available. Read more about [the different ways of registering your types](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?#service-registration-methods).
+You can register types with dependency injection in `Startup.cs` to make them available. Read more about [the different ways of registering your types](https://docs.microsoft.com/aspnet/core/fundamentals/dependency-injection?#service-registration-methods).
 
 ```csharp
 // In Startup.cs
@@ -74,15 +74,15 @@ internal class MyActor : Actor, IMyActor, IRemindable
 }
 ```
 
-When using this pattern, avoid creating many instances of **transient** services which implement `IDisposable`. Since the scope associated with an actor could be considered valid for a long time, you can accumulate many services in memory. See the [dependency injection guidelines](https://docs.microsoft.com/en-us/dotnet/core/extensions/dependency-injection-guidelines) for more information.
+When using this pattern, avoid creating many instances of **transient** services which implement `IDisposable`. Since the scope associated with an actor could be considered valid for a long time, you can accumulate many services in memory. See the [dependency injection guidelines](https://docs.microsoft.com/dotnet/core/extensions/dependency-injection-guidelines) for more information.
 
 ### IDisposable and actors
 
 Actors can implement `IDisposable` or `IAsyncDisposable`. It's recommended that you rely on dependency injection for resource management rather than implementing dispose functionality in application code. Dispose support is provided in the rare case where it is truly necessary. 
 
 ### Logging
 
-Inside an actor class, you have access to an `ILogger` instance through a property on the base `Actor` class. This instance is connected to the ASP.NET Core logging system and should be used for all logging inside an actor. Read more about [logging](https://docs.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line). You can configure a variety of different logging formats and output sinks.
+Inside an actor class, you have access to an `ILogger` instance through a property on the base `Actor` class. This instance is connected to the ASP.NET Core logging system and should be used for all logging inside an actor. Read more about [logging](https://docs.microsoft.com/dotnet/core/extensions/logging?tabs=command-line). You can configure a variety of different logging formats and output sinks.
 
 Use _structured logging_ with _named placeholders_ like the example below:
 
@@ -178,7 +178,7 @@ public void ConfigureServices(IServiceCollection services)
 
 ### Actors and routing
 
-The ASP.NET Core hosting support for actors uses the [endpoint routing](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing) system. The .NET SDK provides no support hosting actors with the legacy routing system from early ASP.NET Core releases.
+The ASP.NET Core hosting support for actors uses the [endpoint routing](https://docs.microsoft.com/aspnet/core/fundamentals/routing) system. The .NET SDK provides no support hosting actors with the legacy routing system from early ASP.NET Core releases.
 
 Since actors uses endpoint routing, the actors HTTP handler is part of the middleware pipeline. The following is a minimal example of a `Configure` method setting up the middleware pipeline with actors.
 

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-actors/dotnet-actors-usage.md

@@ -39,7 +39,7 @@ may change from one release to the next, so please be aware of this possibility
 The `Dapr.AI.Microsoft.Extensions` package implements the `Microsoft.Extensions.AI` abstractions, providing a unified API for
 AI services in .NET applications. `Microsoft.Extensions.AI` is designed to offer a consistent programming model across
 different AI providers and scenarios. For detailed information about `Microsoft.Extensions.AI`, refer to the 
-[official documentation](https://learn.microsoft.com/en-us/dotnet/ai/microsoft-extensions-ai).
+[official documentation](https://learn.microsoft.com/dotnet/ai/microsoft-extensions-ai).
 
 {{% alert title="Limited Support" color="warning" %}}
 
@@ -138,5 +138,5 @@ building block configuration. The `DaprChatClient` will respect these settings w
 ## Related Links
 
 - [Dapr Conversation Building Block]({{ ref conversation-overview.md }})
-- [Microsoft.Extensions.AI Documentation](https://learn.microsoft.com/en-us/dotnet/ai/microsoft-extensions-ai)
+- [Microsoft.Extensions.AI Documentation](https://learn.microsoft.com/dotnet/ai/microsoft-extensions-ai)
 - [Dapr .NET Conversation SDK]({{% ref dotnet-ai-conversation-howto.md %}})

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-ai/dotnet-ai-extensions-howto.md

@@ -135,9 +135,9 @@ When an operation is cancelled, it will throw an `OperationCancelledException`.
 
 Many methods on `DaprClient` perform JSON serialization using the `System.Text.Json` serializer. Methods that accept an application data type as an argument will JSON serialize it, unless the documentation clearly states otherwise.
 
-It is worth reading the [System.Text.Json documentation](https://docs.microsoft.com/en-us/dotnet/standard/serialization/system-text-json-overview) if you have advanced requirements. The Dapr .NET SDK provides no unique serialization behavior or customizations - it relies on the underlying serializer to convert data to and from the application's .NET types.
+It is worth reading the [System.Text.Json documentation](https://docs.microsoft.com/dotnet/standard/serialization/system-text-json-overview) if you have advanced requirements. The Dapr .NET SDK provides no unique serialization behavior or customizations - it relies on the underlying serializer to convert data to and from the application's .NET types.
 
-`DaprClient` is configured to use a serializer options object configured from [JsonSerializerDefaults.Web](https://docs.microsoft.com/en-us/dotnet/api/system.text.json.jsonserializerdefaults?view=net-5.0). This means that `DaprClient` will use `camelCase` for property names, allow reading quoted numbers (`"10.99"`), and will bind properties case-insensitively. These are the same settings used with ASP.NET Core and the `System.Text.Json.Http` APIs, and are designed to follow interoperable web conventions.
+`DaprClient` is configured to use a serializer options object configured from [JsonSerializerDefaults.Web](https://docs.microsoft.com/dotnet/api/system.text.json.jsonserializerdefaults?view=net-5.0). This means that `DaprClient` will use `camelCase` for property names, allow reading quoted numbers (`"10.99"`), and will bind properties case-insensitively. These are the same settings used with ASP.NET Core and the `System.Text.Json.Http` APIs, and are designed to follow interoperable web conventions.
 
 `System.Text.Json` as of .NET 5.0 does not have good support for all of F# language features built-in. If you are using F# you may want to use one of the converter packages that add support for F#'s features such as [FSharp.SystemTextJson](https://github.com/Tarmil/FSharp.SystemTextJson).
 
@@ -150,7 +150,7 @@ Your experience using JSON serialization and `DaprClient` will be smooth if you
 - Do not put complex or expensive logic in constructors or property accessors
 - Use .NET types that map cleanly to JSON types (numeric types, strings, `DateTime`)
 - Create your own classes for top-level messages, events, or state values so you can add properties in the future
-- Design types with `get`/`set` properties OR use the [supported pattern](https://docs.microsoft.com/en-us/dotnet/standard/serialization/system-text-json-immutability?pivots=dotnet-5-0) for immutable types with JSON
+- Design types with `get`/`set` properties OR use the [supported pattern](https://docs.microsoft.com/dotnet/standard/serialization/system-text-json-immutability?pivots=dotnet-5-0) for immutable types with JSON
 
 ### Polymorphism and serialization
 

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-client/dotnet-daprclient-usage.md

@@ -108,7 +108,7 @@ For suppressing warnings across multiple projects in a directory, add a `Directo
 
 This file should be placed in the root directory of your test projects. You can learn more about using 
 `Directory.Build.props` files in the 
-[MSBuild documentation](https://learn.microsoft.com/en-us/visualstudio/msbuild/customize-by-directory).
+[MSBuild documentation](https://learn.microsoft.com/visualstudio/msbuild/customize-by-directory).
 
 ### Lifecycle of Experimental APIs
 
@@ -135,4 +135,4 @@ Conversely, the `[Obsolete]` attribute will now be reserved exclusively for APIs
 ### Additional Resources
 
 - [Dapr Component Certification Lifecycle](https://docs.dapr.io/operations/components/certification-lifecycle/)
-- [C# Experimental Attribute Documentation](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-12.0/experimental-attribute)
+- [C# Experimental Attribute Documentation](https://learn.microsoft.com/dotnet/csharp/language-reference/proposals/csharp-12.0/experimental-attribute)

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-guidance/dotnet-guidance-experimental-attributes.md

@@ -49,7 +49,7 @@ should jump directly to the part of your code responsible for the violating the
 ### Suppress specific analyzers
 If you wish to keep an analyzer from firing against some particular piece of your project, their outputs can be
 individually targeted for suppression through a number of ways. Read more about suppressing analyzers in projects
-or files in the associated [.NET documentation](https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/suppress-warnings#use-the-suppressmessageattribute).
+or files in the associated [.NET documentation](https://learn.microsoft.com/dotnet/fundamentals/code-analysis/suppress-warnings#use-the-suppressmessageattribute).
 
 ### Disable all analyzers
 If you wish to disable all analyzers in your project without removing any packages providing them, set

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-guidance/dotnet-guidance-source-generators.md

@@ -8,7 +8,7 @@ description: Learn about local development with .NET Aspire
 
 # .NET Aspire
 
-[.NET Aspire](https://learn.microsoft.com/en-us/dotnet/aspire/get-started/aspire-overview) is a development tool 
+[.NET Aspire](https://learn.microsoft.com/dotnet/aspire/get-started/aspire-overview) is a development tool 
 designed to make it easier to include external software into .NET applications by providing a framework that allows 
 third-party services to be readily integrated, observed and provisioned alongside your own software.
 
@@ -21,7 +21,7 @@ integrations as well, including Dapr.
 
 While Aspire also assists with deployment of your application to various cloud hosts like Microsoft Azure and 
 Amazon AWS, deployment is currently outside the scope of this guide. More information can be found in Aspire's 
-documentation [here](https://learn.microsoft.com/en-us/dotnet/aspire/deployment/overview).
+documentation [here](https://learn.microsoft.com/dotnet/aspire/deployment/overview).
 
 An end-to-end demonstration featuring the following and demonstrating service invocation between multiple Dapr-enabled
 services can be found [here](https://github.com/dapr/dotnet-sdk/tree/master/examples/Hosting/Aspire/ServiceInvocationDemo).

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-integrations/dotnet-development-dapr-aspire.md

@@ -194,7 +194,7 @@ public class MySampleClass
 
 ## Set up a endpoint to be invoked when the job is triggered
 
-It's easy to set up a jobs endpoint if you're at all familiar with [minimal APIs in ASP.NET Core](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis/overview) as the syntax is the same between the two.
+It's easy to set up a jobs endpoint if you're at all familiar with [minimal APIs in ASP.NET Core](https://learn.microsoft.com/aspnet/core/fundamentals/minimal-apis/overview) as the syntax is the same between the two.
 
 Once dependency injection registration has been completed, configure the application the same way you would to handle mapping an HTTP request via the minimal API functionality in ASP.NET Core. Implemented as an extension method,
 pass the name of the job it should be responsive to and a delegate. Services can be injected into the delegate's arguments as you wish and the job payload can be accessed from the `ReadOnlyMemory<byte>` originally provided to the 

sdkdocs/dotnet/content/en/dotnet-sdk-docs/dotnet-jobs/dotnet-jobs-howto.md

@@ -20,7 +20,7 @@ There are a few layers to this problem with different solutions:
 
 **This is important. Future steps will depend on your ability to see logging output. ASP.NET Core logs almost nothing with the default log settings, so you will need to change it.**
 
-Adjust the logging verbosity to include `Information` logging for ASP.NET Core as described [here](https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/routing?view=aspnetcore-5.0#debug-diagnostics). Set the `Microsoft` key to `Information`.
+Adjust the logging verbosity to include `Information` logging for ASP.NET Core as described [here](https://docs.microsoft.com/aspnet/core/mvc/controllers/routing?view=aspnetcore-5.0#debug-diagnostics). Set the `Microsoft` key to `Information`.
 
 ## Step 2: Verify you can receive traffic from Dapr