Line edits2

Author: lootle1

learn-pr/aspnetcore/use-databases-dotnet-aspire-app/includes/exercise-use-databases-persist-data-from-aspire-app.md

@@ -53,7 +53,7 @@ Install the .NET Aspire workload using the .NET CLI:
     You should see the details of the .NET Aspire workload.
 
     ```console
-	Installed Workload Id      Manifest Version      Installation Source
+    Installed Workload Id      Manifest Version      Installation Source
     ---------------------------------------------------------------------------------------------
     aspire                     8.0.0/8.0.100         SDK 8.0.300-preview.24203, VS 17.10.34902.84
 

learn-pr/aspnetcore/use-databases-dotnet-aspire-app/includes/store-data-sql-databases.md

@@ -20,7 +20,7 @@ In the app host project:
 
 - Install the .NET Aspire hosting integration to the app host project.
 - Register a database and create a container for it in the solution's app host.
-- Pass a reference to the projects that needs access to the created container hosting the database.
+- Pass a reference to the projects that need access to the created container hosting the database.
 
 In the projects that use the database:
 
@@ -114,12 +114,12 @@ Once the database is registered in the consuming project, you can interact with
 public class YourService(NpgsqlDataSource dataSource)
 {
     public async Task<IEnumerable<Catalog>> GetCatalog()
-	{
+    {
         const string query = "SELECT * FROM catalog";
         using var dbConnection = dataSource.OpenConnection();
         var results = await dbConnection.QueryAsync<Catalog>(command);
         return queryResult.ToArray();
-	}
+    }
 }
 ```
 
@@ -129,17 +129,17 @@ Or you can then retrieve the database context `YourDbContext` to interact with t
 public class YourService(YourDbContext context)
 {
     public async Task<IEnumerable<Catalog>> GetCatalog()
-	{
+    {
         var items = await context.ObjectItems;
         if (item is null)
         {
             return Results.NotFound();
         }
-		else
-		{
-		    return items;
-		}
-	}
+        else
+        {
+        return items;
+        }
+    }
 }
 ```
 
@@ -171,7 +171,7 @@ Then in the configuration file, you can add the connection string:
 
 ### Using configuration providers
 
-.NET Aspire has a feature of integrations that allows them to support a `Microsoft.Extensions.Configuration`. The PostgreSQL integration supports this feature, and by default it looks for settings using the `Aspire:Npgsql` key. In projects using *appsettings.json*, an example configuration might look like this:
+.NET Aspire has a feature of integrations that allows them to support a `Microsoft.Extensions.Configuration`. The PostgreSQL integration supports this feature, and by default it looks for settings using the `Aspire:Npgsql` key. In projects using _appsettings.json_, an example configuration might look like this:
 
 ```json
 {
@@ -186,7 +186,7 @@ Then in the configuration file, you can add the connection string:
 }
 ```
 
-The previous configuration is setting the connection string, enabling health checks, tracing, and metrics for the PostgreSQL integration. You code then no longer needs to specify the connection string, just use `builder.AddNpgsqlDataSource();`.
+The previous configuration is setting the connection string, enabling health checks, tracing, and metrics for the PostgreSQL integration. Your code then no longer needs to specify the connection string, just use `builder.AddNpgsqlDataSource();`.
 
 If you're using the PostgreSQL Entity Framework Core integration, you can use the `Aspire:Npgsql:EntityFrameworkCore:PostgreSQL` key to configure the database context:
 
@@ -296,7 +296,7 @@ As before, if you use the same database name in app host and the consuming proje
 
 ### Using configuration providers
 
-The SQL Server integration also supports `Microsoft.Extensions.Configuration`. By default, it looks for settings using the `Aspire:SqlServer:SqlClient` key. In projects using *appsettings.json*, an example configuration might look like this:
+The SQL Server integration also supports `Microsoft.Extensions.Configuration`. By default, it looks for settings using the `Aspire:SqlServer:SqlClient` key. In projects using _appsettings.json_, an example configuration might look like this:
 
 ```json
 {
@@ -323,10 +323,10 @@ builder.AddSqlServerClient("sqldata", static settings => settings.HealthChecks =
 
 You can pass any of the supported options:
 
-* `ConnectionString`: The connection string of the SQL Server database
-* `HealthChecks`: A boolean value that indicates whether the database health check is enabled
-* `Tracing`: A boolean value that indicates whether the OpenTelemetry tracing is enabled
-* `Metrics`: A boolean value that indicates whether the OpenTelemetry metrics are enabled
+- `ConnectionString`: The connection string of the SQL Server database.
+- `HealthChecks`: A boolean value that indicates whether the database health check is enabled.
+- `Tracing`: A boolean value that indicates whether the OpenTelemetry tracing is enabled.
+- `Metrics`: A boolean value that indicates whether the OpenTelemetry metrics are enabled.
 
 ### Connect to multiple databases
 
@@ -380,7 +380,7 @@ var myService = builder.AddProject<Projects.MyService>()
 ```
 
 Like the PostgreSQL integration, the MySQL integration also allows you to create a container for database management tools. The previous example adds **PhpMyAdmin** to the solution.
- 
+
 ## Using a MySQL database
 
 The pattern is the same in the projects that need MySQL access. In the _Program.cs_ file, this code registers the database:
@@ -429,7 +429,7 @@ builder.AddMySqlDataSource("MySqConnection");
 ### Configuration providers
 
 The `Aspire:MySqlConnector` key is used to configure the MySQL integration.
- 
+
 ```json
 {
   "Aspire": {

learn-pr/aspnetcore/use-databases-dotnet-aspire-app/includes/test-aspire-projects.md

@@ -1,16 +1,16 @@
 Testing is an essential part of developing high-quality software. Testing can help you find and fix bugs, improve performance, and ensure that your code meets the requirements and expectations of your users. Testing can also help you automate the deployment process and prevent regressions in the future. .NET Aspire provides tools and libraries to simplify the development, testing, and deployment of distributed applications. 
 
-In this unit, you learn how to test .NET Aspire projects using xUnit, a popular testing framework for .NET. You learn how to create different types of tests, such as integration tests and functional tests, and how to run them using the .NET Aspire CLI or Visual Studio. 
+In this unit, you learn how to test .NET Aspire projects using xUnit, a popular testing framework for .NET. You learn how to create different types of tests, such as integration tests and functional tests, and how to run them using the .NET Aspire CLI or Visual Studio.
 
-## Create a test project 
+## Create a test project
 
 The easiest way to create a .NET Aspire test project is to use the testing project template. You can use the `dotnet new` command to create a standard class library project, and then add the references to the .NET Aspire testing libraries and the xUnit packages.
 
 ```dotnetcli
 dotnet new aspire-xunit
 ```
 
-## Explore the test project 
+## Explore the test project
 
 The following example test project was created as part of the **.NET Aspire Starter Application** template. If you're unfamiliar with it, see [Quickstart: Build your first .NET Aspire project](/dotnet/aspire/get-started/build-your-first-aspire-app). The .NET Aspire test project takes a project reference dependency on the target app host. Consider the template project:
 

learn-pr/aspnetcore/use-databases-dotnet-aspire-app/knowledge-check.yml

@@ -28,10 +28,10 @@ quiz:
     choices:
     - content: "Connection strings in the appsettings.json file and inline code."
       isCorrect: false
-      explanation: "That's incorrect. These two ways are supported but there are more."
+      explanation: "That's incorrect. These two ways are supported, but there are more."
     - content: "With inline code and using Microsoft.Extensions.Configuration."
       isCorrect: false
-      explanation: "That's incorrect. These two ways are supported but there are more."
+      explanation: "That's incorrect. These two ways are supported, but there are more."
     - content: "Using Microsoft.Extensions.Configuration, connection strings, and inline code."
       isCorrect: true
       explanation: "That's correct. All of these ways are supported."