Edit pass of SPFx > Extensions (SharePoint#1234)

* Edit in progress

Serving your extension...

* Fixed errors

* Replace Enter

Replaced bold Enter with plain Enter

* Final edit

* Final edit Extensions > Getting started

* Edit in progress -  Migrating extensions

* Final edit

* Edit in progress

* Final edit

* Edited customer instances

* Final tweaks

Author: Linda-Editor

docs/declarative-customization/site-design-pnp-provisioning.md

@@ -9,9 +9,9 @@ ms.date: 12/14/2017
 > [!NOTE]
 > Site designs and site scripts are currently in preview and are subject to change. They are not currently supported for use in production environments.
 
-Site designs offer a great way to standardize the look and feel of your site collections. You can't do some things with site designs, however, like add a footer to every page. You can use the PnP provisioning engine to create a template that you can use to provision an application customizer to a site. This application customizer can then update your page design, for example to register a footer on every page. 
+Site designs offer a great way to standardize the look and feel of your site collections. You can't do some things with site designs, however, like add a footer to every page. You can use the PnP provisioning engine to create a template that you can use to provision an Application Customizer to a site. This Application Customizer can then update your page design, for example to register a footer on every page. 
 
-This article describes how to create a site design that applies a PnP provisioning template to a site. The template will add an application customizer to render a footer.
+This article describes how to create a site design that applies a PnP provisioning template to a site. The template will add an Application Customizer to render a footer.
 
 The steps in this article use the following components:
 

docs/design/accessibility.md

@@ -84,7 +84,7 @@ Use the space bar to select or deselect the item currently in focus in a control
 
 ### Run a control
 
-Select **Enter** or the return key to run a control.
+Select Enter or the return key to run a control.
 
 *Figure 4. Selecting Enter to run a control*
 

docs/spfx/call-microsoft-graph-using-graphhttpclient.md

@@ -36,7 +36,7 @@ You can use the **get()** method to make a REST call to Microsoft Graph. This ex
   * Select **Web Part** as the type of client-side component to create.
   * Enter **HelloGraph** as your web part name.
   * Enter **Calls the Microsoft Graph Groups API** as the web part description.
-  * Accept the default **No javascript web framework** as the framework, and choose **Enter**.
+  * Accept the default **No javascript web framework** as the framework, and choose Enter.
 
   ![GraphHttpClient values to enter at command line](../images/graphhttpclient-web-part-create.jpg)
 

docs/spfx/extensions/basics/configure-extension-icon.md

@@ -1,32 +1,38 @@
 ---
-title: Configure extension icon
-ms.date: 11/20/2017
+title: Configure extension icon in SharePoint Framework (SPFx) Extensions
+description: Options for configuring the icon for your commands in SharePoint Framework (SPFx) Extensions.
+ms.date: 01/11/2018
 ms.prod: sharepoint
 ---
 
 # Configure extension icon
 
-Selecting an icon that illustrates the purpose of your custom command, makes it easier for users to find your command among other options visible in the toolbar or in the context menu. This article explains the different options available to you to configure the icon for your commands.
-
-## Extension types that support icons
+Selecting an icon that illustrates the purpose of your custom command in SharePoint Framework makes it easier for users to find your command among other options visible in the toolbar or in the context menu. Specifying an icon for a command is optional. If you don't specify an icon, only the command title is displayed in the command bar.
 
 SharePoint Framework supports building the following types of extensions:
 
-- Application customizer
-- Field customizer
-- Command set
+- Application Customizer
+- Field Customizer
+- Command Set
+
+The Command Set is the only type of SharePoint Framework Extension for which you can configure icons.
+
+When deploying Command Sets, you can choose whether their commands should be visible on:
 
-Command set is the only type of SharePoint Framework extension for which you can configure icons.
+- The command bar (`___location: ClientSideExtension.ListViewCommandSet.CommandBar`)
 
-## Defining Command set locations
+- The context menu (`___location: ClientSideExtension.ListViewCommandSet.ContextMenu`)
 
-When deploying command sets, you can choose whether their commands should be visible on the command bar (`___location: ClientSideExtension.ListViewCommandSet.CommandBar`), in the context menu (`___location: ClientSideExtension.ListViewCommandSet.ContextMenu`) or both (`___location: ClientSideExtension.ListViewCommandSet`). Icons defined for the different commands will be displayed only for commands displayed in the command bar.
+- Both (`___location: ClientSideExtension.ListViewCommandSet`)
 
-## Configuring command set icons
+Icons defined for the different commands are displayed only for commands displayed in the command bar.
 
-SharePoint Framework offers you two ways to define the icon for your extension.
+SharePoint Framework offers you two ways to define the icon for your extension:
 
-### Using an external icon image
+- Use an external icon image
+- Use a base64-encoded image
+
+## Use an external icon image
 
 When building SharePoint Framework command sets, you can specify an icon for each command by providing an absolute URL pointing to the icon image in the extension manifest, in the **iconImageUrl** property.
 
@@ -58,17 +64,21 @@ When building SharePoint Framework command sets, you can specify an icon for eac
 }
 ```
 
-The command icon displayed in the command bar is 16x16px. If your image is bigger, it will be sized proportionally to match these dimensions.
+<br/>
+
+The command icon displayed in the command bar is 16x16 px. If your image is bigger, it is sized proportionally to match these dimensions.
 
 ![Custom image used as the command icon in the command bar](../../../images/extensionicon_commandbar_imagepng.png)
 
-While using custom images gives you flexibility to choose an icon for your command, it requires you to deploy them along with your other extension assets. Additionally, your image might lose quality when displayed in higher DPI or specific accessibility settings. To avoid quality loss, you can use vector-based SVG images which are also supported by the SharePoint Framework.
+<br/>
 
-### Using a base64 encoded image
+While using custom images gives you flexibility to choose an icon for your command, it requires you to deploy them along with your other extension assets. Additionally, your image might lose quality when displayed in higher DPI or specific accessibility settings. To avoid quality loss, you can use vector-based SVG images, which are also supported by the SharePoint Framework.
 
-When using a custom image, rather than specifying an absolute URL to the image file hosted together with other extension assets, you can have your image base64 encoded and use the base64 string instead of the URL.
+## Use a base64-encoded image
 
-> There are a number of services available on the Internet that you can use to base64 encode your image, such as [https://www.base64-image.de](https://www.base64-image.de).
+When using a custom image, rather than specifying an absolute URL to the image file hosted together with other extension assets, you can have your image base64-encoded and use the base64 string instead of the URL.
+
+A number of services are available online that you can use to base64-encode your image, such as [Convert your images to Base64](https://www.base64-image.de).
 
 After encoding the image, copy the base64 string and use it as the value for the **iconImageUrl** property in the web part manifest.
 
@@ -100,10 +110,12 @@ After encoding the image, copy the base64 string and use it as the value for the
 }
 ```
 
-![Base64 encoded image displayed as web part icon in the toolbox](../../../images/extensionicon_commandbar_base64.png)
+<br/>
 
-Base64 encoding works both for bitmap images such as PNG as well as vector SVG images. The big benefit of using base64 encoded images is, that you don't need to deploy the web part icon image separately.
+Base64 encoding works for both bitmap images, such as PNG, as well as vector SVG images. The big benefit of using base64-encoded images is that you don't need to deploy the web part icon image separately.
+
+![Base64 encoded image displayed as web part icon in the toolbox](../../../images/extensionicon_commandbar_base64.png)
 
-## Additional considerations
+## See also
 
-Specifying an icon for a command is optional. If you don't specify an icon, then only the command title will be displayed in the command bar.
+- [Overview of SharePoint Framework Extensions](../overview-extensions.md)

docs/spfx/extensions/get-started/build-a-hello-world-extension.md

@@ -38,17 +38,17 @@ You can also follow the steps in this article by watching the video on the [Shar
 
 4. When prompted:
 
-    * Accept the default **app-extension** as your solution name, and select **Enter**.
-    * Select **SharePoint Online only (latest)**, and select **Enter**.
-    * Select **Use the current folder**, and select **Enter**.
+    * Accept the default **app-extension** as your solution name, and select Enter.
+    * Select **SharePoint Online only (latest)**, and select Enter.
+    * Select **Use the current folder**, and select Enter.
     * Select **N** to require the extension to be installed on each site explicitly when it's being used. 
     * Select **Extension** as the client-side component type to be created. 
     * Select **Application Customizer** as the extension type to be created.
 
 5. The next set of prompts ask for specific information about your extension. When prompted:
 
-    * Accept the default **HelloWorld** as your extension name, and select **Enter**.
-    * Accept the default **HelloWorld description** as your extension description, and select **Enter**.
+    * Accept the default **HelloWorld** as your extension name, and select Enter.
+    * Accept the default **HelloWorld description** as your extension description, and select Enter.
 
     <br/>