review-1

Author: v-thpra

learn-pr/aspnetcore/blazor-build-reusable-components/1-introduction.yml

@@ -4,7 +4,7 @@ title: Introduction to Razor class libraries
 metadata:
   unitType: introduction
   title: Introduction to Razor class libraries
-  description: "By using Razor class libraries, you can share user-interface components between ASP.NET Core and Blazor applications. You package the components by using NuGet, and they can be easily referenced by other applications."
+  description: "By using Razor class libraries, you can share user-interface components between ASP.NET Core and Blazor applications. You package the components using NuGet and other applications can easily reference them."
   ms.date: 01/26/2024
   author: csharpfritz
   ms.author: jefritz

learn-pr/aspnetcore/blazor-build-reusable-components/2-concepts-razor-class-library.yml

@@ -4,7 +4,7 @@ title: Razor class library creation and concepts
 metadata:
   unitType: learning-content
   title: Razor class library creation and concepts
-  description: "In this unit, you'll learn about Razor class libraries, how to create one, and how they differ from other .NET class libraries."
+  description: "In this unit, you learn about Razor class libraries, how to create one, and how they differ from other .NET class libraries."
   ms.date: 01/26/2024
   author: csharpfritz
   ms.author: jefritz
@@ -29,6 +29,6 @@ quiz:
       - content: "JavaScript files"
         isCorrect: false
         explanation: "Incorrect. Razor class libraries can deliver more than just JavaScript files."
-      - content: "All of the above"
+      - content: "All of these content types"
         isCorrect: true
         explanation: "Razor class libraries can deliver Razor components, CSS files, JavaScript files, images, and any static web content that your components need."

learn-pr/aspnetcore/blazor-build-reusable-components/includes/1-introduction.md

@@ -1,4 +1,4 @@
-By using Razor class libraries, you can share and reuse user-interface components between Blazor applications. In this module, you'll focus on building and sharing components for Blazor applications.
+By using Razor class libraries, you can share and reuse user-interface components between Blazor applications. In this module, you focus on building and sharing components for Blazor applications.
 
 ![Diagram showing a Razor class library being used in the Blazor server instance and Blazor WebAssembly.](../media/blazor-class-library-usage.png)
 
@@ -10,17 +10,17 @@ By using Razor class libraries, you can share the features across the applicatio
 
 ![Screenshot of an example modal window component that can be shared across Blazor applications.](../media/modal-window.png)
 
-## What will we be doing?
+## What are you going to do?
 
-In this module, you'll create a Razor class library to accomplish the following goals:
+In this module, you create a Razor class library to accomplish the following goals:
 
-- Present a modal dialog box with default theming
-- Use and customize the modal dialog in a Blazor application
-- Package the modal window dialog for use with other applications
+- Present a modal dialog box with default theming.
+- Use and customize the modal dialog in a Blazor application.
+- Package the modal window dialog for use with other applications.
 
 ## What is the main goal?
 
-By the end of the module, you'll be able to design a modal window component that you can share and customize across other Blazor applications.
+By the end of the module, you're able to design a modal window component that you can share and customize across other Blazor applications.
 
 ## Prerequisites
 

learn-pr/aspnetcore/blazor-build-reusable-components/includes/2-concepts-razor-class-library.md

@@ -1,6 +1,6 @@
 Components in web applications give developers the ability to reuse portions of an application user interface throughout the application. By using Razor class libraries, developers can share and reuse these components across many applications.
 
-In this unit, you'll learn how to create a Razor class library and then use it to share rendered and static content for Blazor applications to customize and display.
+In this unit, you learn how to create a Razor class library. You then use it to share rendered and static content for Blazor applications to customize and display.
 
 ## About Razor class libraries
 
@@ -55,7 +55,7 @@ A class library is a common package delivery structure in .NET applications, and
 
 - The project file contains an SDK reference to *Microsoft.NET.Sdk.Razor* to declare that it contains and creates Razor content as a Razor class library.
 - The `SupportedPlatform` entry declares that this library can be used in a `browser` platform, namely WebAssembly.
-- The `PackageReference` to the `Microsoft.AspNetCore.Components.Web` library gives access to the base Blazor components that are shipped with the framework. This lets you use those simple components to help you build more complex components.
+- The `PackageReference` to the `Microsoft.AspNetCore.Components.Web` library gives access to the base Blazor components that are shipped with the framework. This access lets you use those simple components to help you build more complex components.
 
 ### Razor component contents
 
@@ -71,7 +71,7 @@ This component interacts with other Blazor components and pages that reference i
 
 ### Static asset delivery
 
-You can reference the contents of the *wwwroot* folder relatively among the other contents of that folder and the components' individual CSS files, such as *Component1.razor.css*, as files in the same base folder. For example, the default CSS adds a 2 pixel dashed red border and a background image style that uses the *background.png* image in the *wwwroot* folder. No path is required to make this reference from the CSS to the content that resides in the *wwwroot* folder.
+You can reference the contents of the *wwwroot* folder relatively among the other contents of that folder and the components' individual CSS files, such as *Component1.razor.css*, as files in the same base folder. For example, the default CSS adds a two pixel dashed red border and a background image style that uses the *background.png* image in the *wwwroot* folder. No path is required to make this reference from the CSS to the content that resides in the *wwwroot* folder.
 
 ```css
 .my-component {