review-2

Author: v-thpra

learn-pr/aspnetcore/blazor-build-reusable-components/3-create-razor-class-library.yml

@@ -4,7 +4,7 @@ title: Create a Razor class library
 metadata:
   unitType: exercise
   title: Create a Razor class library
-  description: "In this exercise, you'll create your first Razor class library with a component that can be used in Blazor and ASP.NET Core applications."
+  description: "In this exercise, you create your first Razor class library with a component that can be used in Blazor and ASP.NET Core applications."
   ms.date: 01/26/2024
   author: csharpfritz
   ms.author: jefritz

learn-pr/aspnetcore/blazor-build-reusable-components/4-concept-package-razor-class-library.yml

@@ -4,7 +4,7 @@ title: Package a Razor class library
 metadata:
   unitType: learning-content
   title: Package a Razor class library
-  description: "In this unit, you'll learn how Razor class libraries are packaged when they're shared with other developers."
+  description: "In this unit, you learn how Razor class libraries are packaged when they're shared with other developers."
   ms.date: 01/26/2024
   author: csharpfritz
   ms.author: jefritz
@@ -14,16 +14,16 @@ durationInMinutes: 3
 content: |
   [!include[](includes/4-concept-package-razor-class-library.md)]
 quiz:
-    title: Check your knowledge
-    questions:
+  title: Check your knowledge
+  questions:
     - content: "What project property is the default value for PackageId?"
       choices:
-      - content: "Default namespace"
-        isCorrect: false
-        explanation: "Incorrect. The default namespace of the project might match the property that's used for the default PackageId, but this isn't the correct value."
-      - content: "Project Name"
-        isCorrect: false
-        explanation: "Incorrect. The Project Name might match the property that's used for the default PackageId, but this isn't the correct value."
-      - content: "AssemblyName"
-        isCorrect: true
-        explanation: "AssemblyName is the default value for  PackageId."
+        - content: "Default namespace"
+          isCorrect: false
+          explanation: "Incorrect. The default namespace of the project might match the property that's used for the default PackageId, but it isn't the correct value."
+        - content: "Project Name"
+          isCorrect: false
+          explanation: "Incorrect. The Project Name might match the property that's used for the default PackageId, but it isn't the correct value."
+        - content: "AssemblyName"
+          isCorrect: true
+          explanation: "AssemblyName is the default value for  PackageId."

learn-pr/aspnetcore/blazor-build-reusable-components/5-nuget-package.yml

@@ -4,7 +4,7 @@ title: Create a NuGet package
 metadata:
   unitType: exercise
   title: Create a NuGet package
-  description: "In this exercise, you'll package the Razor class library that you created earlier."
+  description: "In this exercise, you package the Razor class library that you created earlier."
   ms.date: 01/26/2024
   author: csharpfritz
   ms.author: jefritz

learn-pr/aspnetcore/blazor-build-reusable-components/6-summary.yml

@@ -3,8 +3,8 @@ uid: learn.blazor-build-reusable-components.summary
 title: Summary
 metadata:
   unitType: summary
-  title: summary
-  description: "This unit summarizes what you've learned about creating Razor class libraries."
+  title: Summary
+  description: "This unit summarizes what you learned about creating Razor class libraries."
   ms.date: 01/26/2024
   author: csharpfritz
   ms.author: jefritz

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

@@ -2,9 +2,9 @@ Components in web applications give developers the ability to reuse portions of
 
 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
+## Razor class libraries
 
-A Razor class library is a .NET project type that contains Razor components, pages, HTML, Cascading Style Sheet (CSS) files, JavaScript, images, and other static web content that can be referenced by a Blazor application. Like other .NET class library projects, Razor class libraries can be bundled as a NuGet package and shared on NuGet package repositories such as NuGet.org.
+A Razor class library is a .NET project type. It contains Razor components, pages, HTML, Cascading Style Sheet (CSS) files, JavaScript, images, and other static web content that a Blazor application can reference. Like other .NET class library projects, Razor class libraries can be bundled as a NuGet package and shared on NuGet package repositories such as NuGet.org.
 
 Let's look at the default template for creating a Razor class library.
 
@@ -59,7 +59,7 @@ A class library is a common package delivery structure in .NET applications, and
 
 ### Razor component contents
 
-The initial Razor component that's delivered is simple. It contains only an HTML `div` element with a short block of text:
+This initial Razor component is simple. It contains only an HTML `div` element with a short block of text:
 
 ```razor
 <div class="my-component">
@@ -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 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.
+You can reference the contents of the *wwwroot* folder relatively among the other contents of that folder. You can also relatively reference 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 {
@@ -82,7 +82,7 @@ You can reference the contents of the *wwwroot* folder relatively among the othe
 }
 ```
 
-The contents of the *wwwroot* folder are available to be referenced by hosted Blazor applications with an absolute folder reference in the format:
+The contents of the *wwwroot* folder are available for referencing by hosted Blazor applications with an absolute folder reference in the format:
 
 ```dotnetcli
 /_content/{PACKAGE_ID}/{PATH_AND_FILENAME_INSIDE_WWWROOT}

learn-pr/aspnetcore/blazor-build-reusable-components/includes/3-create-razor-class-library.md

@@ -1,4 +1,4 @@
-In this exercise, you'll create a modal dialog in a Razor class library that you can reuse in the default Blazor template application.
+In this exercise, you create a modal dialog in a Razor class library that you can reuse in the default Blazor template application.
 
 ![Screenshot of the modal dialog to be created in the standard Blazor template application.](../media/first-modal.png)
 
@@ -162,7 +162,7 @@ With the modal component now residing in the *FirstClassLibrary* project, add a
     dotnet new blazor -o MyBlazorApp -f net8.0
     ```
 
-1. In the *MyBlazorApp* project, add a reference to the *FirstClassLibrary* project either by using the Visual Studio Add Reference feature or by running the following command from the *MyBlazorApp* folder:
+1. Add a reference to the *FirstClassLibrary* project in the *MyBlazorApp* project, either by using the Visual Studio Add Reference feature or by running the following command from the *MyBlazorApp* folder:
 
     ```dotnetcli
     dotnet add reference ../FirstClassLibrary

learn-pr/aspnetcore/blazor-build-reusable-components/includes/4-concept-package-razor-class-library.md

@@ -1,12 +1,12 @@
-A task you'll often perform is packaging libraries for reuse by other developers. NuGet packaging makes it trivial for any developer anywhere to acquire and properly configure all the .NET references for their applications. 
+A task that you often need to perform is packaging libraries for reuse by other developers. NuGet packaging makes it trivial for any developer anywhere to acquire and properly configure all the .NET references for their applications.
 
-In the preceding unit, you built your modal dialog component and used it in your own application. Now you'll want to reuse it in other applications. 
+In the preceding unit, you built your modal dialog component and used it in your own application. Now you want to reuse it in other applications. 
 
-In this unit, you'll learn the steps necessary to configure a Razor class library as a NuGet package. You'll also learn how to package the library for distribution by using a package-repository service, such as NuGet.org, or GitHub repositories.
+In this unit, you learn the steps necessary to configure a Razor class library as a NuGet package. You also learn how to package the library for distribution by using a package-repository service, such as NuGet.org, or GitHub repositories.
 
 ## Configure a Razor class library for NuGet packaging
 
-The .NET ecosystem makes it easy to define the properties that are necessary for other developers to identify and use your components. You can define all these properties in the project file (*\*.csproj*) of your Razor class library so that they travel with the library and are updated appropriately when your library is updated. 
+The .NET ecosystem makes it easy to define the properties that are necessary for other developers to identify and use your components. You can define all these properties in the project file (*\*.csproj*) of your Razor class library so they travel with the library. The properties are then updated appropriately when your library is updated.
 
 You can configure fields that identify your package in the **Visual Studio Project Properties - Package** dialog, or you can create entries directly in the *\*.csproj* file yourself.
 
@@ -23,7 +23,7 @@ Some of these fields have default values, and it might look funny to publish a p
 
 In the preceding unit, you learned that the static content of a Razor class library is available at `_content/[PACKAGE_ID]/`, and now you see where the `PackageId` value is configured.
 
-A sample project file with these values configured might look like the following:
+A sample project file with these values configured might look like the following example:
 
 ```xml
 <PropertyGroup>
@@ -34,7 +34,7 @@ A sample project file with these values configured might look like the following
 </PropertyGroup>
 ```
 
-When you're building the project, you can also configure it to generate a NuGet package either by selecting the **Generate NuGet Package on Build** option in the Visual Studio **Project Properties** dialog or by adding a `GeneratePackageOnBuild` entry next to the other package fields, as shown here:
+When you're building the project, you can also configure it to generate a NuGet package either by selecting the option to **Generate NuGet Package on Build** in the Visual Studio **Project Properties** dialog or by adding a `GeneratePackageOnBuild` entry next to the other package fields, as shown here:
 
 ```xml
 <GeneratePackageOnBuild>True</GeneratePackageOnBuild>
@@ -52,7 +52,7 @@ For a full list of properties, check the Microsoft documentation on the [MSBuild
 
 ## Package the library
 
-After you've written the library configuration into the *\*.csproj* file, you can generate the NuGet package either in Visual Studio, by right-clicking the project and selecting the **Pack** command, or in the project folder, by running the following command:
+After you write the library configuration into the *\*.csproj* file, you can generate the NuGet package either in Visual Studio, by right-clicking the project and selecting the **Pack** command, or in the project folder, by running the following command:
 
 ```dotnetcli
 dotnet pack

learn-pr/aspnetcore/blazor-build-reusable-components/includes/5-nuget-package.md

@@ -1,14 +1,14 @@
-When you package your Razor class library, you have a binary deliverable that can be referenced by Blazor projects, and the components within it can be used in those projects.
+When you package your Razor class library, you have a binary deliverable that other Blazor projects can reference and the components within it can be used in those projects.
 
 In an earlier unit, you created a Razor class library with a modal component that delivers a modal dialog window for Blazor applications. To share that component for use in other applications, you need to package and place it in either a repository or a folder where other developers can acquire it.
 
-In this unit, you'll update that project and generate a NuGet package. Finally, you'll deploy that NuGet package to your Blazor server application.
+In this unit, you update that project and generate a NuGet package. Finally, you deploy that NuGet package to your Blazor server application.
 
 ## Add package properties to FirstClassLibrary
 
-Begin by updating the *FirstClassLibrary* project with properties that will allow it to be packaged for deployment as a NuGet package. 
+Begin by updating the *FirstClassLibrary* project with properties that allow it to be packaged for deployment as a NuGet package.
 
-1. Open the project file for the *MyClassLibrary* project either by double-clicking the project in Visual Studio Solution Explorer or by opening the *MyClassLibrary.csproj* file in Visual Studio Code.
+1. Open the project file for the *MyClassLibrary* project. Either double-click the project in Visual Studio Solution Explorer or open the *MyClassLibrary.csproj* file in Visual Studio Code.
 1. Near the top of the file, in the section with the `<PropertyGroup>` tag, add the following content before the closing `</PropertyGroup>` tag:
 
     ```xml
@@ -40,9 +40,9 @@ This command writes a file named *My.FirstClassLibrary.0.1.0.nupkg* to your *bin
 
 You already referenced the *FirstClassLibrary* project in your MyBlazorServer application, because it was in the same folder structure as the web application. 
 
-Now, you'll undo that project reference and add a reference to the NuGet package that you created earlier. 
+Now, you undo that project reference and add a reference to the NuGet package that you created earlier.
 
-These steps are *not* a typical configuration. Library projects that reside in the same folders or solution as the applications that want to reference them can reference the project directly, as you saw in the earlier exercise. 
+The following steps *don't* describe a typical configuration. Library projects that reside in the same folders or solution as the applications that want to reference them can reference the project directly, as you saw in the earlier exercise.
 
 1. Open the *MyBlazorServer.csproj* file either by double-clicking the *MyBlazorServer* project name in Visual Studio or by opening the file in Visual Studio Code.
 1. In the *MyBlazorServer.csproj* file, remove the following line:
@@ -59,7 +59,7 @@ These steps are *not* a typical configuration. Library projects that reside in t
 
 ## Check your work
 
-Did your new package install properly?  Can you start the FirstServer application and see a modal window when the application starts?
+Did your new package install properly? Can you start the FirstServer application and see a modal window when the application starts?
 
 Let's find out:
 
@@ -69,4 +69,4 @@ Let's find out:
 
 1. In your browser, go to the home page of the MyBlazorServer application: ``` https://localhost:5000 ```.
 
-   Is the **My first Modal dialog** dialog displayed?  If so, congratulations! You've successfully packaged and deployed the *FirstClassLibrary* project correctly. Applications everywhere can now use your modal window component by referencing your newly created NuGet package.
+   Is the **My first Modal dialog** dialog displayed? If so, congratulations! You successfully packaged and deployed the *FirstClassLibrary* project correctly. Applications everywhere can now use your modal window component by referencing your newly created NuGet package.

learn-pr/aspnetcore/blazor-build-reusable-components/includes/6-summary.md

@@ -1,13 +1,13 @@
-In this module, you faced and resolved a problem with building, packaging, and sharing Blazor components that can be used and reused across Blazor applications.
+In this module, you faced and resolved a problem with building, packaging, and sharing Blazor components for use and reuse across Blazor applications.
 
 You learned how to build a Razor class library that contains components to be shared with many applications. To assemble the library, you:
 
 - Created a new Razor class library from the .NET template.
-- Added a *.razor* file with a Blazor component and a *.razor.css* file that contains its style sheet.
+- Added a `.razor` file with a Blazor component and a `.razor.css` file that contains its style sheet.
 - Added package metadata to the project file, which defines the package for other developers.
 - Created a NuGet package from your Razor class library by using the .NET command-line interface.
 
-Blazor components are the building blocks that make it easier for you to build more complex applications. By building components and pages that reference other components, you can more quickly deliver applications that take advantage of the user-interface paradigms that other developers have shared with you. When you can depend on reusing earlier investments made by other developers, you can save time and money on your own projects as well.  
+Blazor components are the building blocks that make it easier for you to build more complex applications. By building components and pages that reference other components, you can more quickly deliver applications that take advantage of the user-interface paradigms that other developers share with you. When you can depend on reusing earlier investments made by other developers, you can save time and money on your own projects as well.  
 
 ## References
 

learn-pr/aspnetcore/blazor-build-reusable-components/index.yml

@@ -14,7 +14,7 @@ metadata:
 title: Build reusable components with Blazor
 summary: "By using Blazor components, you can reuse sections of HTML in your applications. Learn how to build a component, package it, and share it with other Blazor applications."
 abstract: |
-  By the end of this module, you'll be able to:
+  By the end of this module, you're able to:
     - Build a Razor class library that contains Blazor components.
     - Package a Razor class library for use in other Blazor applications.
     - Reference a Razor class library in a Blazor application and use its components.