updates based on @Jaylyn-Barbee review

Author: chatasweetie

hub/images/command-palette/command-result.png

@@ -59,7 +59,7 @@ public <ExtensionName>CommandsProvider()
 > The `ShowMessageCommand()` functionality was created prior at [InvokableCommand Command](adding-commands#invokableCommand-command)
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 ![Screenshot of extension with send message command at top level](../../images/command-palette/top-level-command.png)
 

hub/powertoys/command-palette/add-top-level-commands-to-your-extension.md

@@ -11,11 +11,11 @@ no-loc: [PowerToys, Windows, Insider]
 
 **Previous**: [Creating an extension](creating-an-extension.md). We'll be starting with the project created in that article.
 
-Now that you've created your extension, it's time to add some commands to it.
+Now that you've created your extension, it's time to add commands to it.
 
-## Add some commands
+## Add commands
 
-We can start by navigating to the `<ExtensionName>Page.cs` file. This file is the [ListPage](./microsoft-commandpalette-extensions-toolkit/listpage.md) that will be displayed when the user selects your extension. In there you should see:
+We can start by navigating to the `/Pages/<ExtensionName>Page.cs` file. This file is the [ListPage](./microsoft-commandpalette-extensions-toolkit/listpage.md) that will be displayed when the user selects your extension. In there you should see:
 
 ```csharp
 public <ExtensionName>Page()
@@ -32,7 +32,7 @@ public override IListItem[] GetItems()
 }
 ```
 
-Here you can see that we've set the icon for the page, the title, and the name that's shown at the top-level when you have the command selected. The `GetItems` method is where you'll return the list of commands that you want to show on this page. Right now, that's just returning a single command that does nothing. Let's instead try making that command open _this_ page in the user's default web browser.
+Here you can see that we've set the icon for the page, the title, and the name that's shown at the top-level when you have the command selected. The `GetItems` method is where you'll return the list of commands that you want to show on this page. Right now, it's just returning a single command that does nothing. Let's instead try making that command open _this_ page in the user's default web browser.
 
 1. Update `GetItems` to the following:
 
@@ -87,8 +87,8 @@ As your building your extension, you'll most likely want to debug it.
     }
 ```
 
-1. Deploy your extension, wait until it's successful
-1. Confirm You're in Debug Configuration
+1. Deploy your extension
+1. Confirm you're in Debug configuration
 
 <details>
   <summary>Instructions to confirm debug configuration</summary>
@@ -114,7 +114,7 @@ As your building your extension, you'll most likely want to debug it.
 
 Let's continue building a new command, that shows a **MessageBox**. To do that, we need to create a new class that implements `InvokableCommand`.
 
-1. In Visual Studio, Add a New Class File
+1. In Visual Studio, Add a New Class File to your `Pages` directory
     - Keyboard Shortcut: Press Ctrl + Shift + A
     - Or in the Solution Explorer, go to Project > Add New Item...
 1. In the Add New Item dialog:
@@ -166,18 +166,18 @@ public override IListItem[] GetItems()
 ```
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 And presto - a command to show a message box!
 
 > [!TIP]
 > At about this point, you'll probably want to initialize a git repo / {other source control method of your choice} for your project. This will make it easier to track changes, and to share your extension with others.
 > 
-> We recommend using GitHub, as it's easy to collaborate on your extension with others, and get feedback, and share it with the world.
+> We recommend using GitHub, as it's easy to collaborate on your extension with others, get feedback, and share it with the world.
 
 ## Types of Pages
 
-So far, we've only worked with commands that "do something". However, you can also add commands that show additional pages within the Command Palette. There are basically two types of "Commands" in the Palette:
+So far, we've only worked with commands that "do something". However, you can also add commands that show additional pages within the Command Palette. There are two types of "Commands" in the Palette:
 
 - `InvokableCommand` - These are commands that **do something**
 - `IPage` - These are commands that **show something**
@@ -249,10 +249,10 @@ internal sealed partial class MySecondPage : ListPage
 +           new ListItem(new MySecondPage()) { Title = "My second page", Subtitle = "A second page of commands" },
         ];
     }
-```
+```f
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 You should now see a new page in your extension that shows 100 commands that copy a number to the clipboard.
 

hub/powertoys/command-palette/adding-commands.md

@@ -63,7 +63,10 @@ This is useful for commands that might have destructive actions, or that need to
 
 ## Example
 
-Below is a page with one command for each kind of command result:
+Below is a page with one command for each kind of `CommandResult`:
+
+1. Open `/Pages/<ExtensionName>Page.cs`
+1. Replace `GetItems` with the `GetItems` below:
 
 ```csharp
 
@@ -72,7 +75,7 @@ using Microsoft.CommandPalette.Extensions.Toolkit;
 
 internal sealed partial class <ExtensionName>Page : ListPage
 {
-    public CommandResultsPage()
+    public <ExtensionName>Page()
     {
         Icon = IconHelpers.FromRelativePath("Assets\\StoreLogo.png");
         Title = "Example command results";
@@ -111,6 +114,11 @@ internal sealed partial class <ExtensionName>Page : ListPage
 }
 ```
 
+1. Deploy your extension
+1. In Command Palette, `Reload`
+
+![Screenshot of extension with several commands for CommandResult](../../images/command-palette/command-result.png)
+
 ### Next up: [Display markdown content](using-markdown-content.md)
 
 ## Related content

hub/powertoys/command-palette/command-results.md

@@ -62,7 +62,7 @@ You can deploy and run your extension:
   <summary>How to Deploy your extension</summary>
 
 1. In the navigation bar, click on `Build`
-1. Click on `Deploy <ExtensionName>`
+1. Click on `Deploy \<ExtensionName\>`
 
 </details>
 
@@ -81,17 +81,20 @@ Once your package is deployed and running, Command Palette will automatically di
 > ```
 > These files are used by WinAppSdk to deploy your app as a package. Without it, anyone who clones your repo won't be able to deploy your extension.
 
-1. In the Command Palette, scroll down the list of commands
-1. Press `Enter` on your <ExtensionName>
+1. In the Command Palette, type `Reload` and press `Enter`
+    1. Make sure to select the `Reload` that has a subtitle of: `Reload Command Palette Extension`
+    ![Screenshot of reload](../../images/command-palette/reload.png)
+1. In the Command Palette, scroll all the way down to the bottom of the list of commands
+    1. or `up arrow` once to get to the end
+1. Press `Enter` on your \<ExtensionName\>
 1. You should see a single command that says `TODO: Implement your extension here`.
 
 ![A screenshot of the empty extension template, running in the command palette](../../images/command-palette/initial-created-extension-list.png)
 
 Congrats! You've made your first extension! Now let's go ahead and actually add some commands to it.
 
-When you make changes to your extension, you can rebuild your project and deploy it again. Command Palette will **not** notice changes to packages that are re-ran through Visual Studio, so you'll need to manually run the "**Reload**" command to force Command Palette to re-instantiate your extension.
-
-![Screenshot of reload](../../images/command-palette/reload.png)
+> [!TIP]
+> When you make changes to your extension, you can rebuild your project and deploy it again. Command Palette will **not** notice changes to packages that are re-ran through Visual Studio, so you'll need to manually run the "**Reload**" command to force Command Palette to re-instantiate your extension.
 
 ### Next up: [Add commands to your extension](adding-commands.md)
 

hub/powertoys/command-palette/creating-an-extension.md

@@ -47,7 +47,7 @@ Here, we're using ``AnonymousCommand`` to create a command that will update the
 
 ## Updating Subtitle of Page
 
-You can of course create custom **ListItem** objects too:
+You can create custom **ListItem** objects too:
 
 1. In the `Pages` folder, create a new class called `IncrementingListItem`
 1. Update the code to:
@@ -107,6 +107,8 @@ To do this, you can use the `RaiseItemsChanged` method on the `ListPage` object.
 1. Update the code to:
 
 ```csharp
+using <ExtensionName>
+
 internal sealed partial class IncrementingListItem : ListItem
 {
     public IncrementingListItem(<ExtensionName>Page page) :
@@ -121,7 +123,7 @@ internal sealed partial class IncrementingListItem : ListItem
 }
 ```
 
-1. In `<ExtensionName>Page.cs`, replace code with:
+1. In `<ExtensionName>Page.cs`, replace code inside of the class:
 
 ```cs
 public <ExtensionName>Page()
@@ -145,7 +147,7 @@ private List<ListItem> _items;
 ```
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 Now, every time you perform one of the `IncrementingListItem` commands, the list of items on the page will update to add another item. We're using a single **List** owned by the page to own all the items. Notably, we're creating the new items in the `Increment` method, before calling `RaiseItemsChanged`. The **Invoke** of a **InvokableCommand** can take as long as you'd like. All your code is running in a separate process from the Command Palette, so you won't block the UI. But constructing the items before calling `RaiseItemsChanged` will help keep your extension *feeling* more responsive.
 
@@ -159,6 +161,10 @@ Everything so far has been pretty instantaneous. Many extensions however may nee
 1. In your `<ExtensionName>Page.cs`, replace the `Increment()`.
 
 ```csharp
+using System.Threading;
+
+...
+
 internal void Increment()
 {
     this.IsLoading = true;
@@ -173,7 +179,7 @@ internal void Increment()
 ```
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 Best practice is to set `IsLoading` to `true` before starting the work. Then do all the work to build all the new `ListItems` you need to display to the user. Then, once the items are ready, call `RaiseItemsChanged` and set `IsLoading` back to `false`. This will ensure that the loading spinner is shown for the entire duration of the work, and that the UI is updated as soon as the work is done (without waiting for your extension to construct new `ListItem` objects).
 

hub/powertoys/command-palette/update-a-list-of-commands.md

@@ -11,7 +11,7 @@ no-loc: [PowerToys, Windows, Insider]
 
 **Previous**: [Display markdown content](using-markdown-content.md)
 
-Now that we know how to present basic markdown content, let's try displaying something more elaborate by leveraging the power of **[Adaptive Cards](https://adaptivecards.io/)**. This is useful for creating forms, or for displaying more complex content.
+Now that we know how to present basic markdown content, let's try displaying something more meaningful by leveraging the power of **[Adaptive Cards](https://adaptivecards.io/)**. This is useful for creating forms, or for displaying more complex content.
 
 ## Working with forms
 
@@ -109,6 +109,9 @@ internal sealed partial class SampleContentForm : FormContent
                 Name = "Confirm",
                  Result = CommandResult.KeepOpen(),
             },
+            Title = "You can set a title for the dialog",
+            Description = "Are you really sure you want to do the thing?",
+        };
         return CommandResult.Confirm(confirmArgs);
     }
 }
@@ -131,7 +134,7 @@ public <ExtensionName>CommandsProvider()
 ```
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 ![Screenshot of extension using ContentPage for simple form](../../images/command-palette/form-simple.png)
 
@@ -256,7 +259,7 @@ To add this content to your extension:
 ```
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 ![Screenshot of extension using ContentPage for simple form](../../images/command-palette/form-toggle-comdpal.png)
 

hub/powertoys/command-palette/using-form-pages.md

@@ -59,7 +59,7 @@ public <ExtensionName>CommandsProvider()
 ```
 
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 
 In this example, a new `ContentPage` that displays a simple markdown string is created. The 'MarkdownContent' class takes a string of markdown content and renders it in the Command Palette.
 
@@ -103,7 +103,7 @@ public class <ExtensionName>Page : ContentPage
         path = 
 
 +       Commands = [
-+           new CommandContextItem(new OpenUrlCommand("C:\\Path\\to\\file.txt")) { Title = "Open in File Explorer" },
++           new CommandContextItem(new OpenUrlCommand(doc_path)) { Title = "Open in File Explorer" },
 +       ];
     }
     public override IContent[] GetContent()
@@ -119,13 +119,12 @@ public class <ExtensionName>Page : ContentPage
 
 1. Update the path in the `doc_path` to a .txt file on your local machine
 1. Deploy your extension
-1. In command palette, `Reload`
+1. In Command Palette, `Reload`
 1. Select <ExtensionName>
 1. Press `Enter` key, the docs should open
 
 ![Screenshot of extension using CommandContextItem](../../images/command-palette/CommandContextItem.png)
 
-
 ### Next up: [Get user input with forms](using-form-pages.md)
 
 ## Related content