Merge pull request #51345 from chatasweetie/winui-101-review-new

 Updates based on @AnnaMHuff review

Author: JamesJBarnett

learn-pr/windows/winui-101/includes/11-summary.md

@@ -1,14 +1,14 @@
 You completed this module and build a strong foundation for Windows development skills.
 
-Here's what you achieve in this module:
+Here's what you achieved in this module:
 
 - You understand the role of the Windows App SDK and WinUI in creating modern and high-performance Windows applications.
 - You set up the development environment by enabling Developer Mode and installing Visual Studio.
-- You create a WinUI project, update essential packages, and organize the project by following best practices.
-- You use XAML for UI design and learn about the purpose of code-behind files.
+- You created a WinUI project, update essential packages, and organize the project by following best practices.
+- You used XAML for UI design and learned about the purpose of code-behind files.
 - You implemented two ways of binding data (`{x:Bind}` and `{Binding}`).
 - You understand how to use resource dictionaries for styling.
-- You can dynamically add data or update images to the View.
+- You added dynamically add data or updated images to the View.
 - You set up navigation in your future apps.
 
 These skills help you as you continue to develop Windows applications. Keep practicing and exploring new features. The world of Windows development offers many opportunities, and you're ready to learn more

learn-pr/windows/winui-101/includes/2-dev-set-up.md

@@ -7,7 +7,7 @@ Windows has a special mode for developers that adjusts security settings to let
 To enable Developer Mode:
 
 1. Open Windows Settings and navigate to the **System** > **For developers** page.
-2. Toggle the Developer Mode switch to **On** and confirm your choice in the confirmation dialog.
+1. Toggle the Developer Mode switch to **On** and confirm your choice in the confirmation dialog.
 
 ## Install Visual Studio
 
@@ -16,16 +16,16 @@ You use [Visual Studio](https://github.com/MicrosoftDocs/windows-dev-docs/blob/d
 > [!NOTE]
 > Before installing these tools, ensure your development computer meets the [system requirements for Windows app development](https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/apps/windows-app-sdk/system-requirements.md).
 
-3. Go to the Visual Studio page to download and install the latest Visual Studio. You can use the free Visual Studio Community Edition.
+1. Go to the Visual Studio page to download and install the latest Visual Studio. You can use the free Visual Studio Community Edition.
 
-> [!NOTE]
-> The installer guides you through the steps, but if you need detailed instructions, see [Install Visual Studio](https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/visualstudio/install/install-visual-studio).
+    > [!NOTE]
+    > The installer guides you through the steps, but if you need detailed instructions, see [Install Visual Studio](https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/visualstudio/install/install-visual-studio).
 
-While installing Visual Studio, you need to install the workloads and components required for developing with WinUI and the Windows App SDK.
+    While installing Visual Studio, you need to install the workloads and components required for developing with WinUI and the Windows App SDK.
 
-4. Open the Visual Studio Installer app
-5. Select **Modify** to add workloads and components.
-6. On the **Workloads** tab of the Visual Studio Installer app, select the following workloads and components:
+1. Open the Visual Studio Installer app
+1. Select **Modify** to add workloads and components.
+1. On the **Workloads** tab of the Visual Studio Installer app, select the following workloads and components:
 
     - [Visual Studio 2022 version 17.10 and later](https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/apps/get-started/start-here.md#tab/vs-2022-17-10)
 
@@ -41,15 +41,15 @@ While installing Visual Studio, you need to install the workloads and components
 
 To create a new project using the WinUI C# Blank App project template:
 
-7. Open Visual Studio and select **Create a new project** from the launch page. (If Visual Studio is already open to the editor, select **File** > **New**> **Project**)
-8. Search for **WinUI** and select the **Blank App, Packaged (WinUI 3 in Desktop)** project template
-9. Click **Next**
-10. Name your project: **SnowPal**
+1. Open Visual Studio and select **Create a new project** from the launch page. (If Visual Studio is already open to the editor, select **File** > **New**> **Project**)
+1. Search for **WinUI** and select the **Blank App, Packaged (WinUI 3 in Desktop)** project template
+1. Click **Next**
+1. Name your project: **SnowPal**
 
-> [!IMPORTANT]
-> The Project Name and Solution Name must be SnowPal. Visual Studio creates namespaces using this information. If it's something different, the code you copy and paste from this tutorial can cause build errors.
+    > [!IMPORTANT]
+    > The Project Name and Solution Name must be SnowPal. Visual Studio creates namespaces using this information. If it's something different, the code you copy and paste from this tutorial can cause build errors.
 
-11. Select **Create**.
+1. Select **Create**.
 
 ## Update & Install Packages
 
@@ -60,25 +60,25 @@ The Windows App SDK (including WinUI) and tools like the Community Toolkit are d
 
 To update the Windows App SDK NuGet package for your project:
 
-12. In Visual Studio, with your project loaded, select **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution....**
+1. In Visual Studio, with your project loaded, select **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution....**
 
-> [!IMPORTANT]
-> Projects must not be running in order to access the "Manage Nuget packages" option in the drop-down
+    > [!IMPORTANT]
+    > Projects must not be running in order to access the "Manage Nuget packages" option in the drop-down
 
-:::image type="content" source="../media/2-dev-set-up/package-source.png" alt-text="Screenshot of Visual Studio.":::
+    :::image type="content" source="../media/2-dev-set-up/package-source.png" alt-text="Screenshot of Visual Studio.":::
 
-13. Confirm that it's set to `nuget.org`
+1. Confirm that it's set to `nuget.org`
     - if it isn't, follow [these](/nuget/consume-packages/install-use-packages-visual-studio#package-sources) instructions.
-14. Click on the **Installed** tab.
-15. Click on **Microsoft.WindowsAppSDK**
-16. Select the **Checkbox** to Include prelease
-17. On the right panel:
+1. Click on the **Installed** tab.
+1. Click on **Microsoft.WindowsAppSDK**
+1. Select the **Checkbox** to Include prelease
+1. On the right panel:
     1. select the **checkbox** of the **Project**
-    1. Select from the dropdown  **1.7.250401001** 
+    1. Select from the dropdown  **1.7.250401001**
     1. Click **install**
         1. On the Preview Changes Popup, **Click Apply**.
         1. On the License Acceptance Popup, **Click I Accept**.
-18. To install the CommunityToolkit NuGet package for your project:
+1. To install the CommunityToolkit NuGet package for your project:
     1. Still in the Manage NuGet Packages for Solution, Click on the **Browse** tab.
     1. Enter **`CommunityToolkit.Mvvm`** in the search bar
     1. **Click to select** `CommunityToolkit.Mvvm`
@@ -88,22 +88,22 @@ To update the Windows App SDK NuGet package for your project:
         1. Click **Install**.
             1. On the Preview Changes Popup, **Click Apply**.
             1. On the License Acceptance Popup, **Click I Accept**.
-19. **Close** the  NuGet Package Manager
+1. **Close** the  NuGet Package Manager
 
-The Community Toolkit.Mvvm uses features that are ahead of the standard C# language version that your project is configured to use by default. You need to update the project's configuration:
+    The Community Toolkit.Mvvm uses features that are ahead of the standard C# language version that your project is configured to use by default. You need to update the project's configuration:
 
-20. If Solution Explorer isn't already open, you can open it by selecting **View** > **Solution Explorer** from the top menu.
-21. In the Solution Explorer, you see a tree structure representing your solution and its projects. Look for the project node named **SnowPal**. This node is usually a folder icon with the project name next to it.
-22. **Right-click** on the project node (**SnowPal**) and select **Edit Project File**. This action opens the .csproj file in the editor.
+1. If Solution Explorer isn't already open, you can open it by selecting **View** > **Solution Explorer** from the top menu.
+1. In the Solution Explorer, you see a tree structure representing your solution and its projects. Look for the project node named **SnowPal**. This node is usually a folder icon with the project name next to it.
+1. **Right-click** on the project node (**SnowPal**) and select **Edit Project File**. This action opens the .csproj file in the editor.
 
-:::image type="content" source="../media/2-dev-set-up/edit-project-file.png" alt-text="Screenshot of Edit Project.":::
+    :::image type="content" source="../media/2-dev-set-up/edit-project-file.png" alt-text="Screenshot of Edit Project.":::
 
-23. **Locate** the first `PropertyGroup` element in the file
-24. **Add** `<LangVersion>preview</LangVersion>`
+1. **Locate** the first `PropertyGroup` element in the file
+1. **Add** `<LangVersion>preview</LangVersion>`
 
-:::image type="content" source="../media/2-dev-set-up/language-version.png" alt-text="Screenshot of file with added LangVersion element.":::
+    :::image type="content" source="../media/2-dev-set-up/language-version.png" alt-text="Screenshot of file with added LangVersion element.":::
 
-25. **Save and Close** the file
+1. **Save and Close** the file
 
 Adding Preview is a way to unlock experimental language features required by advanced tools like Community Toolkit.Mvvm, enabling developers to use cutting-edge capabilities in their projects.
 
@@ -113,11 +113,11 @@ Now your project is using the latest WinUI features that are available.
 
 You can run this blank project:
 
-26. On the title bar, **Click** on **Debug** > **Start Debugging** OR on your keyboard press **F5** key
+1. On the title bar, **Click** on **Debug** > **Start Debugging** OR on your keyboard press **F5** key
 
-:::image type="content" source="../media/2-dev-set-up/start-debug.png" alt-text="Screenshot of visual studio's Debug.":::
+    :::image type="content" source="../media/2-dev-set-up/start-debug.png" alt-text="Screenshot of visual studio's Debug.":::
 
-27. To stop debugging, **Close** the app window, or **Click** the debug "Stop" button in Visual Studio.
+1. To stop debugging, **Close** the app window, or **Click** the debug "Stop" button in Visual Studio.
 
 ## The project's file structure
 
@@ -136,13 +136,13 @@ To improve maintainability, you create two new folders for organizing your proje
 
 ### Steps to Create Folders
 
-28. In Solution Explorer, **right-click** on your project.
-29. Select **Add** > **New Folder**.
+1. In Solution Explorer, **right-click** on your project.
+1. Select **Add** > **New Folder**.
 
-:::image type="content" source="../media/2-dev-set-up/add-new-folder.png" alt-text="Screenshot of visual studio's add new folder.":::
+    :::image type="content" source="../media/2-dev-set-up/add-new-folder.png" alt-text="Screenshot of visual studio's add new folder.":::
 
-30. Name the new folder `Models`.
-31. Repeat steps 1–3 and name the second folder `Pages`.
+1. Name the new folder `Models`.
+1. Repeat steps 1–3 and name the second folder `Pages`.
 
 ### Why Name It "Pages" Instead of "Views"?