review-1

Author: v-thpra

learn-pr/aspnetcore/create-aspire-applications/includes/exercise-create-new-aspire-application.md

@@ -1,6 +1,6 @@
-Before you begin working on a new service for your company's latest project, you want to check your system has all the prerequisites for .NET Aspire. The best way to check is create a new .NET Aspire project with a starter template.
+Before you begin working on a new service for your company's latest project, you want to check that your system has all the prerequisites for .NET Aspire. The best way to check is to create a new .NET Aspire project with a starter template.
 
-In the exercise you'll install all the prerequisites, and then you'll create a new .NET Aspire Starter app. Then you'll see how to add a caching integration using Redis to the app. Finally, you'll test the application and quickly explore the Aspire Dashboard.
+In the exercise you install all the prerequisites, and then create a new .NET Aspire Starter app. Then, you see how to add a caching integration using Redis to the app. Finally, you test the application and quickly explore the Aspire Dashboard.
 
 # [Visual Studio](#tab/visual-studio)
 
@@ -104,7 +104,7 @@ Install the .NET Aspire workload using the .NET CLI:
     dotnet workload install aspire
     ```
 
-    You should see a message that the aspire workload is installed.
+    You should see a message that the "aspire" workload is installed.
 
     ```console
     Installing Aspire.Hosting.Sdk.Msi.x64 ...... Done
@@ -140,7 +140,7 @@ Now that the prerequisites are installed, let's create a new app.
 
 # [Visual Studio](#tab/visual-studio)
 
-1. Open **Visual Studio**. In the dialog select **Create a new project**.
+1. Open **Visual Studio**. In the dialog, select **Create a new project**.
 1. In the **Search for templates** box, enter **aspire**.
 1. Select **.NET Aspire Starter Application**, and then select **Next**.
 1. In the **Solution name** box, enter **AspireTestApp**.
@@ -219,7 +219,7 @@ Now that the prerequisites are installed, let's create a new app.
           Distributed application started. Press CTRL-C to stop.
     ```
 
-1. <kbd>Ctrl</kbd> + click on the listening URL to open this .NET Aspire dashboard. In the above example, the URL is **http://localhost:15157**.
+1. <kbd>Ctrl</kbd> + click on the listening URL to open this .NET Aspire dashboard. In the previous example, the URL is **http://localhost:15157**.
 
 ---
 
@@ -237,7 +237,7 @@ Close the browser tabs for the Blazor App and the .NET Aspire dashboard. In Visu
 
 ## Add a caching integration to a .NET Aspire project
 
-Now let's add a Redis caching integration to the .NET Aspire project. We'll start with the app host:
+Now let's add a Redis caching integration to the .NET Aspire project. We start with the app host:
 
 # [Visual Studio](#tab/visual-studio)
 
@@ -356,7 +356,7 @@ Now let's run the application to see the caching in action. In Visual Studio:
 
 1. From the menu select **Debug**, and then select **Start Debugging** (Alternatively, press <kbd>F5</kbd>). The solution builds, and the Aspire Dashboard opens in your default web browser.
 1. Select the **Endpoint** URL for the **webfrontend** service to view the home page of the application.
-1. In the browser, refresh the page a few times. The time on the page doesn't change within the 10 second cache duration.
+1. In the browser, refresh the page a few times. The time on the page doesn't change within the 10-second cache duration.
 
     :::image type="content" source="../media/cache-aspire-app.png" alt-text="A screenshot of the updated Aspire Starter template with caching on the home page." lightbox="../media/cache-aspire-app.png":::
 
@@ -368,4 +368,4 @@ Now let's run the application to see the caching in action. In Visual Studio:
 
 1. Open **Docker Desktop**, and select **Containers/Apps**. You should see the **redis:latest** is no longer running.
 
-You've seen how easy it is to add a new caching integration to an application using .NET Aspire. You added a NuGet package, and then added a few lines of code. .NET Aspire automatically configured the Redis container and the output caching for you.
+You just saw how it's easy to add a new caching integration to an application using .NET Aspire. You added a NuGet package, and then added a few lines of code. .NET Aspire automatically configured the Redis container and the output caching for you.

learn-pr/aspnetcore/create-aspire-applications/includes/exercise-integrate-aspire-existing-application.md

@@ -1,4 +1,4 @@
-Now let's explore how to add .NET Aspire to an existing ASP.NET Core web app. Along the way, you'll learn how to add the .NET Aspire stack to an existing ASP.NET Core web app and then run the app. You'll also see how to call microservices from the ASP.NET Core app.
+Now let's explore how to add .NET Aspire to an existing ASP.NET Core web app. Along the way, you learn how to add the .NET Aspire stack to an existing ASP.NET Core web app and then run the app. You also see how to call microservices from the ASP.NET Core app.
 
 ## Set up your environment
 
@@ -84,7 +84,7 @@ In Visual Studio:
 
 ## Update the orchestration to include the products API
 
-There are many ways to resolve this issue. You could explore the code, work out how the front end is configured, edit the code, or change the **launchSettings.json** or **appsettings.json** files.
+There are many ways to resolve this issue. You could explore the code. Work out how the front end is configured, edit the code, or change the **launchSettings.json** or **appsettings.json** files.
 
 With .NET Aspire, you can change the orchestration so that the products API responds on port 5200.
 
@@ -152,7 +152,7 @@ In Visual Studio:
     builder.Build().Run();
     ```
 
-    The above code reorders the projects. The products API is now passed as a project reference to the front end Store web app.
+    This code reorders the projects. The products API is now passed as a project reference to the front end Store web app.
 
 1. In **Solution Explorer**, open the **Store** project, then open the *appsettings.json* file.
 1. Delete the endpoint configuration lines:

learn-pr/aspnetcore/create-aspire-applications/includes/how-add-orchestration-existing-app.md

@@ -1,4 +1,4 @@
-.NET Aspire can be broken down into solutions for three issues that face modern cloud-native apps. These are:
+.NET Aspire can be broken down into solutions for these three issues that face modern cloud-native apps:
 
 1. Managing the complexity of orchestration between microservices.
 1. Simplifying how your microservices use integrations through NuGet packages.
@@ -25,7 +25,7 @@ Configuration through declarative code is better. Using .NET Aspire, you don't n
 .NET Aspire orchestration also supports your development in the following ways:
 
 - **App composition**: .NET Aspire specifies the .NET projects, containers, executables, and cloud resources that make up the application.
-- **Service discovery and connection string management**: The app host manages injecting the right connection strings and service discovery information to simplify the developer experience.
+- **Service discovery and connection string management**: The app host manages injection of the right connection strings and service discovery information to simplify the developer experience.
 
 ## Enlisting an existing app in .NET Aspire orchestration
 

learn-pr/aspnetcore/create-aspire-applications/includes/introduction.md

@@ -1,6 +1,6 @@
 Creating a cloud-native application can be challenging, as it requires in-depth technical knowledge of both coding and infrastructure. Each microservice needs to locate and communicate with others, store data, utilize common services such as caches, and manage messaging queues. Using .NET Aspire simplifies many of these challenges, allowing you to focus more on developing your application’s unique functionality.
 
-Imagine you work for an outdoor equipment retailer. You're new to the development team, and want to see how hard it is to add .NET Aspire to the team's current cloud-native app. You believe .NET Aspire can help your team reduce development effort.
+Imagine you work for an outdoor equipment retailer. You're new to the development team, and want to see if it's difficult to add .NET Aspire to the team's current cloud-native app. You believe .NET Aspire can help your team reduce development effort.
 
 In this module, learn how to use the .NET Aspire project templates in Visual Studio to create new cloud-native apps in just a few steps. To ease further development on an existing code base, see how to enlist an existing app in .NET Aspire orchestration.
 

learn-pr/aspnetcore/create-aspire-applications/includes/learn-how-create-new-aspire-application.md

@@ -21,7 +21,7 @@ There are two .NET Aspire starter templates currently available:
 
 - **.NET Aspire Starter Application**: This template includes the **AspireSample.AppHost** and **AspireSample.ServiceDefaults** projects, but also includes an example Blazor App **AspireSample.Web** and an API that provides data to it **AspireSample.ApiService**. These projects are preconfigured with service discovery and other basic examples of common .NET Aspire functionality.
 
-Both Aspire templates provide a dashboard to monitor the health of the services and the traffic between them. The dashboard helps improve your local development experience — as at a glance it gives you an overview of the state and structure of your app.
+Both Aspire templates provide a dashboard to monitor the health of the services and the traffic between them. The dashboard helps improve your local development experience—as at a glance it gives you an overview of the state and structure of your app.
 
 There are also three project templates available:
 
@@ -88,7 +88,7 @@ Both templates add **AppHost** and **ServiceDefaults** projects. These projects
 
 The **ServiceDefaults** project contains the default configuration for the application. These configurations are reused across all the projects in your solution.
 
-The above solution also includes **Web** and **ApiService** projects. The **Web** project is a Blazor WebAssembly app that has a counter and calls the **ApiService** to get forecast data. The **ApiService** is a simple API that returns forecast data.
+This solution also includes **Web** and **ApiService** projects. The **Web** project is a Blazor WebAssembly app that has a counter and calls the **ApiService** to get forecast data. The **ApiService** is a simple API that returns forecast data.
 
 ### Walk through the code structure
 
@@ -108,13 +108,13 @@ builder.AddProject<Projects.AspireStarterSample_Web>("webfrontend")
 builder.Build().Run();
 ```
 
-Walking through the above code, line by line:
+Walking through the *Program.cs* code, line by line:
 
 - Create a `builder` variable that's a `IDistributedApplicationBuilder`.
 - Create a `cache` variable that's a `IResourceBuilder<RedisResource>`.
 - Call `AddProject` with a generic-type parameter containing the project's `IServiceMetadata` details, adding the **AspireSample.ApiService** project to the application model.
 
-    This is a fundamental building block of .NET Aspire. The `AddProject` configures service discovery and communication between the projects in your app. The name argument **apiservice** is used to identify the project in the application model, and used later by projects that want to communicate with it.
+    This method is a fundamental building block of .NET Aspire. `AddProject` configures service discovery and communication between the projects in your app. The name argument **apiservice** is used to identify the project in the application model, and used later by projects that want to communicate with it.
 
 - Calls `AddProject` again, this time adding the **AspireSample.Web** project to the application model. It also chains multiple calls to `WithReference` passing the **cache** and **apiservice** variables.
 

learn-pr/aspnetcore/create-aspire-applications/includes/summary.md

@@ -1,8 +1,8 @@
 Congratulations! In this module, you learned how to create a brand-new .NET Aspire solution and how to add .NET Aspire to an existing cloud-native application. 
 
-You also saw how .NET Aspire takes care of many tasks that can be challenging for cloud-native apps, such as resolving a service discovery problem, with only a few lines of code. .NET Aspire also simplifies configuration tasks, and adding common services like databases, messaging, and caching.
+You also saw how .NET Aspire takes care of many tasks that can be challenging for cloud-native apps. Such as, resolving a service discovery problem with only a few lines of code. .NET Aspire also simplifies configuration tasks, and adding common services like databases, messaging, and caching.
 
-Having completed this module, you can:
+After completing this module, you can:
 
 - Create new cloud-native apps by using the .NET Aspire templates in Visual Studio.
 - Add the .NET Aspire stack to an existing .NET app for orchestration and simple cloud-native integrations.

learn-pr/aspnetcore/create-aspire-applications/knowledge-check.yml

@@ -3,7 +3,7 @@ uid: learn.create-aspire-application.knowledge-check
 title: Module assessment
 metadata:
   title: Module assessment
-  description: "Test what you've learned."
+  description: "Test what you learned about .NET Aspire."
   ms.date: 2/6/2024
   author: camsoper
   ms.author: casoper
@@ -16,21 +16,21 @@ quiz:
     choices:
     - content: "Docker Desktop or Podman"
       isCorrect: true
-      explanation: "That's correct! A local container host is required to run a project with .NET Aspire."
+      explanation: "Correct! A local container host is required to run a project with .NET Aspire."
     - content: "Docker Compose"
       isCorrect: false
-      explanation: "That's incorrect. Docker Compose isn't required to run a project with .NET Aspire."
+      explanation: "Incorrect. Docker Compose isn't required to run a project with .NET Aspire."
     - content: "Kubernetes"
       isCorrect: false
-      explanation: "That's incorrect. Kubernetes isn't required to run a project with .NET Aspire."
+      explanation: "Incorrect. Kubernetes isn't required to run a project with .NET Aspire."
   - content: "You enlist your application in the .NET Aspire orchestration. Which of the following changes would you expect to see in your solution?"
     choices:
     - content: "A new Redis cache container for outbound HTTP requests."
       isCorrect: false
-      explanation: "That's incorrect. A new Redis cache container isn't added to the solution by default. You can choose to add one when creating a new .NET Aspire project."
+      explanation: "Incorrect. A new Redis cache container isn't added to the solution by default. You can choose to add one when creating a new .NET Aspire project."
     - content: "The web app project is set to the new start-up project."
       isCorrect: false
-      explanation: "That's incorrect. The web app project isn't set to the new start-up project. The AppHost project is."
+      explanation: "Incorrect. The web app project isn't set to the new start-up project. The AppHost project is."
     - content: "A new ServiceDefaults project is added to the solution."
       isCorrect: true
-      explanation: "That's correct! When you enlist your application in .NET Aspire orchestration, AppHost and ServiceDefaults projects are added to the solution."
+      explanation: "Correct! When you enlist your application in .NET Aspire orchestration, AppHost and ServiceDefaults projects are added to the solution."