Gerund fixes

Author: iRaindrop

docs/sharepoint/how-to-add-a-custom-sharepoint-node-to-server-explorer.md

@@ -89,7 +89,7 @@ ms.workload:
 
 -   System.Drawing  
 
-## Deploying the extension  
+## Deploy the extension  
  To deploy the **Server Explorer** extension, create a [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] extension (VSIX) package for the assembly and any other files that you want to distribute with the extension. For more information, see [Deploy extensions for the SharePoint Tools in Visual Studio](../sharepoint/deploying-extensions-for-the-sharepoint-tools-in-visual-studio.md).  
 
 ## See also

docs/sharepoint/how-to-add-a-property-to-a-custom-sharepoint-project-item-type.md

@@ -37,12 +37,12 @@ ms.workload:
  [!code-vb[SPExtensibility.ProjectItemExtension.MenuAndProperty#11](../sharepoint/codesnippet/VisualBasic/projectitemmenuandproperty/extension/projectitemtypeproperty.vb#11)]
  [!code-csharp[SPExtensibility.ProjectItemExtension.MenuAndProperty#11](../sharepoint/codesnippet/CSharp/projectitemmenuandproperty/extension/projectitemtypeproperty.cs#11)]  
 
-### Understanding the code  
+### Understand the code  
  To ensure that the same instance of the `CustomProperties` class is used each time the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItemEvents.ProjectItemPropertiesRequested> event occurs, the code example saves the properties object to the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property of the project item the first time this event occurs. The code retrieves this object whenever this event occurs again. For more information about using the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property to save data with project items, see [Associate custom data with SharePoint tools extensions](../sharepoint/associating-custom-data-with-sharepoint-tools-extensions.md).  
 
  To persist changes to the property value, the **set** accessor for `ExampleProperty` saves the new value to the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItem.ExtensionData%2A> property of the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItem> object that the property is associated with. For more information about using the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItem.ExtensionData%2A> property to persist data with project items, see [Save data in extensions of the SharePoint project system](../sharepoint/saving-data-in-extensions-of-the-sharepoint-project-system.md).  
 
-### Specifying the behavior of custom properties  
+### Specify the behavior of custom properties  
  You can define how a custom property appears and behaves in the **Properties** window by applying attributes from the <xref:System.ComponentModel> namespace to the property definition. The following attributes are useful in many scenarios:  
 
 -   <xref:System.ComponentModel.DisplayNameAttribute>: Specifies the name of the property that appears in the **Properties** window.  
@@ -55,14 +55,14 @@ ms.workload:
 
 -   <xref:System.ComponentModel.EditorAttribute>: Specifies a custom editor to use to modify the property.  
 
-## Compiling the code  
+## Compile the code  
  These code examples require a class library project with references to the following assemblies:  
 
 -   Microsoft.VisualStudio.SharePoint  
 
 -   System.ComponentModel.Composition  
 
-## Deploying the project item  
+## Deploy the project item  
  To enable other developers to use your project item, create a project template or a project item template. For more information, see [Create item templates and project templates for SharePoint project items](../sharepoint/creating-item-templates-and-project-templates-for-sharepoint-project-items.md).  
 
  To deploy the project item, create a [!include[vsprvs](../sharepoint/includes/vsprvs-md.md)] extension (VSIX) package for the assembly, the template, and any other files that you want to distribute with the project item. For more information, see [Deploy extensions for the SharePoint tools in Visual Studio](../sharepoint/deploying-extensions-for-the-sharepoint-tools-in-visual-studio.md).  

docs/sharepoint/how-to-add-a-property-to-a-sharepoint-project-item-extension.md

@@ -37,12 +37,12 @@ ms.workload:
  [!code-csharp[SPExtensibility.ProjectItemExtension.MenuAndProperty#8](../sharepoint/codesnippet/CSharp/projectitemmenuandproperty/extension/projectitemextensionproperty.cs#8)]
  [!code-vb[SPExtensibility.ProjectItemExtension.MenuAndProperty#8](../sharepoint/codesnippet/VisualBasic/projectitemmenuandproperty/extension/projectitemextensionproperty.vb#8)]  
 
-### Understanding the code  
+### Understand the code  
  To ensure that the same instance of the `CustomProperties` class is used each time the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItemEvents.ProjectItemPropertiesRequested> event occurs, the code example adds the properties object to the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property of the project item the first time this event occurs. The code retrieves this object whenever this event occurs again. For more information about using the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property to associate data with project items, see [Associate custom data with SharePoint tools extensions](../sharepoint/associating-custom-data-with-sharepoint-tools-extensions.md).  
 
  To persist changes to the property value, the **set** accessor for `ExampleProperty` saves the new value to the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItem.ExtensionData%2A> property of the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItem> object that the property is associated with. For more information about using the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItem.ExtensionData%2A> property to persist data with project items, see [Save data in extensions of the SharePoint project system](../sharepoint/saving-data-in-extensions-of-the-sharepoint-project-system.md).  
 
-### Specifying the behavior of custom properties  
+### Specify the behavior of custom properties  
  You can define how a custom property appears and behaves in the **Properties** window by applying attributes from the <xref:System.ComponentModel> namespace to the property definition. The following attributes are useful in many scenarios:  
 
 -   <xref:System.ComponentModel.DisplayNameAttribute>: Specifies the name of the property that appears in the **Properties** window.  
@@ -55,14 +55,14 @@ ms.workload:
 
 -   <xref:System.ComponentModel.EditorAttribute>: Specifies a custom editor to use to modify the property.  
 
-## Compiling the code  
+## Compile the code  
  These examples require a class library project with references to the following assemblies:  
 
 -   Microsoft.VisualStudio.SharePoint  
 
 -   System.ComponentModel.Composition  
 
-## Deploying the extension  
+## Deploy the extension  
  To deploy the extension, create a [!include[vsprvs](../sharepoint/includes/vsprvs-md.md)] extension (VSIX) package for the assembly and any other files that you want to distribute with the extension. For more information, see [Deploy extensions for the SharePoint tools in Visual Studio](../sharepoint/deploying-extensions-for-the-sharepoint-tools-in-visual-studio.md).  
 
 ## See also

docs/sharepoint/how-to-add-a-property-to-sharepoint-projects.md

@@ -37,7 +37,7 @@ ms.workload:
  [!code-vb[SpExt_SPCustomPrjProperty#1](../sharepoint/codesnippet/VisualBasic/customspproperty/customproperty.vb#1)]
  [!code-csharp[SpExt_SPCustomPrjProperty#1](../sharepoint/codesnippet/CSharp/customspproperty/customproperty.cs#1)]  
 
-### Understanding the code  
+### Understand the code  
  To ensure that the same instance of the `CustomProjectProperties` class is used each time the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectEvents.ProjectPropertiesRequested> event occurs, the code example adds the properties object to the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property of the project the first time this event occurs. The code retrieves this object whenever this event occurs again. For more information about using the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property to associate data with projects, see [Associate custom data with SharePoint tools extensions](../sharepoint/associating-custom-data-with-sharepoint-tools-extensions.md).  
 
  To persist changes to the property values, the **set** accessors for the properties use the following APIs:  
@@ -48,7 +48,7 @@ ms.workload:
 
  For more information about persisting data in these files, see [Save data in extensions of the SharePoint project system](../sharepoint/saving-data-in-extensions-of-the-sharepoint-project-system.md).  
 
-### Specifying the behavior of custom properties  
+### Specify the behavior of custom properties  
  You can define how a custom property appears and behaves in the **Properties** window by applying attributes from the <xref:System.ComponentModel> namespace to the property definition. The following attributes are useful in many scenarios:  
 
 -   <xref:System.ComponentModel.DisplayNameAttribute>: Specifies the name of the property that appears in the **Properties** window.  
@@ -61,7 +61,7 @@ ms.workload:
 
 -   <xref:System.ComponentModel.EditorAttribute>: Specifies a custom editor to use to modify the property.  
 
-## Compiling the code  
+## Compile the code  
  This example requires references to the following assemblies:  
 
 -   Microsoft.VisualStudio.SharePoint
@@ -74,7 +74,7 @@ ms.workload:
 -     
 -   System.ComponentModel.Composition  
 
-## Deploying the extension  
+## Deploy the extension  
  To deploy the extension, create a [!include[vsprvs](../sharepoint/includes/vsprvs-md.md)] extension (VSIX) package for the assembly and any other files that you want to distribute with the extension. For more information, see [Deploy extensions for the SharePoint tools in Visual Studio](../sharepoint/deploying-extensions-for-the-sharepoint-tools-in-visual-studio.md).  
 
 ## See also

docs/sharepoint/how-to-add-a-shortcut-menu-item-to-a-custom-sharepoint-project-item-type.md

@@ -39,14 +39,14 @@ ms.workload:
 
  This example uses the SharePoint project service to write the message to the **Output** window. For more information, see [Use the SharePoint project service](../sharepoint/using-the-sharepoint-project-service.md).  
 
-## Compiling the code  
+## Compile the code  
  This example requires a class library project with references to the following assemblies:  
 
 -   Microsoft.VisualStudio.SharePoint  
 
 -   System.ComponentModel.Composition  
 
-## Deploying the project item  
+## Deploy the project item  
  To enable other developers to use your project item, create a project template or a project item template. For more information, see [Create item templates and project templates for SharePoint project items](../sharepoint/creating-item-templates-and-project-templates-for-sharepoint-project-items.md).  
 
  To deploy the project item, create a [!include[vsprvs](../sharepoint/includes/vsprvs-md.md)] extension (VSIX) package for the assembly, the template, and any other files that you want to distribute with the project item. For more information, see [Deploy extensions for the SharePoint tools in Visual Studio](../sharepoint/deploying-extensions-for-the-sharepoint-tools-in-visual-studio.md).  

docs/sharepoint/how-to-add-a-shortcut-menu-item-to-a-sharepoint-project-item-extension.md

@@ -39,14 +39,14 @@ ms.workload:
 
  This example uses the SharePoint project service to write the message to the **Output** window. For more information, see [Use the SharePoint project service](../sharepoint/using-the-sharepoint-project-service.md).  
 
-## Compiling the code  
+## Compile the code  
  This example requires a class library project with references to the following assemblies:  
 
 -   Microsoft.VisualStudio.SharePoint  
 
 -   System.ComponentModel.Composition  
 
-## Deploying the extension  
+## Deploy the extension  
  To deploy the extension, create a [!include[vsprvs](../sharepoint/includes/vsprvs-md.md)] extension (VSIX) package for the assembly and any other files that you want to distribute with the extension. For more information, see [Deploy extensions for the SharePoint tools in Visual Studio](../sharepoint/deploying-extensions-for-the-sharepoint-tools-in-visual-studio.md).  
 
 ## See also

docs/sharepoint/how-to-add-a-shortcut-menu-item-to-sharepoint-projects.md

@@ -37,14 +37,14 @@ ms.workload:
  [!code-csharp[SPExtensibility.ProjectExtension.Menu#1](../sharepoint/codesnippet/CSharp/projectmenu/extension/projectitemextensionmenu.cs#1)]
  [!code-vb[SPExtensibility.ProjectExtension.Menu#1](../sharepoint/codesnippet/VisualBasic/projectmenu/extension/projectitemextensionmenu.vb#1)]  
 
-## Compiling the code  
+## Compile the code  
  This example requires a class library project with references to the following assemblies:  
 
 -   Microsoft.VisualStudio.SharePoint
 -     
 -   System.ComponentModel.Composition  
 
-## Deploying the extension  
+## Deploy the extension  
  To deploy the extension, create a [!include[vsprvs](../sharepoint/includes/vsprvs-md.md)] extension (VSIX) package for the assembly and any other files that you want to distribute with the extension. For more information, see [Deploy extensions for the SharePoint tools in Visual Studio](../sharepoint/deploying-extensions-for-the-sharepoint-tools-in-visual-studio.md).  
 
 ## See also

docs/sharepoint/how-to-add-and-remove-additional-assemblies.md

@@ -25,7 +25,7 @@ ms.workload:
 
  You can also add and change the safe controls and class resource files associated with the assemblies.  
 
-## Adding additional assemblies, safe controls, and class resources  
+## Add additional assemblies, safe controls, and class resources  
  You can add additional assemblies into the SharePoint solution package. Additional assemblies in a sandboxed solution deploy to the global assembly cache, but SharePoint project items in a sandboxed solution are added to the content database. You can also add safe controls and class resources to these additional assemblies. For more information about safe controls, see [Providing Packaging and Deployment Information in Project Items](../sharepoint/providing-packaging-and-deployment-information-in-project-items.md) or "Creating a SafeControl Entry" in [Deploying Web Parts in SharePoint Foundation](http://go.microsoft.com/fwlink/?LinkId=245505).  
 
 #### To add an existing assembly  
@@ -78,7 +78,7 @@ ms.workload:
 
 3.  In the **File Name** column, choose the ellipsis (![ASP.NET Mobile Designer ellipse](../sharepoint/media/mwellipsis.gif "ASP.NET Mobile Designer ellipse")), and choose the class resource that you want to add.  
 
-## Deleting custom assemblies  
+## Delete custom assemblies  
  You can delete assemblies from a SharePoint package, or delete safe controls and class resources from existing assemblies.  
 
 #### To delete an existing assembly  

docs/sharepoint/how-to-add-and-remove-feature-dependencies.md

@@ -24,7 +24,7 @@ ms.workload:
 # How to: Add and remove feature dependencies
   Your SharePoint Feature may depend on other Features for functionality or data. In these cases, you can mark these other Features as dependencies for your Feature. This way, the SharePoint server ensures that dependent Features are activated before your Feature is activated.  
 
-## Adding dependencies  
+## Add dependencies  
  You can add other Features in your solution as dependencies. This way, you can make sure that required Features are installed and activated before your feature is installed.  
 
 #### To add a dependency on a feature in the solution
@@ -35,7 +35,7 @@ ms.workload:
 
      You can add more than one feature by choosing multiple titles while choosing the **Ctrl** key.  
 
-## Adding custom dependencies  
+## Addi custom dependencies  
  You can add Features that are already deployed on a SharePoint server as a dependency. This way, the SharePoint activation process checks to make sure that all dependent Features are activated before your Feature is installed.  
 
 #### To add a dependency by the feature ID
@@ -46,7 +46,7 @@ ms.workload:
 
 3.  In the **Feature ID** text box, enter the GUID for the Feature that you want to mark as an activation dependency, and then choose the **Add** button.  
 
-## Editing custom dependencies  
+## Edit custom dependencies  
  You can edit custom dependencies that you added previously. However, dependent Features that are in your solution can only be removed, not edited.  
 
 #### To change a dependency on a feature in the solution
@@ -57,7 +57,7 @@ ms.workload:
 
 3.  In the **Edit Custom Feature Activation Dependency** dialog box, change the title, Feature ID, or description, and then choose the **Submit** button.  
 
-## Removing dependencies  
+## Remove dependencies  
 
 #### To remove a dependency on a feature in the solution
 

docs/sharepoint/how-to-add-and-remove-features-and-items-to-a-package-by-using-the-package-designer.md

@@ -25,7 +25,7 @@ ms.workload:
 
  Alternatively, you can use the Packaging Explorer to add and remove SharePoint project items. You can also view and change the hierarchy of the SharePoint project items and Features that are put into the package (.wsp). For more information, see [How to: Add and remove features and items to a Package by using the Packaging Explorer](../sharepoint/how-to-add-and-remove-features-and-items-to-a-package-by-using-the-packaging-explorer.md).  
 
-## Adding features to a SharePoint package  
+## Add features to a SharePoint package  
  You can use the Package Designer to add Features to a SharePoint package.  
 
 #### To add SharePoint features with the package designer
@@ -46,7 +46,7 @@ ms.workload:
 
      The SharePoint Project Items and Features appear in the **Items in the Package** list.  
 
-## Removing Features from a SharePoint Package  
+## Remove Features from a SharePoint Package  
  You can use the Package Designer to remove Features to a SharePoint package.  
 
 #### To remove SharePoint features with the package designer

docs/sharepoint/how-to-add-and-remove-features-and-items-to-a-package-by-using-the-packaging-explorer.md

@@ -25,7 +25,7 @@ ms.workload:
 
  Alternatively, you can use the Packaging Designer to view and re-order the Features to change the activation order. For more information, see [How to: Add and remove features and items to a package by using the Package Designer](../sharepoint/how-to-add-and-remove-features-and-items-to-a-package-by-using-the-package-designer.md).  
 
-## Opening the Packaging Explorer  
+## Open the Packaging Explorer  
  You can use the following procedure to open the Packaging Explorer, if your Visual Studio solution has at least one SharePoint project. Alternatively, the Packaging Explorer opens automatically when you view a Feature or package designer. After you close all Feature and package designers, the Packaging Explorer also closes.  
 
 #### To open the Packaging Explorer  
@@ -52,7 +52,7 @@ ms.workload:
     > [!NOTE]  
     >  Use this procedure if you have more than one SharePoint project in your solution.  
   
-## Validating a feature or package  
+## Validate a feature or package  
  You can identify potential problems in the SharePoint Features and packages by validating the files. Warnings and errors are displayed in the Output window and Error List window.  
 
 #### To validate a SharePoint feature or package

docs/sharepoint/how-to-add-and-remove-items-to-sharepoint-features.md

@@ -23,7 +23,7 @@ ms.workload:
 # How to: Add and remove items to SharePoint features
   When you create a SharePoint solution, Visual Studio adds the default SharePoint project items to your Feature. Before deployment, you can add and remove SharePoint project items to modify the SharePoint Feature.  
 
-## Adding SharePoint project items to a feature  
+## Add SharePoint project items to a feature  
 
 #### To add SharePoint project items with the Feature Designer  
 
@@ -41,7 +41,7 @@ ms.workload:
 
      The SharePoint Project Items appear in the **Items in the Feature** list.  
 
-## Removing SharePoint project items from a feature  
+## Remove SharePoint project items from a feature  
 
 #### To remove SharePoint items with the Feature Designer