Merge pull request #2138 from iRaindrop/vbruham_sharepoint_e

VS SharePoint other content fixes: A - C

Author: TrishaMc

docs/sharepoint/additional-information-for-sharepoint-errors.md

@@ -22,10 +22,10 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Additional Information for SharePoint Errors
+# Additional information for SharePoint errors
   You can find assistance in troubleshooting [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint tools errors and warnings in troubleshooting topics and the Microsoft Developer Network (MSDN) public forums.  
 
-## Troubleshooting Errors and Issues  
+## Troubleshoot errors and issues
  For assistance with some common errors and other issues in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint tools, see the following topics:  
 
 -   [Troubleshooting SharePoint Solutions](../sharepoint/troubleshooting-sharepoint-solutions.md)  
@@ -34,7 +34,7 @@ ms.workload:
 
 -   [Troubleshooting SharePoint Packaging and Deployment](../sharepoint/troubleshooting-sharepoint-packaging-and-deployment.md)  
 
-## Other Resources  
+## Other resources
  The following table lists the [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint tools forums and other resources available on MSDN.  
 
 |Term|Definition|  
@@ -45,7 +45,7 @@ ms.workload:
 
  If you still cannot find  the answers that you need, you can access online support options, such as contacting Microsoft Product Support Services or searching KnowledgeBase articles. For more information, see the [Microsoft Help and Support](http://go.microsoft.com/fwlink/?LinkID=155371) page.  
 
-## See Also  
+## See also
  [Building and Debugging SharePoint Solutions](../sharepoint/building-and-debugging-sharepoint-solutions.md)  
 
-  
+ 

docs/sharepoint/api-reference-sharepoint-tools-extensibility.md

@@ -16,10 +16,10 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# API Reference (SharePoint Tools Extensibility)
+# API reference (SharePoint tools extensibility)
   This section contains API reference documentation for extending the SharePoint tools in Visual Studio.  
 
-## In This Section  
+## In this section
  <xref:Microsoft.VisualStudio.SharePoint>  
  Contains types that you use to extend the SharePoint project system. For example, you can extend the built-in SharePoint projects and project items, or you can create your own project items.  
 
@@ -53,12 +53,11 @@ ms.workload:
  <xref:Microsoft.VisualStudio.SharePoint.Validation>  
  Contains types that you use to customize the feature and package validation behavior for a SharePoint project.  
 
-## See Also  
+## See also
  [Reference &#40;SharePoint Tools Extensibility&#41;](../sharepoint/reference-sharepoint-tools-extensibility.md)   
  [Overview of the Programming Model of SharePoint Tools Extensions](../sharepoint/overview-of-the-programming-model-of-sharepoint-tools-extensions.md)   
  [Extending the SharePoint Project System](../sharepoint/extending-the-sharepoint-project-system.md)   
  [Extending the SharePoint Connections Node in Server Explorer](../sharepoint/extending-the-sharepoint-connections-node-in-server-explorer.md)   
  [Extending SharePoint Packaging and Deployment](../sharepoint/extending-sharepoint-packaging-and-deployment.md)   
  [Calling into the SharePoint Object Models](../sharepoint/calling-into-the-sharepoint-object-models.md)  
 
-  

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
+# Associating 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.  
@@ -29,7 +29,7 @@ ms.workload:
 
  In extensions of the SharePoint project system, you can also save string data that persists after an extension is unloaded. For more information, see [Saving Data in Extensions of the SharePoint Project System](../sharepoint/saving-data-in-extensions-of-the-sharepoint-project-system.md).  
 
-## Objects that Can Contain Custom Data  
+## Objects that can contain custom data
  You can add custom data to any object in the SharePoint tools object model that implements the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject> interface. This interface defines just one property, <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A>, which is a collection of custom data objects. The following types implement <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject>:  
 
 -   <xref:Microsoft.VisualStudio.SharePoint.IMappedFolder>  
@@ -62,7 +62,7 @@ ms.workload:
 
 -   <xref:Microsoft.VisualStudio.SharePoint.Explorer.IExplorerNodeTypeDefinition>  
 
-## Adding and Retrieving Custom Data  
+## Add and retrieve custom data
  To add custom data to an object in a SharePoint tools extension, get the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property of the object you want to add the data to, and then use the <xref:Microsoft.VisualStudio.SharePoint.IAnnotationDictionary.Add%2A> method to add the data to the object.  
 
  To retrieve custom data from an object in a SharePoint tools extension, get the <xref:Microsoft.VisualStudio.SharePoint.IAnnotatedObject.Annotations%2A> property of the object and then use one of the following methods:  
@@ -76,10 +76,10 @@ ms.workload:
  [!code-vb[SPExtensibility.ProjectItemExtension.MenuAndProperty#13](../sharepoint/codesnippet/VisualBasic/projectitemmenuandproperty/extension/projectitemtypeproperty.vb#13)]
  [!code-csharp[SPExtensibility.ProjectItemExtension.MenuAndProperty#13](../sharepoint/codesnippet/CSharp/projectitemmenuandproperty/extension/projectitemtypeproperty.cs#13)]  
 
-## See Also  
+## See also
  [Programming Concepts and Features for SharePoint Tools Extensions](../sharepoint/programming-concepts-and-features-for-sharepoint-tools-extensions.md)   
  [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   
-  
+ 

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

@@ -29,12 +29,12 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# BDC Model Design Tools Overview
+# BDC model design tools overview
   You can design a Business Data Connectivity (BDC) model by using the BDC Designer, the **BDC Method Details** window, and the **BDC Explorer**.  
 
  The **BDC Explorer** enables you to browse the model, search the model, and define type descriptors.  
 
-## BDC Designer  
+## BDC Designer
  The BDC Designer enables you to define the entities in your model and to visually arrange their relationships with one another. Use the BDC Designer to accomplish the following tasks:  
 
 -   Add entities to the model.  
@@ -45,7 +45,7 @@ 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.  
@@ -56,23 +56,23 @@ ms.workload:
 
  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  
+## 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.  
 
  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**.  
 
 > [!NOTE]  
 >  The **BDC Explorer** does not display identifiers, custom properties, localized strings, association groups, actions, filter descriptors, action control lists, and the default parameter values.  
   
-### Defining Type Descriptors  
+### Define type descriptors
  Use the **BDC Explorer** to define type descriptors. The BDC Explorer enables you to define a type descriptor one time and then reuse that type descriptor elsewhere in your model. To accomplish this, copy a type descriptor and paste it onto any other parameter or type descriptor.  
 
 > [!NOTE]  
 >  Changes to an original type descriptor do not affect the copies of that type descriptor.  
   
  For more information, see [How to: Define the Type Descriptor of a Parameter](../sharepoint/how-to-define-the-type-descriptor-of-a-parameter.md).  
 
-## See Also  
+## See also
  [How to: Create a BDC Model](../sharepoint/how-to-create-a-bdc-model.md)   
  [How to: Add an Entity to a Model](../sharepoint/how-to-add-an-entity-to-a-model.md)   
  [How to: Add a Finder Method](../sharepoint/how-to-add-a-finder-method.md)   
@@ -86,4 +86,4 @@ ms.workload:
  [Creating a Business Data Connectivity Model](../sharepoint/creating-a-business-data-connectivity-model.md)   
  [Designing a Business Data Connectivity Model](../sharepoint/designing-a-business-data-connectivity-model.md)  
 
-  
+ 

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

@@ -22,17 +22,17 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Browsing SharePoint Connections Using Server Explorer
+# 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.  
 
 > [!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.  
   
-## Server Explorer Nodes  
+## Server Explorer nodes
  Every component of a SharePoint site is represented by a node in the **Server Explorer** tree view under **SharePoint Connections**. For example, default SharePoint sites include a content type called Discussion, which represents a discussion type that displays in the **Discussions** page of the SharePoint site. The Discussion content type contains several fields. To view these fields in **Server Explorer**, expand the **ContentTypes** node, and then the **Discussion** node. Under it are several field nodes, such as Body, Discussion Subject, and Title.  
 
-## Node Shortcut Menu Commands  
- Each node has a shortcut menu that you access by right-clicking the node or choosing it and then choosing the Shift+F10 keys. Node commands may include the following:  
+## Node shortcut menu commands
+ Each node has a shortcut menu that you access by right-clicking the node or choosing it and then choosing the **Shift**+**F10** keys. Node commands may include the following:  
 
 |Command Name|Description|  
 |------------------|-----------------|  
@@ -42,13 +42,13 @@ ms.workload:
 |Add Connection|Allows you to specify a SharePoint site that you want to browse. Available on the **SharePoint Connections** node and sub-site nodes.|  
 |View in Browser|Displays the selected list in the Web browser. This command is available on some lists under the **Lists** node which is contained in **Lists and Libraries**.|  
 
-## Related Topics  
+## Related topics
 
 |Title|Description|  
 |-----------|-----------------|  
 |[How to: Add or Remove SharePoint Connections](../sharepoint/how-to-add-or-remove-sharepoint-connections.md)|Describes the steps that are required for adding a new SharePoint site to the **SharePoint Connections** node in **Server Explorer**.|  
 
-## See Also  
+## See also
  [Developing SharePoint Solutions](../sharepoint/developing-sharepoint-solutions.md)  
 
-  
+ 

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

@@ -19,10 +19,10 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Building and Debugging SharePoint Solutions
+# Building and debugging 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  
+## 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.  
 
 |Build item|Output folder|  
@@ -32,24 +32,24 @@ ms.workload:
 |Build intermediate files.|*ProjectName*\obj\debug or *ProjectName*\obj\release|  
 |Package intermediate files.|*ProjectName*\pkgobj\debug or *ProjectName*\pkgobj\release|  
 
-## Building SharePoint Solutions  
+## 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).  
 
-## Debugging and Testing SharePoint Solutions  
+## 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).  
 
-## Debugging and Verifying SharePoint Solutions by Using ALM Features  
+## 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  
+## 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  
  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  
+## See also
  [Developing SharePoint Solutions](../sharepoint/developing-sharepoint-solutions.md)   
  [Browsing SharePoint Connections Using Server Explorer](../sharepoint/browsing-sharepoint-connections-using-server-explorer.md)   
  [Packaging and Deploying SharePoint Solutions](../sharepoint/packaging-and-deploying-sharepoint-solutions.md)  
 
-  
+