Merge pull request #1 from Linda-Editor/patch-4

Edit pass complete

docs/design/web-part-commanding.md

@@ -1,34 +1,38 @@
 ---
-title: Commanding and See all
+title: Commanding within a web part
 ms.date: 4/16/2018 
 ---
 
 # Commanding within a web part
 
-The commanding with in a web part consists of a single line of commands which sit below the web part title. These commands contain and icon and text, for example the <b>+ plus</b> icon and the text <b>Add</b>. The command bar can be extended to support multiple commands but be aware of overloading the web part with too many commands and how they reflow when the web part is placed in different columns or when the page reflows to smaller screen sizes.
+Commanding within a web part consists of a single line of commands that sits under the web part title. These commands contain an icon and text, for example the `+` (plus) icon and the text **Add**. The command bar can be extended to support multiple commands. However, be aware of overloading the web part with too many commands. Also, note how the commands reflow when the web part is placed in different columns, or when the page reflows to smaller screen sizes.
 
-![Single +Add command below the Title](../images/Commanding_Events_1column_01.png)
+![Single +Add command under the title](../images/Commanding_Events_1column_01.png)
 
-![Mulitple commands on the left and secondary commands on the right](../images/Commanding_Doclib_multiplecommands_05.png)
+<br/>
 
-# See all
+![Multiple commands on the left, and secondary commands on the right](../images/Commanding_Doclib_multiplecommands_05.png)
 
-Many web part may need to support the overflow of content to a secondary page such as the case with News and Events. As well, only specific layouts within the web part may need to support the overflow. The recommended pattern is to place a See all command on the far right corner. This command should be last in the tab order of the web part to support keyboard navigation.
+## See all
+
+Many web parts may need to support the overflow of content to a secondary page (for example, in News and Events web parts). In addition, only specific layouts within the web part may need to support the overflow. The recommended pattern is to place a **See all** command in the far-right corner. To support keyboard navigation, this command should be last in the tab order of the web part.
 
 ![Single +Add command with See All command](../images/Commanding_News_1column_02.png)
 
-# Command bar states
+## Command bar states
+
+A common command is **Add** for many web parts that require content to be created. In the case of News and Events, the **Add** command is only enabled in read mode because it takes the user to a new page or form to create content. The desired web part user experience should determine if commands are active in both read and edit modes, only edit, or only read. Most likely this is driven by whether the web part is designed to be configured by the author of the page and static to the viewer, or if the viewer/reader can interact with the web part.
 
-A common command is Add for many web part that require content to be created. In the case of News and Event the Add command is only enabled in read mode as it takes user to a new page or form to create content. The desired web part user experience should determine if commands are active in both read and edit modes, only edit, or only read. Most likely this will be driven by whether or not the web part is designed to be configured by the author of the page and static to the viewer or if the viewer/reader can interact with the web part.
+## Placement and accessibility of commands
 
-# Placement and accessibility of commands
+Core commands, even when the web part has only one command such as **Add**, should sit under the title to create consistency and discoverability, and to support easy reflow across all column sizes. Long web part titles should wrap to two lines, but not interfere with the placement of the commands.
 
-Core commands, even when the webpart has only 1 command such as Add, should sit below the Title to create consistancy, discoverability and support easy reflow across all column sizes. Long web part Titles should wrap to two lines but not interfere with the placement of the commands.
+![Two-column reflow and title wrap](../images/Commanding_Events_2column_03.png)
 
-![Two column reflow and title wrap](../images/Commanding_Events_2column_03.png)
+<br/>
 
-![Three column reflow and title wrap](../images/Commanding_Events_3column_04.png)
+![Three-column reflow and title wrap](../images/Commanding_Events_3column_04.png)
 
-Here is an example of a web part with a simple set of commands that follow the placement guidance. Follow the guide below when deciding how to make your web part accessible to suppot keyboard navigation and screen reader lables. [To learn more about accessibility!](https://docs.microsoft.com/en-us/sharepoint/dev/design/accessibility)
+Following is an example of a web part with a simple set of commands that follow the placement guidance. Follow this guide when deciding how to make your web part accessible to support keyboard navigation and screen reader labels. To learn more about accessibility, see [Accessibility in SharePoint web part design](accessibility.md).
 
 ![Commmand keyboarding example](../images/Commanding_News_tab_order_06.png)