Fix indents

Author: gewarren

docs/extensibility/ux-guidelines/ux-essentials-for-visual-studio.md

@@ -10,6 +10,7 @@ ms.workload:
   - "vssdk"
 ---
 # UX Essentials for Visual Studio
+
 ## Best practices
 
 ### 1. Be consistent within the Visual Studio environment.
@@ -79,7 +80,8 @@ ms.workload:
  ![Placing UI in an error state by default is a Visual Studio anti-pattern.](../../extensibility/ux-guidelines/media/manifestdesignererrordeclarationsanti-pattern.png "ManifestDesignererrordeclarationsanti-pattern")<br />Placing UI in an error state by default is a Visual Studio anti-pattern.
 
 #### Alternatives
- A much better solution to this problem would be to:
+
+A better solution to this problem is to:
 
 - Allow the user to add a declaration without warning and then move immediately to set properties on the item.
 
@@ -95,42 +97,41 @@ ms.workload:
 #### Anti-pattern
  The team inserting the video links into various places within the VS UI decided against the common pattern of the "&times;" close button and tooltip explanation as specified by UX, and instead implemented a drop-down and "Don't show again" link.
 
-#### Example: video links in Team Explorer
+#### Example: Video links in Team Explorer
 Forcing the user to read explanatory text before dismissing UI is an anti-pattern within Visual Studio. Correctly designed, video links should display a tooltip with additional information on hover, and clicking the "&times;" should dismiss the message without need for further interaction.
 
  ![Explanatory text anti&#45;pattern &#45; incorrect](../../extensibility/ux-guidelines/media/incorrectuseofmultipleclicks.png "Incorrectuseofmultipleclicks")<br />Incorrect video link pattern
 
-#### Result
- Instead of a simple close button (one click), the user is forced to use two clicks to simply dismiss the UI in every place that the video links appear.
+Instead of a simple close button (one click), the user is forced to use two clicks to simply dismiss the UI in every place that the video links appear.
 
-#### Alternatives
- The correct design for this situation would be to follow the pattern common to Internet Explorer, Office, and Visual Studio: on hover, the user can see the tooltip description and one click hides the UI.
+The correct design for this situation is to follow the pattern common to Internet Explorer, Office, and Visual Studio: on hover, the user can see the tooltip description and one click hides the UI.
 
  ![Explanatory text anti&#45;pattern &#45; correct](../../extensibility/ux-guidelines/media/explanatorytextanti-pattern-correct.png "Explanatorytextanti-pattern-correct")<br />Correct video link pattern
 
 ### Using command bars for settings
- **Figure A** represents this anti-pattern: putting a setting underneath a command button that applies to more than just the command. In this sketch, there are commands besides Start Debugging — like View in Browser, Start Without Debugging, and Step Into — that will respect the selected setting.
 
-  ![Figure A: Command bar anti-pattern](../../extensibility/ux-guidelines/media/commandbaranti-pattern-figurea.png "Commandbaranti-pattern-FigureA")<br />Figure A: Command bar anti-pattern
+**Figure A** represents this anti-pattern: putting a setting underneath a command button that applies to more than just the command. In this sketch, there are commands besides Start Debugging — like View in Browser, Start Without Debugging, and Step Into — that will respect the selected setting.
+
+![Figure A: Command bar anti-pattern](../../extensibility/ux-guidelines/media/commandbaranti-pattern-figurea.png "Commandbaranti-pattern-FigureA")<br />Figure A: Command bar anti-pattern
 
- Slightly better, but still undesirable, is putting settings of this type in the toolbars, as shown in **Figure B**. While split buttons take less space and are therefore an improvement over drop-downs, both designs are still using a toolbar to promote something that isn't really a command.
+Slightly better, but still undesirable, is putting settings of this type in the toolbars, as shown in **Figure B**. While split buttons take less space and are therefore an improvement over drop-downs, both designs are still using a toolbar to promote something that isn't really a command.
 
- ![Figure B: Better, but still a command bar anti-pattern](../../extensibility/ux-guidelines/media/commandbaranti-pattern-figureb.png "Commandbaranti-pattern-FigureB")<br />Figure B: Better, but still a command bar anti-pattern
+![Figure B: Better, but still a command bar anti-pattern](../../extensibility/ux-guidelines/media/commandbaranti-pattern-figureb.png "Commandbaranti-pattern-FigureB")<br />Figure B: Better, but still a command bar anti-pattern
 
-  In the correct approach shown in **Figure C**, the setting is tied to a series of commands. There is no global setting being set and we're just switching between four commands. This is the only situation in which commands in the toolbar are acceptable.
+In the correct approach shown in **Figure C**, the setting is tied to a series of commands. There is no global setting being set and we're just switching between four commands. This is the only situation in which commands in the toolbar are acceptable.
 
- ![Figure C: Correct use of Visual Studio command bar pattern](../../extensibility/ux-guidelines/media/commandbaranti-pattern-figurec.png "Commandbaranti-pattern-FigureC")<br />Figure C: Correct use of Visual Studio command bar pattern
+![Figure C: Correct use of Visual Studio command bar pattern](../../extensibility/ux-guidelines/media/commandbaranti-pattern-figurec.png "Commandbaranti-pattern-FigureC")<br />Figure C: Correct use of Visual Studio command bar pattern
 
 ### Control anti-patterns
  Some anti-patterns are simply incorrect usage or presentation of a control or group of controls.
 
 #### Underlining used as a group label, not a hyperlink
  Underlining text should be used only for hyperlinks.
 
- **Bad:**
+ **Bad:**\
  ![Underlined text that is not a hyperlink is a Visual Studio anti-pattern.](../../extensibility/ux-guidelines/media/0102-g_grouplabelincorrect.png "0102-g_GroupLabelIncorrect")<br />Underlined text that is not a hyperlink is a Visual Studio anti-pattern.
 
- **Good:**
+ **Good:**\
  ![Styled correctly, non-hyperlink text appears unadorned in the environment font.](../../extensibility/ux-guidelines/media/0102-h_grouplabelcorrect.png "0102-h_GroupLabelCorrect")<br />Styled correctly, non-hyperlink text appears unadorned in the environment font.
 
 #### Clicking on a check box results in a pop-up dialog
@@ -139,15 +140,15 @@ Forcing the user to read explanatory text before dismissing UI is an anti-patter
  ![Bringing up a dialog after clicking a check box is a Visual Studio anti-pattern.](../../extensibility/ux-guidelines/media/0102-i_checkboxpopup.png "0102-i_CheckboxPopup")<br />Bringing up a dialog after clicking a check box is a Visual Studio anti-pattern.
 
 ### Hyperlink anti-patterns
- The following example contains two anti-patterns.
+ The following example contains two anti-patterns:
 
 1. The foreground turning red on hover means that the correct shared color from the font service is not being used.
 
 2. "Learn more" is not the appropriate text for a link to a conceptual topic. The user's goal is not to learn more, it is to understand the ramifications of their choice.
 
    ![Ignoring the color service and using "Learn more" for hyperlinks are Visual Studio anti-patterns.](../../extensibility/ux-guidelines/media/0102-j_hyperlinkincorrect.png "0102-j_HyperlinkIncorrect")<br />Ignoring the color service and using "Learn more" for hyperlinks are Visual Studio anti-patterns.
 
-   **Better solution:** Pose the question the user would be asking by clicking the link.
+**Better solution:** Pose the question the user would be asking by clicking the link. For example:
 
 - How do Windows Azure services work?