Line edits

Author: lootle1

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/includes/1-introduction.md

@@ -13,7 +13,7 @@ You'll modify the app to include some code-based resiliency handling policies in
 
 ## Learning objectives
 
-In this module, you will:
+In this module, you'll:
 
 * Understand foundational resiliency concepts.
 * Observe the behavior of a microservice that has no resiliency strategy.
@@ -25,4 +25,4 @@ In this module, you will:
 * Familiarity with C# and .NET development at the beginner level.
 * Familiarity with RESTful service concepts.
 * Conceptual knowledge of containers and AKS at the intermediate level.
-* Ability to run development containers GitHub Codespaces or in Visual Studio Code.
+* Ability to run development containers GitHub Codespaces or in Visual Studio Code.

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/includes/2-application-infrastructure-resiliency.md

@@ -28,11 +28,11 @@ A *Circuit Breaker* strategy gives a target service a break after a repeated num
 
 ### Infrastructure-based resiliency
 
-To implement infrastructure-based resiliency, you can use a *service mesh*. Aside from resiliency without changing code, a service mesh provides traffic management, policy, security, strong identity, and observability. Your app is decoupled from these operational capabilities, which are moved to the infrastructure layer. 
+To implement infrastructure-based resiliency, you can use a *service mesh*. Aside from resiliency without changing code, a service mesh provides traffic management, policy, security, strong identity, and observability. Your app is decoupled from these operational capabilities, which are moved to the infrastructure layer.
 
 #### Comparison to code-based approaches
 
-An infrastructure-based resiliency approach can use a metrics-based view that allows it to adapt dynamically to cluster conditions in real time. This approach adds another dimension to managing the cluster, but doesn't add any code.
+An infrastructure-based resiliency approach can use a metrics-based view that allows it to adapt dynamically to cluster conditions in real time. This approach adds another dimension to managing the cluster but doesn't add any code.
 
 With a code-based approach you:
 
@@ -43,4 +43,4 @@ There's no reasonable way to respond to an infrastructure failure in your app's
 
 In contrast, infrastructure-based approaches are unaware of app internals. For example, complex database transactions are invisible to service meshes. Such transactions can only be protected from failure with a code based approach.
 
-In upcoming units, you'll implement resilience for a microservice based app  using .NET HTTP resiliency in code and a Linkerd service mesh.
+In upcoming units, you'll implement resilience for a microservice based app using .NET HTTP resiliency in code and a Linkerd service mesh.

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/includes/3-implement-application-resiliency.md

@@ -43,7 +43,7 @@ You can add this standard strategy, with all the default values by adding this e
 .AddStandardResilienceHandler();
 ```
 
-For example if you have declared a `WebApplication`, and you want to add a resilience strategy to the HttpClient service use this code: 
+For example if you have declared a `WebApplication`, and you want to add a resilience strategy to the HttpClient service use this code:
 
 ```csharp
 builder.Services.AddHttpClient<ServiceBeingCalled>(httpClient =>

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/includes/5-implement-infrastructure-resiliency.md

@@ -9,7 +9,7 @@ The *control plane* component has many components that support managing the serv
 * Security management for things like strong identity and certificates for mTLS.
 * Metrics or observability to collect and aggregate metrics and telemetry from the apps.
 
-The *data plane* component consists of proxies that are transparently injected alongside each service; this is known as the Sidecar pattern. Each proxy is configured to control the network traffic in and out of the pod that contains your service. This configuration allows each proxy to be configured to:
+The *data plane* component consists of proxies that are transparently injected alongside each service, which is known as the Sidecar pattern. Each proxy is configured to control the network traffic in and out of the pod that contains your service. This configuration allows each proxy to be configured to:
 
 * Secure traffic via mTLS.
 * Dynamically route traffic.

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/includes/6-exercise-implement-infrastructure-resiliency.md

@@ -1,6 +1,6 @@
 In the previous unit, you implemented resiliency by adding failure-handling code using .NET native resilience extension. However, this change only applies to the service that you changed. Updating a large app with many services would be nontrivial.
 
-Instead of using *code-based* resiliency, this unit uses an approach called *infrastructure-based* resiliency that spans the entire app. You will:
+Instead of using *code-based* resiliency, this unit uses an approach called *infrastructure-based* resiliency that spans the entire app. You'll:
 
 * Redeploy the app without any resiliency into Kubernetes.
 * Deploy Linkerd in your Kubernetes cluster.

learn-pr/aspnetcore/microservices-resiliency-aspnet-core/index.yml

@@ -11,7 +11,7 @@ metadata:
 title: Implement resiliency in a cloud-native .NET microservice
 summary: Learn how to make your cloud-native .NET Core microservices app fault-tolerant with minimal impact on the user.
 abstract: |
-  In this module, you will:
+  In this module, you'll:
   - Understand foundational resiliency concepts.
   - Observe the behavior of a microservice with no resiliency strategy.
   - Implement failure handling code for HTTP requests in one microservice.