changes based on @v-regandowner review

Author: chatasweetie

learn-pr/windows/winui-101/11-summary.yml

@@ -3,7 +3,7 @@ uid: learn.winui-101.summary
 title: Summary
 metadata:
   title: Summary
-  description: "TODO this field is for search engine optimization and is not user-visible; use 2-3 complete, grammatically correct sentences to describe the unit; include relevant search keywords."
+  description: "Embark on your Windows development journey with this beginner-friendly course designed to get you up and running quickly. Learn how to set up a professional development environment using Visual Studio, understand the fundamentals of the WinUI3, Windows App SDK and CommunityToolkit, and grasp essential concepts of the MVVM architectural pattern. Through practical, hands-on experience building a simple word-guessing game, you'll gain the confidence and skills needed to start creating your own Windows applications. This course is perfect for aspiring Windows developers looking to build a solid foundation in modern development using cutting-edge tools and best practices."
   ms.date: 3/17/2025
   author: chatasweetie
   ms.author: jearleycha

learn-pr/windows/winui-101/includes/1-introduction.md

@@ -14,7 +14,7 @@ Throughout this course, we put these tools into practice by building SnowPal, a
 
 For this course, we’ll use three key terms -— **View**, **ViewModel**, and **Model** -— to represent distinct parts of our application architecture:
 
-:::image type="content" source="../media/1-introduction/mvvm-intro.png" alt-text="Highlevel Overview MVVM.":::
+:::image type="content" source="../media/1-introduction/mvvm-intro.png" alt-text="Diagram that shows Highlevel Overview MVVM.":::
 
 - The **View** term refers to the User Interface (UI) of the application. This View component displays data to users and handles user interactions.
 - The **ViewModel** term handles presentation logic and transforms data from the Model into a form that the View can easily display.
@@ -24,7 +24,7 @@ These three components form the Model-View-ViewModel (MVVM) software architectur
 
 The **ViewModel** component performs the databinding between View and Model components. This databinding enables automatic propagation of data changes in both directions. The ViewModel handles syncing raw Model data to reflect UI changes automatically. If the user makes a change, the View updates the ViewModel, which can then update the Model and notify the View.
 
-:::image type="content" source="../media/1-introduction/mvvm-bi-directional-syncing.png" alt-text="Demonstrates that the View, ViewModel, and Model sync bi-directionally.":::
+:::image type="content" source="../media/1-introduction/mvvm-bi-directional-syncing.png" alt-text="Diagram that demonstrates that the View, ViewModel, and Model sync bi-directionally.":::
 
 This bi-directional syncing between View and Model components allows us to have functionality that enables a user to press a letter button in our game. This button press triggers the ViewModel to both update the View (by disabling the button) and the Model (by processing the user's guessed letter).
 

learn-pr/windows/winui-101/includes/5-add-alphabet-buttons.md

@@ -250,4 +250,4 @@ The app should be playable with alphabet buttons.
 
 Great!
 
-You upgraded the game with a dynamic and interactive set of alphabet buttons. By utilizing a `GridView control` and binding it to your game data, you created a more responsive and efficient interface. This approach not only saves you time in development but also makes your game more adaptable to changes in the future. You learned how to use the `ObservableProperty` attribute to make your data observable, allowing the UI to update automatically when values change. Additionally, you implemented the ``RelayCommand` attribute to handle user interactions cleanly, without the need for traditional event handlers in the code-behind.
+You upgraded the game with a dynamic and interactive set of alphabet buttons. By utilizing a `GridView control` and binding it to your game data, you created a more responsive and efficient interface. This approach not only saves you time in development but also makes your game more adaptable to changes in the future. You learned how to use the `ObservableProperty` attribute to make your data observable, allowing the UI to update automatically when values change. Additionally, you implemented the `RelayCommand` attribute to handle user interactions cleanly, without the need for traditional event handlers in the code-behind.

learn-pr/windows/winui-101/includes/6-game-play.md

@@ -391,12 +391,12 @@ public partial string MessageContent { get; set; }
 public partial string PopUpToDisplay { get; set; }
 ```
 
-4. add to the top of `MainViewModel()`:
+4. Add to the top of `MainViewModel()`:
 ```csharp
 PopUpToDisplay = "false";
 ```
 
-5. Update `OnLetterGuessed` the to be:
+5. Update `OnLetterGuessed` to be:
 
 ```csharp
 [RelayCommand]

learn-pr/windows/winui-101/includes/7-style.md

@@ -71,7 +71,7 @@ Create the Resource Dictionary file called Styles:
 
 :::image type="content" source="../media/7-style/add-new-item.png" alt-text="Screenshot of Visual Studio adding a new item.":::
 
-4. In the **Add New Item** dialog, select **WinUI**in the template list on the left-side of the window.
+4. In the **Add New Item** dialog, select **WinUI** in the template list on the left-side of the window.
 
 5. Select the **Resource Dictionary (WinUI 3)**