Merge pull request #2467 from damabe/1235779

Content fixes for VS extensibility articles

Author: TrishaMc

docs/extensibility/about-file-name-extensions.md

@@ -15,23 +15,23 @@ manager: douge
 ms.workload: 
   - "vssdk"
 ---
-# About File Name Extensions
+# About file name extensions
 When you register a file extension of a VSPackage, you associate it with a version of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)]. This is important if more than one version of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] is installed on a computer.  
 
- File extensions for VSPackages are registered under HKEY_CLASSES_ROOT key with a default value that points to the associated programmatic identifier (ProgID).  
+ File extensions for VSPackages are registered under **HKEY_CLASSES_ROOT** key with a default value that points to the associated programmatic identifier (ProgID).  
 
- The following is an example of the registration information for the .vcproj file extension:  
+ The following example shows registration information for the *.vcproj* file extension:  
 
 ```  
 HKEY_CLASSES_ROOT\  
    .vcproj\  
       (default)=" VisualStudio.vcproj.8.0"   
 ```  
 
- Files associated with [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] must have a versioned ProgID, such as `VisualStudio.vcproj.8.0`, to allow side-by-side installations of the product to maintain file extension associations among product versions. A version-specific ProgID also allows you to use standard verbs, such as open, edit, and so on, without the concern of overwriting or being overwritten by other applications or versions of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)].  
+ Files associated with [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] must have a versioned ProgID, such as `VisualStudio.vcproj.8.0`. A versioned ProgID allows side-by-side installations of the product to maintain file extension associations among product versions. A version-specific ProgID also allows you to use standard verbs, such as open, edit, and so on, without the concern of overwriting or being overwritten by other applications or versions of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)].  
 
- In certain cases, the ProgID associated with a file extension should not be changed. For example, the ProgID for the .htm file extension (progid = htmlfile) is hard coded in a number of places in the operating system, and is widely known and used in association with .htm and .html files.  
+ In certain cases, the ProgID associated with a file extension should not be changed. For example, the ProgID for the *.htm* file extension (progid = htmlfile) is hard-coded in a number of places in the operating system, and is widely known and used in association with *.htm* and *.html* files.  
 
-## See Also  
- [Registering File Name Extensions for Side-By-Side Deployments](../extensibility/registering-file-name-extensions-for-side-by-side-deployments.md)   
- [Specifying File Handlers for File Name Extensions](../extensibility/specifying-file-handlers-for-file-name-extensions.md)
+## See also  
+ [Register file name extensions for side-by-side deployments](../extensibility/registering-file-name-extensions-for-side-by-side-deployments.md)   
+ [Specify file handlers for file name extensions](../extensibility/specifying-file-handlers-for-file-name-extensions.md)

docs/extensibility/accessing-stored-font-and-color-settings.md

@@ -16,10 +16,10 @@ manager: douge
 ms.workload:
   - "vssdk"
 ---
-# Accessing Stored Font and Color Settings
+# Access stored font and color settings
 The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] integrated development environment (IDE) stores modified settings for fonts and colors in the registry. You can use the <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage> interface to access these settings.
 
-## To Initiate State Persistence of Fonts and Colors
+## To initiate state persistence of fonts and colors
  Font and color information is stored by category in the following registry location: [HKCU\SOFTWARE\Microsoft \Visual Studio\\*\<Visual Studio version>*\FontAndColors\\*\<CategoryGUID>*], where *\<CategoryGUID>* is the category GUID.
 
  Therefore, to initiate persistence, a VSPackage must:
@@ -40,7 +40,7 @@ The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] integrated develop
 
     -   The format of color values that are used.
 
-## To Use State Persistence of Fonts and Colors
+## To use state persistence of fonts and colors
  Persisting fonts and colors involves:
 
 -   Synchronizing the IDE settings with settings stored in the registry.
@@ -58,7 +58,7 @@ The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] integrated develop
 > [!NOTE]
 >  Modifications through the **Font and Color** property page generate events independent of <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage>. You can use the <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorCacheManager> interface to determine whether an update of cached font and color settings is needed before calling the methods of the <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage> class.
 
-### Storing and Retrieving Information
+### Store and retrieve information
  To obtain or configure information that a user can modify for a named display item in an open category, VSPackages call the <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage.GetItem%2A> and <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage.SetItem%2A> methods.
 
  Information about font attributes for a particular category is obtained by using the <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage.GetFont%2A> and <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage.SetFont%2A> methods.
@@ -73,8 +73,8 @@ The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] integrated develop
 
  The settings of all **Display Items** in a particular **Category** can be obtained by using the methods of the <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorDefaults> interface.
 
-## See Also
+## See also
 
 - <xref:Microsoft.VisualStudio.Shell.Interop.IVsFontAndColorStorage>
 - <xref:Microsoft.VisualStudio.Shell.Interop.__FCSTORAGEFLAGS>
-- [Implementing Custom Categories and Display Items](../extensibility/implementing-custom-categories-and-display-items.md)
+- [Implement custom categories and display items](../extensibility/implementing-custom-categories-and-display-items.md)

docs/extensibility/accessing-text-layers-by-using-the-legacy-api.md

@@ -14,12 +14,12 @@ manager: douge
 ms.workload: 
   - "vssdk"
 ---
-# Accessing Text Layers by Using the Legacy API
+# Access text layers by using the legacy API
 A text layer typically encapsulates some aspect of text layout. For example, a "function-at-a-time" layer hides text before and after a function containing the caret (text insertion point).  
 
  A text layer resides between a buffer and a view, and it modifies the way the view sees the buffer's contents.  
 
-## Text Layer Information  
+## Text layer information  
  The following list describes how text layers work in [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)]:  
 
 -   The text in a text layer can be adorned with syntax coloring and markers.  
@@ -32,7 +32,7 @@ A text layer typically encapsulates some aspect of text layout. For example, a "
 
 -   A layer can affect only layers that are below it. It cannot affect the layers above it beyond originating standard events.  
 
--   In the editor, hidden text, synthetic text, and word wrap are implemented as layers. You can implement hidden and synthetic text without interacting directly with the layers. For more information, see [Outlining in a Legacy Language Service](../extensibility/internals/outlining-in-a-legacy-language-service.md) and <xref:Microsoft.VisualStudio.TextManager.Interop.IVsSyntheticTextSession>.  
+-   In the editor, hidden text, synthetic text, and word wrap are implemented as layers. You can implement hidden and synthetic text without interacting directly with the layers. For more information, see [Outlining in a legacy language service](../extensibility/internals/outlining-in-a-legacy-language-service.md) and <xref:Microsoft.VisualStudio.TextManager.Interop.IVsSyntheticTextSession>.  
 
 -   Each text layer has its own local coordinate system that is exposed through the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextLayer> interface. The line-wrap layer, for example, might contain two lines while the underlying text buffer might contain only one line.  
 
@@ -42,7 +42,7 @@ A text layer typically encapsulates some aspect of text layout. For example, a "
 
 -   Besides <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextLayer>, a text layer must implement <xref:Microsoft.VisualStudio.OLE.Interop.IConnectionPointContainer> and fire the events in the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextLinesEvents> interface.  
 
-## See Also  
- [Syntax Coloring in Custom Editors](../extensibility/syntax-coloring-in-custom-editors.md)   
- [Using Text Markers with the Legacy API](../extensibility/using-text-markers-with-the-legacy-api.md)   
- [Customizing Editor Controls and Menus by Using the Legacy API](../extensibility/customizing-editor-controls-and-menus-by-using-the-legacy-api.md)
+## See also  
+ [Syntax coloring in custom editors](../extensibility/syntax-coloring-in-custom-editors.md)   
+ [Use text markers with the legacy API](../extensibility/using-text-markers-with-the-legacy-api.md)   
+ [Customize editor controls and menus by using the legacy API](../extensibility/customizing-editor-controls-and-menus-by-using-the-legacy-api.md)

docs/extensibility/accessing-the-text-buffer-by-using-the-legacy-api.md

@@ -14,10 +14,10 @@ manager: douge
 ms.workload: 
   - "vssdk"
 ---
-# Accessing the Text Buffer by Using the Legacy API
+# Access the text buffer by using the legacy API
 The text is responsible for managing text streams and file persistence. Although the buffer can read or write other formats, all ordinary communication with the buffer is performed by using Unicode. In the legacy APIs, the text buffer can use either a one- or a two-dimensional coordinate system to identify character locations in the buffer.  
 
-## One- and Two-Dimension Coordinate Systems  
+## One- and two-dimension coordinate systems  
  A one-dimensional coordinate position is based on a character's position from the first character in the buffer, such as 147. You use the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextStream> interface to access a one-dimensional location in the buffer. A two-dimensional coordinate system is based on line and index pairs. For example, a character in the buffer at 43, 5 would be on line 43, five characters to the right of the first character in that line. You access a two-dimensional location in the buffer using the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextLines> interface. Both the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextLines> and the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextStream> interfaces are implemented by the text buffer object (<xref:Microsoft.VisualStudio.TextManager.Interop.VsTextBuffer>) and can be accessed from each other by using `QueryInterface`. The following diagram shows these and other key interfaces on <xref:Microsoft.VisualStudio.TextManager.Interop.VsTextBuffer>.  
 
  ![Text Buffer Object](../extensibility/media/vstextbuffer.gif "vsTextBuffer")  
@@ -27,12 +27,12 @@ Text buffer object
 
  The text buffer's second responsibility is file persistence. To do this, the text buffer object implements <xref:Microsoft.VisualStudio.Shell.Interop.IVsPersistDocData2> and acts as the document data object component for project items and other environment components involved in persistence. For more information, see [Opening and Saving Project Items](../extensibility/internals/opening-and-saving-project-items.md).  
 
-## In This Section  
- [Changing View Settings by Using the Legacy API](../extensibility/changing-view-settings-by-using-the-legacy-api.md)  
+## In this section  
+ [Change view settings by using the legacy API](../extensibility/changing-view-settings-by-using-the-legacy-api.md)  
  Explains how to change view settings using the legacy API.  
 
- [Using the Text Manager to Monitor Global Settings](../extensibility/using-the-text-manager-to-monitor-global-settings.md)  
- Explains how to use the text manager to monitor global settings..  
+ [Use the text manager to monitor global settings](../extensibility/using-the-text-manager-to-monitor-global-settings.md)  
+ Explains how to use the text manager to monitor global settings.  
 
-## See Also  
- [Inside the Core Editor](../extensibility/inside-the-core-editor.md)
+## See also  
+ [Inside the core editor](../extensibility/inside-the-core-editor.md)

docs/extensibility/accessing-thetext-view-by-using-the-legacy-api.md

@@ -14,10 +14,10 @@ manager: douge
 ms.workload:
   - "vssdk"
 ---
-# Accessing theText View by Using the Legacy API
+# Access the text view by using the legacy API
 A text view is a presentation of the text that is stored in a text buffer. You can access the text view by using the legacy API as shown in the following section.
 
-## Text View Object
+## Text view object
  Each view is associated with its own text buffer, and the view is a window on the data in the buffer. The following diagram shows the key interfaces of the text view object, which is represented by <xref:Microsoft.VisualStudio.TextManager.Interop.VsTextView>.
 
  ![Visual Studio Text View Object](../extensibility/media/vstextview.gif "vstextview")
@@ -27,14 +27,14 @@ Text view object
 
  A view enables other services or processes to intercept incoming commands and act on them before the view acts on them. The most common service to do this is a language service. A language service might need, for example, to intercept the command for the ENTER key to provide custom indenting behavior or tool tips.
 
-## Adding Functionality to the Text View
+## Add functionality to the text view
  You can customize text view behavior by handling specific keystrokes. To intercept the keystrokes, you implement <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextViewFilter> on your object, and provide a command target (<xref:Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget>) to monitor and intercept commands.
 
  The text view uses sequential architecture for command filters. New command filters (<xref:Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget> objects) are added to the sequence by calling the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextView.AddCommandFilter%2A> method.
 
  Event notification for the text view is provided by using the <xref:Microsoft.VisualStudio.TextManager.Interop.IVsTextViewEvents> interface. Implement this interface on your client object to receive notification of changes to the text view. Expose this interface to the text view by using the <xref:Microsoft.VisualStudio.OLE.Interop.IConnectionPointContainer> interface on the text view to receive notification of changes from the view.
 
-## See Also
+## See also
 
-- [Changing View Settings by Using the Legacy API](../extensibility/changing-view-settings-by-using-the-legacy-api.md)
-- [Using the Text Manager to Monitor Global Settings](../extensibility/using-the-text-manager-to-monitor-global-settings.md)
+- [Change view settings by using the legacy API](../extensibility/changing-view-settings-by-using-the-legacy-api.md)
+- [Use the text manager to monitor global settings](../extensibility/using-the-text-manager-to-monitor-global-settings.md)