Small edits to api get-started

Author: Greg Van Liew

api/get-started/extension-anatomy.md

@@ -1,14 +1,14 @@
 ---
 ---
 
-# Extension Anatomy
+# Visual Studio Code Extension Anatomy
 
-In the last topic, we were able to get a basic extension running. How does it work under the hood?
+In the last topic, you were able to get a basic Visual Studio Code extension running. How does it work under the hood?
 
 The `Hello Code` extension does 3 things:
 
 - Registers the [`onCommand`](/api/references/activation-events#activationEvents.onCommand) [**Activation Event**](/api/references/activation-events): `onCommand:extension.helloCode`, so the extension becomes activated when user runs the `Hello Code` command.
-- Uses the [`contributes.commands`](/api/references/contribution-points#contributes.commands) [**Contribution Point**](/api/references/contribution-points) to make the command `Hello Code` available in the command palette, and bind it to a command ID `extension.helloCode`.
+- Uses the [`contributes.commands`](/api/references/contribution-points#contributes.commands) [**Contribution Point**](/api/references/contribution-points) to make the command `Hello Code` available in the Command Palette, and bind it to a command ID `extension.helloCode`.
 - Uses the [`commands.registerCommand`](/api/references/vscode-api#commands.registerCommand) [**VS Code API**](/api/references/vscode-api) to bind a function to the registered command ID `extension.helloCode`.
 
 Understanding these three concepts is crucial to writing VS Code Extensions:
@@ -36,11 +36,11 @@ Let's take a closer look of `Hello Code` sample's source code and see how these
 ├── tsconfig.json       // TypeScript configuration
 ```
 
-You can read more about the config files:
+You can read more about the configuration files:
 
-- `launch.json`: https://code.visualstudio.com/Docs/editor/debugging
-- `tasks.json`: https://code.visualstudio.com/Docs/editor/tasks
-- `tsconfig.json`: https://www.typescriptlang.org/docs/handbook/tsconfig-json.html
+- `launch.json` used to configure VS Code [Debugging](/docs/editor/debugging.md)
+- `tasks.json` for defining VS Code [Tasks](/docs/editor/tasks.md)
+- `tsconfig.json` consult the TypeScript [Handbook](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)
 
 However, let's focus on `package.json` and `extensions.ts`, which are essential to understanding the `Hello Code` extension.
 

api/get-started/your-first-extension.md

@@ -1,9 +1,9 @@
 ---
 ---
 
-# Your First Extension
+# Your First Visual Studio Code Extension
 
-In this section, we'll teach you fundamental concepts for building VS Code extensions. Make sure you have [Node.js](https://nodejs.org/en/) and [Git](https://git-scm.com/) installed, then install [Yeoman](http://yeoman.io/) and [VS Code Extension Generator](https://www.npmjs.com/package/generator-code) with:
+In this topic, we'll teach you the fundamental concepts for building Visual Studio Code extensions. Make sure you have [Node.js](https://nodejs.org/en/) and [Git](https://git-scm.com/) installed, then install [Yeoman](http://yeoman.io/) and [VS Code Extension Generator](https://www.npmjs.com/package/generator-code) with:
 
 ```bash
 npm install -g yo generator-code
@@ -25,13 +25,13 @@ yo code
 code ./hello-code
 ```
 
-Then, inside the editor, press F5, and run the `Hello Code` command in the new window:
+Then, inside the editor, press `kb(workbench.action.debug.start)`, and run the `Hello Code` command from the Command Palette (`kb(workbench.action.showCommands)`) in the new **Extension Development Host** window:
 
 <video autoplay loop muted playsinline controls>
   <source src="/api/get-started/your-first-extension/launch.mp4" type="video/mp4">
 </video>
 
-You should see the `Hello Code` information dialog showing up. Success!
+You should see the `Hello Code` notification showing up. Success!
 
 ## Developing the extension
 
@@ -49,8 +49,8 @@ You should see the updated message showing up.
 
 Here are some ideas for you to try:
 
-- Give `Hello Code` command a new name.
-- [Contribute](/api/references/contribution-points) another command `Goodbye Code`
+- Give the `Hello Code` command a new name.
+- [Contribute](/api/references/contribution-points) another command such as `Goodbye Code`
 - Replace the `vscode.window.showInformationMessage` with another [VS Code API](/api/references/vscode-api) call to show a warning message.
 
 ## Debugging the extension
@@ -61,7 +61,7 @@ The debugger and debug console allow you stop the program and inspect variables
   <source src="/api/get-started/your-first-extension/debug.mp4" type="video/mp4">
 </video>
 
-You can learn more about debugging Node apps in VS Code at the [Node.js Debugging Topic](/docs/nodejs/nodejs-debugging).
+You can learn more about debugging Node.js apps in VS Code at the [Node.js Debugging Topic](/docs/nodejs/nodejs-debugging).
 
 ## Next Steps
 
@@ -71,4 +71,4 @@ You can find the source code of this tutorial at: https://github.com/Microsoft/v
 
 ### Using JavaScript
 
-In this guide, we mainly describe how to develop VS Code extension with TypeScript because we believe TypeScript offers the best experience for developing VS Code extension. However, if you prefer JavaScript, you can still follow along using [hellocode-minimal-sample](https://github.com/Microsoft/vscode-extension-samples/tree/master/hellocode-minimal-sample).
+In this guide, we mainly describe how to develop VS Code extension with TypeScript because we believe TypeScript offers the best experience for developing VS Code extensions. However, if you prefer JavaScript, you can still follow along using [hellocode-minimal-sample](https://github.com/Microsoft/vscode-extension-samples/tree/master/hellocode-minimal-sample).