pull base content,head:MicrosoftDocs:main,into:wwlpublishsync

Author: wwlpublish

learn-pr/aspnetcore/blazor-introduction/1-introduction.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: introduction
   title: Introduction
   description: "Introducing Blazor for web app development."
-  ms.date: 1/19/2024
+  ms.date: 11/01/2024
   author: danroth27
   ms.author: daroth
   ms.manager: markl

learn-pr/aspnetcore/blazor-introduction/2-what-is-blazor.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: learning-content
   title: What is Blazor?
   description: "Blazor is a modern frontend web framework based on HTML and C# that helps you build web apps faster."
-  ms.date: 1/19/2024
+  ms.date: 11/01/2024
   author: danroth27
   ms.author: daroth
   ms.manager: markl

learn-pr/aspnetcore/blazor-introduction/3-how-blazor-works.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: learning-content
   title: How Blazor works
   description: "Blazor supports full stack web UI development with components that can be rendered from the server or client via WebAssembly."
-  ms.date: 1/19/2024
+  ms.date: 11/01/2024
   author: danroth27
   ms.author: daroth
   ms.manager: markl

learn-pr/aspnetcore/blazor-introduction/4-when-to-use-blazor.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: learning-content
   title: When to use Blazor
   description: "Learn whether to use Blazor for your next web app project."
-  ms.date: 1/19/2024
+  ms.date: 11/01/2024
   author: danroth27
   ms.author: daroth
   ms.manager: markl

learn-pr/aspnetcore/blazor-introduction/5-knowledge-check.yml

@@ -4,7 +4,7 @@ title: Knowledge check
 metadata:
   title: Knowledge check
   description: Check your knowledge about what Blazor is and when you should use it to build your apps.
-  ms.date: 1/19/2024
+  ms.date: 11/01/2024
   author: danroth27
   ms.author: daroth
   ms.manager: markl
@@ -26,15 +26,15 @@ quiz:
           explanation: "Blazor is a modern frontend web framework based on HTML, CSS, and C#."
         - content: "A type of jacket resembling a suit jacket, but with a more casual cut."
           isCorrect: false
-          explanation: "That's a 'blazer'! Blazor is a modern frontend web framework based on HTML, CSS, and C#"
+          explanation: "Nope, that's a *blazer*! Blazor is a modern frontend web framework based on HTML, CSS, and C#"
     - content: "What language do you typically use to author Blazor components?"
       choices:
         - content: "JavaScript"
           isCorrect: false
           explanation: "You can use JavaScript from Blazor apps, but it's not the primary authoring language."
         - content: "XAML"
           isCorrect: false
-          explanation: "Blazor components are written in Razor, not XAML."
+          explanation: "Blazor components are written in Razor, not Extensible Application Markup Language (XAML)."
         - content: "Visual Basic"
           isCorrect: false
           explanation: "You can use Visual Basic in Blazor apps, but you don't typically author Blazor components with Visual Basic."
@@ -49,7 +49,7 @@ quiz:
         - content: "False"
           isCorrect: false
           explanation: "Blazor supports JavaScript interop, which lets you call JavaScript libraries and APIs from your Blazor apps."
-    - content: "Which of the following benefits is not a benefit of using Blazor?"
+    - content: "Which of the following benefits isn't a benefit of using Blazor?"
       choices:
         - content: "Build web UI fast with reusable components."
           isCorrect: false
@@ -59,15 +59,15 @@ quiz:
           explanation: "The ability to render Blazor components both from the server and the client enables building various web app architectures and optimizing the user experience."
         - content: "Build the frontend and backend with one development stack."
           isCorrect: false
-          explanation: "Building both the frontend and backend with .NET uses a common skillset, enables code sharing, and reduces complexity."
+          explanation: "Building both the frontend and backend with .NET uses a common skill set, enables code sharing, and reduces complexity."
         - content: "Minimal download size."
           isCorrect: true
           explanation: "While server-based Blazor apps can load quickly, running .NET code on the client requires downloading a small .NET runtime with the app."
-    - content: "Which of the following reasons is valid reason to not use Blazor?"
+    - content: "Which of the following reasons is a valid reason to not use Blazor?"
       choices:
         - content: "You need to use an existing React component in your web app."
           isCorrect: false
-          explanation: "You can typically use components from other frontend frameworks in Blazor as HTML custom elements. However, if you need to use many components from other frameworks, then Blazor may not be the best choice."
+          explanation: "You can typically use components from other frontend frameworks in Blazor as HTML custom elements. However, if you need to use many components from other frameworks, then Blazor might not be the best choice."
         - content: "You need to host your web app on a cheap static site host, like GitHub Pages."
           isCorrect: false
           explanation: "Blazor apps can be configured to run fully on the client via WebAssembly and can be deployed as static sites."
@@ -76,4 +76,4 @@ quiz:
           explanation: "Learning C# is worth the investment! With C# in your developer toolbelt you can use .NET to build virtually any type of app, including web apps, native mobile & desktop apps, games, and much more!"
         - content: "You need to support older browsers."
           isCorrect: true
-          explanation: "Blazor supports all modern browsers, but if you need to support older browsers that don't support modern web platform features, then Blazor may not be the best choice."
+          explanation: "Blazor supports all modern browsers, but if you need to support older browsers that don't support modern web platform features, then Blazor might not be the best choice."

learn-pr/aspnetcore/blazor-introduction/6-summary.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: summary
   title: Summary
   description: "Blazor is a user interface framework for .NET developers that can be used to build applications with Razor and C#. Applications run on the server with ASP.NET Core or in the browser with WebAssembly."
-  ms.date: 01/12/2024
+  ms.date: 11/01/2024
   author: csharpfritz
   ms.author: jefritz
   ms.manager: markl

learn-pr/aspnetcore/blazor-introduction/includes/2-what-is-blazor.md

@@ -1,4 +1,4 @@
-Blazor is a modern frontend web framework based on HTML, CSS, and C# that helps you build web apps faster. With Blazor you build web apps using reusable components that can be run from both the client and the server so that you can deliver great web experiences. Blazor is part of .NET, a developer platform for building *anything*. .NET is free, open-source, and runs cross-platform.
+Blazor is a modern frontend web framework based on HTML, CSS, and C# that helps you build web apps faster. With Blazor, you build web apps using reusable components that can be run from both the client and the server so that you can deliver great web experiences. Blazor is part of .NET, a developer platform for building *anything*. .NET is free, open-source, and runs cross-platform.
 
 Some of the benefits of using Blazor include:
 
@@ -9,6 +9,6 @@ Some of the benefits of using Blazor include:
 - **Server and client-side rendering:** Render components from both the server and the client to implement various web app architectures and deliver the best possible web app experience.
 - **Progressively enhanced server rendering**: Use built-in support for enhanced navigation & form handling and streaming rendering to progressively enhance the user experience of server rendered web apps.
 - **Interop with JavaScript:** Use the ecosystem of JavaScript libraries and browser APIs from your C# code.
-- **Integrate with existing apps:** Integrate Blazor components with existing MVC, Razor Pages, or JavaScript based apps.
+- **Integrate with existing apps:** Integrate Blazor components with an existing MVC, Razor Pages, or JavaScript based apps.
 - **Great tooling**: Use Visual Studio or Visual Studio Code to get started in seconds and stay productive with great code editing support.
 - **Web, mobile, and desktop**: Blazor components can also be used to build native mobile & desktop apps using a hybrid of native and web, called Blazor Hybrid.

learn-pr/aspnetcore/blazor-introduction/includes/3-how-blazor-works.md

@@ -12,7 +12,7 @@ You author Blazor components using Razor syntax, a convenient mixture of HTML, C
 
 Interactive Blazor components can handle standard web UI interactions using C# event handlers. Components can update their state in response to UI events and adjust their rendering accordingly. Blazor also includes support for two-way data binding to UI elements as a way to keep component state in sync with UI elements.
 
-Below is an example of a simple Blazor counter component implemented in Razor. Most of the content is HTML, while the `@code` block contains C#. Every time the button is pressed the `IncrementCount` C# method is invoked, which increments the `currentCount` field, and then the component renders the updated value:
+The following example is a simple Blazor counter component implemented in Razor. Most of the content is HTML, while the `@code` block contains C#. Every time the button is pressed the `IncrementCount` C# method is invoked, which increments the `currentCount` field, and then the component renders the updated value:
 
 ```razor
 <h1>Counter</h1>
@@ -43,7 +43,7 @@ Alternatively, Blazor components can be rendered interactively from the client.
 
 ![Diagram of Blazor interactive WebAssembly rendering.](../media/interactive-wasm.png)
 
-You can choose to render different components from the server or the client within the same app. Many of the pages in your app might not require any interactivity at all, and can be rendered statically from the server, while other more interactive parts of your app can be handled from the server or client. You can decide which component render mode to use at design time or runtime. With Blazor, you have the flexibility to build the web app architecture that's right for your scenario.
+You can choose to render different components from the server or the client within the same app. Many of the pages in your app might not require any interactivity at all, and can be rendered statically from the server. While other more interactive parts of your app can be handled from the server or client. You can decide which component render mode to use at design time or runtime. With Blazor, you have the flexibility to build the web app architecture that's right for your scenario.
 
 ## Using Blazor to build a pizza shop
 

learn-pr/aspnetcore/blazor-introduction/includes/4-when-to-use-blazor.md

@@ -7,7 +7,7 @@ You should consider using Blazor for web development if:
 - You're already using .NET, and you want to apply your existing .NET skills and resources on the web.
 - You need a high-performance and highly scalable backend to power your web app.
 
-Blazor may not be a good fit if:
+Blazor might not be a good fit if:
 
 - You need to fully optimize download size and load time of client-side assets.
 - You need to integrate heavily with a different frontend framework ecosystem.

learn-pr/aspnetcore/blazor-introduction/includes/6-summary.md

@@ -2,7 +2,7 @@ In this module, you learned that Blazor is a modern full stack web UI framework
 
 Are you ready to build your first Blazor web app? Continue on to the next module to get started.
 
-Also, check out the following additional resources to learn more about Blazor.
+Also, check out the following resources to learn more about Blazor.
 
 ## References