Merge pull request #2170 from iRaindrop/vbruham_sharepoint_g

VS SharePoint Content QA: A-C missing fixes

Author: TrishaMc

docs/sharepoint/associating-custom-data-with-sharepoint-tools-extensions.md

@@ -20,7 +20,7 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Associating custom data with SharePoint tools extensions
+# Associate custom data with SharePoint tools extensions
   You can add custom data to certain objects in SharePoint tools extensions. This is useful when you have data in one part of your extension that you want to access later from other code in your extension. Instead of implementing a custom way to store and access data, you can associate the data with an object in your extension and then retrieve the data from the same object later.  
 
  Adding custom data to objects is also useful when you want to preserve data that is relevant to a specific item in Visual Studio. SharePoint tools extensions are loaded just once in Visual Studio, so your extension might work with several different items (such as projects, project items, or **Server Explorer** nodes) at any time. If you have custom data that is relevant only to a specific item, you can add the data to the object that represents that item.  
@@ -81,5 +81,6 @@ ms.workload:
  [Walkthrough: Creating a Custom Action Project Item with an Item Template, Part 1](../sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-1.md)   
  [Walkthrough: Extending Server Explorer to Display Web Parts](../sharepoint/walkthrough-extending-server-explorer-to-display-web-parts.md)   
  [How to: Add a Property to SharePoint Projects](../sharepoint/how-to-add-a-property-to-sharepoint-projects.md)   
- [How to: Add a Property to a Custom SharePoint Project Item Type](../sharepoint/how-to-add-a-property-to-a-custom-sharepoint-project-item-type.md   
+ [How to: Add a Property to a Custom SharePoint Project Item Type](../sharepoint/how-to-add-a-property-to-a-custom-sharepoint-project-item-type.md)
+   
 

docs/sharepoint/bdc-model-design-tools-overview.md

@@ -45,19 +45,19 @@ ms.workload:
 
  To open the BDC Designer, double-click the model file in your project, or open the shortcut menu for the model file and then choose **Open**. Add an entity to the model by dragging or copying an **Entity** from the **Toolbox** onto the designer. To create an association between two entities, choose the **Association** control in the **Toolbox**, choose the first entity, and then choose the second entity.  
 
-## BDC method details window
+## BDC Method Details window
  Use the **BDC Method Details** window to define the parameters, instances, and filter descriptors of a method.  
 
  You can quickly generate Finder, Specific Finder, Creator, Updater, and Deleter methods in the **BDC Method Details** window. When you generate these methods, Visual Studio adds metadata, such as parameters, instances, and type descriptors, to the method. You can modify this metadata to satisfy your specific scenario.  
 
- To open the **BDC Method Details** window, on the menu bar, choose **View**, **Other Windows**, **BDC Method Details**.  
+ To open the **BDC Method Details** window, on the menu bar, choose **View** > **Other Windows** > **BDC Method Details**.  
 
  To view methods in the **BDC Method Details** window, choose the entity in the BDC Designer. The methods of the selected entity appear in the **BDC Method Details** window. If you do not choose an entity in the BDC Designer, the **BDC Method Details** window displays no information.  
 
  Expand or collapse nodes in the **BDC Method Details** window to define parameters, instances, and filter descriptors. Use the **BDC Explorer** to define type descriptors.  
 
 ## BDC Explorer
- The **BDC Explorer** displays the elements that make up the model. To open the **BDC Explorer**, on the menu bar, choose **View**, **Other Windows**, **BDC Explorer**. To browse the model, expand nodes in the **BDC Explorer**. Each node represents an element in the XML of the model file.  
+ The **BDC Explorer** displays the elements that make up the model. To open the **BDC Explorer**, on the menu bar, choose **View** > **Other Windows** > **BDC Explorer**. To browse the model, expand nodes in the **BDC Explorer**. Each node represents an element in the XML of the model file.  
 
  As you choose nodes in the **BDC Explorer**, the properties of each node that you choose appear in the **Properties** window. Many of these properties correspond to attributes in the model file. You can search the model by using the search box at the top of the **BDC Explorer**.  
 

docs/sharepoint/browsing-sharepoint-connections-using-server-explorer.md

@@ -22,8 +22,8 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Browsing SharePoint connections that use Server Explorer
-  You can now browse local SharePoint connections in **Server Explorer**. By using this technique, you can navigate through the components of a SharePoint site on your system. SharePoint site components, such as list definitions and content types, appear in a node that's named **SharePoint Connections** in the tree view of **Server Explorer**. To display **Server Explorer**, on the menu bar, choose **View**, **Server Explorer**. In addition to displaying the SharePoint site components, you can remove items, view their properties, or refresh the tree view by using commands on the shortcut menu.  
+# Browse SharePoint connections by using Server Explorer
+  You can now browse local SharePoint connections in **Server Explorer**. By using this technique, you can navigate through the components of a SharePoint site on your system. SharePoint site components, such as list definitions and content types, appear in a node that's named **SharePoint Connections** in the tree view of **Server Explorer**. To display **Server Explorer**, on the menu bar, choose **View** > **Server Explorer**. In addition to displaying the SharePoint site components, you can remove items, view their properties, or refresh the tree view by using commands on the shortcut menu.  
 
 > [!IMPORTANT]  
 >  To browse a SharePoint site, you must be an administrator of the SharePoint site collection, and you must be running Visual Studio as an administrator of the local computer. Otherwise, the site appears in **Server Explorer**, but you can't expand its node. To verify whether you are an administrator of the site collection, open the site in a web browser, open the **Site Actions** menu, choose **Site Permissions**, and then, on the **Permissions: Team Site** page, choose the **Site Collection Administrators** command from the **Manage** group on the ribbon. Your name will appear in the text box if you are a site collection administrator. If the **Site Collection Administrators** command doesn't appear in the Manage group on the ribbon, you aren't an administrator for the site collection, and you must obtain the appropriate permissions from the site administrator.  

docs/sharepoint/building-and-debugging-sharepoint-solutions.md

@@ -19,32 +19,32 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Building and debugging SharePoint solutions
+# Build and debug SharePoint solutions
   In general, building and debugging SharePoint solutions is the same as building and debugging other types of projects in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)]. The topics in this section explain the differences that do exist.  
 
 ## Project output for SharePoint solutions
- Building SharePoint solutions creates assemblies and a solution package (.wsp) file. The following table shows the locations of these files during a build.  
+ Building SharePoint solutions creates assemblies and a solution package (*.wsp*) file. The following table shows the locations of these files during a build.  
 
 |Build item|Output folder|  
 |----------------|-------------------|  
-|Assembly, program database (PDB), and .wsp files.|*ProjectName*\bin\debug or *ProjectName*\bin\release|  
-|SharePoint project item files.|*ProjectName*\pkg\debug or *ProjectName*\pkg\release|  
-|Build intermediate files.|*ProjectName*\obj\debug or *ProjectName*\obj\release|  
-|Package intermediate files.|*ProjectName*\pkgobj\debug or *ProjectName*\pkgobj\release|  
+|Assembly, program database (*.pdb*), and *.wsp* files.|*{ProjectName}\bin\debug* or *{ProjectName}\bin\release*|  
+|SharePoint project item files.|*{ProjectName}\pkg\debug* or *{ProjectName}\pkg\release*|  
+|Build intermediate files.|*{ProjectName}\obj\debug* or *{ProjectName}\obj\release*|  
+|Package intermediate files.|*{ProjectName}\pkgobj\debug* or *{ProjectName}\pkgobj\release*|  
 
 ## Build SharePoint solutions
  To build SharePoint solutions, the development computer must have the correct version of SharePoint server installed. Otherwise, building SharePoint solutions is the same as building other types of projects in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)]. For more information, see [How to: Build SharePoint Solutions](../sharepoint/how-to-build-sharepoint-solutions.md).  
 
 ## Debug and test SharePoint solutions
- Before debugging, [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] copies the .wsp package to the SharePoint server, activates the Site and Web-scoped Features, and in some cases, starts the project. In other cases, you may have to open the project manually. For more information, see [Troubleshooting SharePoint Solutions](../sharepoint/troubleshooting-sharepoint-solutions.md) and [Debugging SharePoint Solutions](../sharepoint/debugging-sharepoint-solutions.md).  
+ Before debugging, [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] copies the *.wsp* package to the SharePoint server, activates the Site and Web-scoped Features, and in some cases, starts the project. In other cases, you may have to open the project manually. For more information, see [Troubleshooting SharePoint Solutions](../sharepoint/troubleshooting-sharepoint-solutions.md) and [Debugging SharePoint Solutions](../sharepoint/debugging-sharepoint-solutions.md).  
 
 ## Debug and verify SharePoint solutions by using ALM features
  Visual Studio ALM features such as unit testing and IntelliTrace enable you to more accurately pinpoint problems in your SharePoint solutions. Profiling enables you to locate and identify performance problem areas in your SharePoint solutions. For more information, see [Verifying and Debugging SharePoint Code](../sharepoint/verifying-and-debugging-sharepoint-code.md) and [Profiling the Performance of SharePoint Applications](../sharepoint/profiling-the-performance-of-sharepoint-applications.md).  
 
 ## Security during the build process
  To package or deploy SharePoint solutions, [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] must have permission to copy files to the SharePoint server. You must run [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] as an elevated process, and your user account must be a Site Collections Administrator on the SharePoint server. In addition, you must specify whether your project is a sandboxed solution or a farm solution. For more information, see [Differences Between Sandboxed and Farm Solutions](../sharepoint/differences-between-sandboxed-and-farm-solutions.md).  
 
-## Using the Clean Command  
+## Using the Clean command  
  When a SharePoint solution is installed on a SharePoint server for debugging, the **Clean** command does not uninstall the solution. Instead, you must deactivate the Features through the SharePoint configuration.  
 
 ## See also

docs/sharepoint/calling-into-the-sharepoint-object-models.md

@@ -19,14 +19,14 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Calling into the SharePoint object models
+# Call into the SharePoint object models
   When you create extensions for the SharePoint tools in Visual Studio, you might have to call SharePoint APIs to perform certain tasks. For example, if you create a custom deployment step for SharePoint projects, you might have to call SharePoint APIs to perform some of the tasks to deploy solutions.  
 
  [!INCLUDE[wss_14_long](../sharepoint/includes/wss-14-long-md.md)] and [!INCLUDE[moss_14_long](../sharepoint/includes/moss-14-long-md.md)] provide two different object models that you can use in SharePoint tools extensions: a server object model and a client object model. Each object model has benefits and drawbacks in the context of SharePoint tools extensions.  
 
  For an overview of the SharePoint object models, see [Overview of the Programming Model of SharePoint Tools Extensions](../sharepoint/overview-of-the-programming-model-of-sharepoint-tools-extensions.md).  
 
-## Using the client object model in extension projects
+## Use the client object model in extension projects
  When you develop an extension for the SharePoint tools, you can use the client object model in your project like any other set of managed APIs. You can add references to assemblies in the client object model to your project, and you can call APIs in the client object model directly from your code.  
 
  However, the client object model has two drawbacks in the context of SharePoint tools extensions:  
@@ -37,7 +37,7 @@ ms.workload:
 
  For a walkthrough that demonstrates how to use the client object model in an extension of the SharePoint tools in Visual Studio, see [Walkthrough: Calling into the SharePoint Client Object Model in a Server Explorer Extension](../sharepoint/walkthrough-calling-into-the-sharepoint-client-object-model-in-a-server-explorer-extension.md).  
 
-## Using the server object model in extension projects
+## Use the server object model in extension projects
  The server object model is a superset of the client object model. When you use the server object model, you can use all the features that [!INCLUDE[wss_14_long](../sharepoint/includes/wss-14-long-md.md)] and [!INCLUDE[moss_14_long](../sharepoint/includes/moss-14-long-md.md)] expose programmatically.  
 
  SharePoint tools extensions can use APIs in the server object model, but they cannot call the APIs directly. The server object model can be called only from a 64-bit process that targets the .NET Framework 3.5. However, SharePoint tools extensions require the [!INCLUDE[net_v40_short](../sharepoint/includes/net-v40-short-md.md)] and they run in the 32-bit Visual Studio process. This prevents SharePoint tools extensions from referencing the assemblies in the SharePoint server object model directly.  
@@ -49,7 +49,7 @@ ms.workload:
  For walkthroughs that demonstrate how to create and use SharePoint commands, see [Walkthrough: Creating a Custom Deployment Step for SharePoint Projects](../sharepoint/walkthrough-creating-a-custom-deployment-step-for-sharepoint-projects.md) and [Walkthrough: Extending Server Explorer to Display Web Parts](../sharepoint/walkthrough-extending-server-explorer-to-display-web-parts.md).  
 
 ### Understand how SharePoint commands are executed
- Assemblies that define SharePoint commands are loaded in a 64-bit host process named vssphost4.exe. After you call a SharePoint command in a SharePoint tools extension, the command is executed by vssphost4.exe instead of the 32-bit Visual Studio process (devenv.exe). You can control some aspects of how SharePoint commands are executed by setting values in the registry. For more information, see [Debugging Extensions for the SharePoint Tools in Visual Studio](../sharepoint/debugging-extensions-for-the-sharepoint-tools-in-visual-studio.md).  
+ Assemblies that define SharePoint commands are loaded in a 64-bit host process named *vssphost4.exe*. After you call a SharePoint command in a SharePoint tools extension, the command is executed by *vssphost4.exe* instead of the 32-bit Visual Studio process (*devenv.exe*). You can control some aspects of how SharePoint commands are executed by setting values in the registry. For more information, see [Debugging Extensions for the SharePoint Tools in Visual Studio](../sharepoint/debugging-extensions-for-the-sharepoint-tools-in-visual-studio.md).  
 
 ## See also
  [How to: Create a SharePoint Command](../sharepoint/how-to-create-a-sharepoint-command.md)   

docs/sharepoint/converting-between-sharepoint-project-system-types-and-other-visual-studio-project-types.md

@@ -16,7 +16,7 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Converting between SharePoint project system types and other Visual Studio project types
+# Convert between SharePoint project system types and other Visual Studio project types
   In some cases you might have an object in the SharePoint project system and you want to use features of a corresponding object in the Visual Studio automation object model or integration object model, or vice versa. In these cases, you can use the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectService.Convert%2A> method of the SharePoint project service to convert the object to a different object model.  
 
  For example, you might have an <xref:Microsoft.VisualStudio.SharePoint.ISharePointProject> object, but you want to use methods that are only available on an <xref:EnvDTE.Project> or <xref:Microsoft.VisualStudio.Shell.Interop.IVsProject> object. In this case, you can use the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectService.Convert%2A> method to convert the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProject> to an <xref:EnvDTE.Project> or <xref:Microsoft.VisualStudio.Shell.Interop.IVsProject>.  
@@ -39,7 +39,7 @@ ms.workload:
 
  This example requires:  
 
--   An extension of the SharePoint project system that has a reference to the EnvDTE.dll assembly. For more information, see [Extending the SharePoint Project System](../sharepoint/extending-the-sharepoint-project-system.md).  
+-   An extension of the SharePoint project system that has a reference to the *EnvDTE.dll* assembly. For more information, see [Extending the SharePoint Project System](../sharepoint/extending-the-sharepoint-project-system.md).  
 
 -   Code that registers the `projectService_ProjectAdded` method to handle the <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectEvents.ProjectAdded> event of an <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectService> object. For an example, see [How to: Create a SharePoint Project Extension](../sharepoint/how-to-create-a-sharepoint-project-extension.md).  
 

docs/sharepoint/creating-a-business-data-connectivity-model.md

@@ -21,7 +21,7 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Creating a business data connectivity model
+# Create a business data connectivity model
   You can create a Business Data Connectivity (BDC) model or customize an existing BDC model by using Visual Studio. Each SharePoint project can contain only one model. For more information, see [Integrating Business Data into SharePoint](../sharepoint/integrating-business-data-into-sharepoint.md).  
 
 ## Create a new model

docs/sharepoint/creating-an-association-between-entities.md

@@ -25,7 +25,7 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Creating an association between entities
+# Create an association between entities
   You can define relationships between entities in your Business Data Connectivity (BDC) model by creating associations. Visual Studio generates methods that provide consumers of the model with information about each association. These methods can be consumed by SharePoint web parts, lists, or custom applications to display data relationships in a user interface (UI).  
 
 ## Create an association

docs/sharepoint/creating-application-pages-for-sharepoint.md

@@ -22,7 +22,7 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Creating application pages for SharePoint
+# Create application pages for SharePoint
   An *application page* is an ASP.NET Web page that is designed for use in a SharePoint Web site. Application pages are a specialized type of ASP.NET page. The primary difference between an application page and a standard ASP.NET page is that an application page contains content that is merged with a SharePoint master page. A master page enables application pages to share the same appearance and behavior as other pages on a site.  
 
  Visual Studio enables you to design application pages by using a designer. The designer displays a content area for each content placeholder that is defined in a master page. You can design the application page by dragging controls to these content areas.  
@@ -49,7 +49,7 @@ ms.workload:
 
 |File|Description|  
 |----------|-----------------|  
-|ASP.NET page file (.aspx)|Contains XML markup that defines the page.|  
+|ASP.NET page file (*.aspx*)|Contains XML markup that defines the page.|  
 |Application page code file|Contains code behind the application page. Add code that handles events to this file.|  
 |Application page designer code file|Contains code that is generated by the designer. Do not directly edit this file.|