Fix typo in .NET SDK docs

Author: stulzq

daprdocs/content/en/dotnet-sdk-docs/dotnet-actors/dotnet-actors-client.md

@@ -91,4 +91,4 @@ var request = new MyRequest() { Message = "Hi, it's me.", };
 var response = await proxy.InvokeMethodAsync<MyRequest, MyResponse>("DoSomethingGreat", request);
 ```
 
-When using a weakly-typed proxy, it is your responsbility to define the correct actor method names and message types. This is done for you when using a strongly-typed proxy since the names and types are part of the interface definition.
+When using a weakly-typed proxy, it is your responsibility to define the correct actor method names and message types. This is done for you when using a strongly-typed proxy since the names and types are part of the interface definition.

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

@@ -26,7 +26,7 @@ The `ActorHost` is provided by the runtime and contains all of the state that th
 
 ### Using dependency injection
 
-Actors support [depenendency injection](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection) of additonal parameters into the constructor. Any other parameters your define will have their values satisfied from the dependency injection container.
+Actors support [depenendency injection](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection) of additional parameters into the constructor. Any other parameters your define will have their values satisfied from the dependency injection container.
 
 ```csharp
 internal class MyActor : Actor, IMyActor, IRemindable
@@ -56,7 +56,7 @@ public void ConfigureServices(IServiceCollection services)
 
 Each actor instance has its own dependency injection scope. Each actor remains in memory for some time after performing an operation, and during that time the dependency injection scope associated with the actor is also considered live. The scope will be releases when the actor is deactivated.
 
-If an actor injects an `IServiceProvider` in the constructor, the actor will recieve a reference to the `IServiceProvider` associated with its scope. The `IServiceProvider` can be used to resolve services dynamically in the future.
+If an actor injects an `IServiceProvider` in the constructor, the actor will receive a reference to the `IServiceProvider` associated with its scope. The `IServiceProvider` can be used to resolve services dynamically in the future.
 
 ```csharp
 internal class MyActor : Actor, IMyActor, IRemindable
@@ -193,7 +193,7 @@ public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
 }
 ```
 
-The `UseRouting` and `UseEndpoints` calls are necessary to configure routing. Adding `MapActorsHandlers` inside the endpoint middleware is what configures actors as part of the pipline.
+The `UseRouting` and `UseEndpoints` calls are necessary to configure routing. Adding `MapActorsHandlers` inside the endpoint middleware is what configures actors as part of the pipeline.
 
 This is a minimal example, it's valid for Actors functionality to existing alongside:
 

daprdocs/content/en/dotnet-sdk-docs/dotnet-development/dotnet-development-docker-compose.md

@@ -35,7 +35,7 @@ Similar to running locally with `dapr run` for each service you need to choose a
 
 The compose file will contain at a minimum:
 
-- A network that the containers use to communiate
+- A network that the containers use to communicate
 - Each service's container
 - A `<service>-daprd` sidecar container with the service's port and app-id specified
 - Additional dependencies that run in containers (redis for example)

daprdocs/content/en/dotnet-sdk-docs/dotnet-troubleshooting/dotnet-troubleshooting-pubsub.md

@@ -12,7 +12,7 @@ The most common problem with pub/sub is that the pub/sub endpoint in your applic
 
 There are a few layers to this problem with different solutions:
 
-- The application is not recieving any traffic from Dapr
+- The application is not receiving any traffic from Dapr
 - The application is not registering pub/sub endpoints with Dapr
 - The pub/sub endpoints are registered with Dapr, but the request is not reaching the desired endpoint
 
@@ -81,7 +81,7 @@ Pay particular attention to the HTTP status code, and the JSON output.
 A 200 status code indicates success.
 
 
-The JSON blob that's included near the end is the output of `/dapr/subscribe` that's procesed by the Dapr runtime. In this case it's using the `ControllerSample` in this repo - so this is an example of correct output.
+The JSON blob that's included near the end is the output of `/dapr/subscribe` that's processed by the Dapr runtime. In this case it's using the `ControllerSample` in this repo - so this is an example of correct output.
 
 ```json
 [
@@ -120,7 +120,7 @@ app.UseEndpoints(endpoints =>
 
 ### Option 2: The response contained JSON but it was empty (like `[]`)
 
-If the JSON output was an empty array (like `[]`) then the subcribe handler is registered, but no topic endpoints were registered.
+If the JSON output was an empty array (like `[]`) then the subscribe handler is registered, but no topic endpoints were registered.
 
 ---