removed 2013 version references

Author: davidchesnut

docs/general-development/access-sharepoint-from-mobile-and-native-device-apps.md

@@ -27,13 +27,13 @@ Non-Microsoft device apps, including mobile apps, **use SharePoint REST/OData AP
 
 
 
-- See  [Get to know the SharePoint 2013 REST service](http://msdn.microsoft.com/library/2de035a0-ac75-43bd-9665-5c5a59c4c590%28Office.15%29.aspx) for the basics.
+- See  [Get to know the SharePoint REST service](http://msdn.microsoft.com/library/2de035a0-ac75-43bd-9665-5c5a59c4c590%28Office.15%29.aspx) for the basics.
 
 
-- See  [REST API reference for SharePoint 2013](http://msdn.microsoft.com/library/3514e753-19f9-4b41-a1ae-f35c5ffc17d2%28Office.15%29.aspx) for a complete reference.
+- See  [REST API reference for SharePoint](http://msdn.microsoft.com/library/3514e753-19f9-4b41-a1ae-f35c5ffc17d2%28Office.15%29.aspx) for a complete reference.
 
 
-For more information about how to create mobile apps for any platform, see  [Build mobile apps for other platforms using SharePoint 2013](build-mobile-apps-for-other-platforms-using-sharepoint.md).
+For more information about how to create mobile apps for any platform, see  [Build mobile apps for other platforms using SharePoint](build-mobile-apps-for-other-platforms-using-sharepoint.md).
 
 
 
@@ -56,7 +56,7 @@ Windows Phone apps can use one of the following:
 
 
 
-For more about creating Windows Phone apps that access SharePoint, see  [Build Windows Phone apps that access SharePoint 2013](build-windows-phone-apps-that-access-sharepoint.md).
+For more about creating Windows Phone apps that access SharePoint, see  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md).
 
 
 

docs/general-development/accessibility-in-sharepoint.md

@@ -1,26 +1,26 @@
 ---
-title: Accessibility in SharePoint 2013
+title: Accessibility in SharePoint
 ms.prod: SHAREPOINT
 ms.assetid: c9106d47-c523-49c1-b9f1-cdd7420abd5e
 ---
 
 
-# Accessibility in SharePoint 2013
-Learn about the features, products, and services that make SharePoint 2013 accessible for people with disabilities, and find developer resources that can help you design and build apps and websites that support key accessibility scenarios.
+# Accessibility in SharePoint
+Learn about the features, products, and services that make SharePoint accessible for people with disabilities, and find developer resources that can help you design and build apps and websites that support key accessibility scenarios.
 Accessible technology enables users to interact with computers and applications in different ways to help meet their visual, hearing, speech, dexterity, and cognitive needs. Accessible technology includes features, options, and utilities that are built into the Windows operating system and other Microsoft products, in addition to third-party hardware and software add-ons (also known asassistive technology).
 
 
 
 
 Microsoft strives to build products that are accessible to everyone. For information about these efforts, see the  [Microsoft Accessibility](http://www.microsoft.com/enable/default.aspx) site.
-## Accessibility features in SharePoint 2013
+## Accessibility features in SharePoint
 <a name="bkmk_AccessibilitySP2013"> </a>
 
-SharePoint 2013 supports the accessibility features of common web browsers to enable you to access and manage SharePoint sites. Web browsers provide support for keyboard interactions so that users who don't use a mouse can use a keyboard to navigate the user interface and perform actions in SharePoint 2013.
+SharePoint supports the accessibility features of common web browsers to enable you to access and manage SharePoint sites. Web browsers provide support for keyboard interactions so that users who don't use a mouse can use a keyboard to navigate the user interface and perform actions in SharePoint.
 
 
 
-For more information about accessibility features in SharePoint 2013, see the following articles:
+For more information about accessibility features in SharePoint, see the following articles:
 
 
 
@@ -31,7 +31,7 @@ For more information about accessibility features in SharePoint 2013, see the fo
 -  [Keyboard shortcuts for SharePoint products](http://office.microsoft.com/en-us/sharepoint-foundation-help/keyboard-shortcuts-for-sharepoint-products-HA102772894.aspx?CTT=5&amp;origin=HA102772892)
 
 
-Users who have site administrator responsibilities typically use the SharePoint Central Administration site to manage deployments. A mouse and keyboard are the typical devices that you use to interact with Central Administration. For more information about accessibility for administrators and other IT pros in SharePoint, see  [Accessibility for SharePoint 2013](http://technet.microsoft.com/en-us/library/jj219681.aspx).
+Users who have site administrator responsibilities typically use the SharePoint Central Administration site to manage deployments. A mouse and keyboard are the typical devices that you use to interact with Central Administration. For more information about accessibility for administrators and other IT pros in SharePoint, see  [Accessibility for SharePoint](http://technet.microsoft.com/en-us/library/jj219681.aspx).
 
 
 
@@ -43,7 +43,7 @@ Users who have devices that support touch can use gestures to complete operation
 ## Developing accessible apps and websites
 <a name="bkmk_DevAccessibleApps"> </a>
 
-As you design and build apps and solutions for SharePoint 2013, you should implement markup and code to support key accessibility scenarios, including keyboard accessibility, proper text contrast, and screen reading.
+As you design and build apps and solutions for SharePoint, you should implement markup and code to support key accessibility scenarios, including keyboard accessibility, proper text contrast, and screen reading.
 
 
 
@@ -80,7 +80,7 @@ If you build solutions and apps for SharePoint in Visual Studio, you will find t
 ## Accessibility in web browsers
 <a name="bkmk_AccessBrowsers"> </a>
 
-SharePoint administrators and users depend on the accessibility features that web browsers provide. SharePoint 2013 supports the accessibility features of typical browsers. Table 1 contains links to resources that describe the accessibility features that typical browsers support.
+SharePoint administrators and users depend on the accessibility features that web browsers provide. SharePoint supports the accessibility features of typical browsers. Table 1 contains links to resources that describe the accessibility features that typical browsers support.
 
 
 
@@ -121,7 +121,7 @@ SharePoint administrators and users depend on the accessibility features that we
 -  [Accessibility in Microsoft Products](http://www.microsoft.com/enable/products/default.aspx)
 
 
--  [Accessibility for SharePoint 2013](http://technet.microsoft.com/en-us/library/jj219681.aspx)
+-  [Accessibility for SharePoint](http://technet.microsoft.com/en-us/library/jj219681.aspx)
 
 
 

docs/general-development/accessing-a-schema.md

@@ -14,7 +14,7 @@ This topic shows one example of how you can access and look at a schema for the
 
 
 > **Note:**
-> The Excel Services REST API applies to SharePoint 2013 and SharePoint 2016 on-premises. For Office 365 Education, Business, and Enterprise accounts, use the Excel REST APIs that are part of the  [Microsoft Graph](http://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/excel
+> The Excel Services REST API applies to SharePoint and SharePoint 2016 on-premises. For Office 365 Education, Business, and Enterprise accounts, use the Excel REST APIs that are part of the  [Microsoft Graph](http://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/excel
 ) endpoint.
 
 

docs/general-development/add-in-scoped-external-content-types-in-sharepoint.md

@@ -1,25 +1,25 @@
 ---
-title: Add-in-scoped external content types in SharePoint 2013
+title: Add-in-scoped external content types in SharePoint
 ms.prod: SHAREPOINT
 ms.assetid: a34cbbba-dc38-4d3d-b796-d54b5848bdfb
 ---
 
 
-# Add-in-scoped external content types in SharePoint 2013
-Learn about external content types that are installed or scoped at the add-in level in SharePoint 2013 and enable you to create data-rich SharePoint Add-ins using external data sources.
-## Overview of add-in-scoped external content types in SharePoint 2013
+# Add-in-scoped external content types in SharePoint
+Learn about external content types that are installed or scoped at the add-in level in SharePoint and enable you to create data-rich SharePoint Add-ins using external data sources.
+## Overview of add-in-scoped external content types in SharePoint
 <a name="Appscopedect_overview"> </a>
 
 In SharePoint 2010, you can install and use external content types only at the farm level. This often causes problems for developers because even for simple applications, an administrator had to be involved because of the access rights that are needed to install at the farm level.
 
 
 
-In SharePoint 2013, applications are basically isolated into more autonomous units called add-ins. Add-ins contain all the resources they need to run. This approach enables a running application to be insulated from other applications. The benefits of this architecture are as follows:
+In SharePoint, applications are basically isolated into more autonomous units called add-ins. Add-ins contain all the resources they need to run. This approach enables a running application to be insulated from other applications. The benefits of this architecture are as follows:
 
 
 
 
-- You can create add-ins that are aligned with the new application model of SharePoint 2013.
+- You can create add-ins that are aligned with the new application model of SharePoint.
 
 
 - You can create add-ins that access external data from SAP, Netflix, and proprietary and other types of data without involving the tenant administrator.
@@ -47,7 +47,7 @@ The following are the requirements for developing external content types that ar
 - Office Developer Tools for Visual Studio 2012
 
 
-- SharePoint 2013
+- SharePoint
 
 
 For information about setting up your SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
@@ -68,7 +68,7 @@ Table 1 contains some core concepts that you should be familiar with when workin
 |**Article**|**Description**|
 |:-----|:-----|
 | [External content types in SharePoint](external-content-types-in-sharepoint.md) <br/> |Learn how to create BCS external content types.  <br/> |
-| [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx) <br/> |Learn about the new add-in model in SharePoint 2013 that enables you to create add-ins, which are small, easy-to-use solutions for end users.  <br/> |
+| [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx) <br/> |Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.  <br/> |
 | [Get started creating SharePoint-hosted SharePoint Add-ins](http://msdn.microsoft.com/library/1b992485-6efe-4ea4-a18c-221689b0b66f%28Office.15%29.aspx) <br/> |Learn how to create a basic SharePoint-hosted add-in by using the Office Developer Tools for Visual Studio 2012.  <br/> |
 
 
@@ -94,11 +94,11 @@ The concept of a file-based metadata catalog was introduced in SharePoint 2010.
 
 
 
-In SharePoint 2013, **SPListDataSource** has been modified to add a property that indicates the scope of the application.
+In SharePoint, **SPListDataSource** has been modified to add a property that indicates the scope of the application.
 
 
 
-This class serves as the bridge between **SPList** and an external list. Use the associated **SPList** to retrieve entity fields and data. Retrieve an instance of **SPListDataSource** from the **HasExternalDataSource** property. When **HasExternalDataSource** is not null, the **SPList** object's data is external to SharePoint 2013.
+This class serves as the bridge between **SPList** and an external list. Use the associated **SPList** to retrieve entity fields and data. Retrieve an instance of **SPListDataSource** from the **HasExternalDataSource** property. When **HasExternalDataSource** is not null, the **SPList** object's data is external to SharePoint.
 
 
 
@@ -228,10 +228,10 @@ The following example shows how to set security credentials for an external syst
 -  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint.md)
 
 
--  [What's new in Business Connectivity Services in SharePoint 2013](what-s-new-in-business-connectivity-services-in-sharepoint.md)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
 
 
--  [Get started with Business Connectivity Services in SharePoint 2013](get-started-with-business-connectivity-services-in-sharepoint.md)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
 
 
 

docs/general-development/add-sharepoint-capabilities.md

@@ -6,8 +6,8 @@ ms.assetid: 11ecb65e-6dc5-4cf1-80ca-3c16418697b6
 
 
 # Add SharePoint capabilities
-Find overview and how-to information about adding SharePoint 2013 features and capabilities to custom apps.
-## What are SharePoint capabilities in SharePoint 2013?
+Find overview and how-to information about adding SharePoint features and capabilities to custom apps.
+## What are SharePoint capabilities in SharePoint?
 <a name="bkmk_whatIs"> </a>
 
 SharePoint capabilities represent the features that you work with on SharePoint sites, such as workflows, social feeds, and search. By adding SharePoint capabilities to your app, you can help users to do things better and more quickly.
@@ -27,7 +27,7 @@ The following table shows SharePoint capabilities that you can add to your app,
 
 
 
-**Table 1. SharePoint capabilities that you can add to apps in SharePoint 2013**
+**Table 1. SharePoint capabilities that you can add to apps in SharePoint**
 
 
 |**Capability**|**Article title**|
@@ -36,7 +36,7 @@ The following table shows SharePoint capabilities that you can add to your app,
 |Communicate and collaborate with people and track content  <br/> | [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md) <br/> |
 |Add ___location and mapping features  <br/> | [Integrating ___location and map functionality in SharePoint](integrating-___location-and-map-functionality-in-sharepoint.md) <br/> |
 |Make search results more relevant  <br/> | [Search in SharePoint](search-in-sharepoint.md) <br/> |
-|Access data from external data systems  <br/> | [Business Connectivity Services in SharePoint 2013](business-connectivity-services-in-sharepoint.md) <br/> |
+|Access data from external data systems  <br/> | [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md) <br/> |
 |Work with data, convert file formats, and translate sites  <br/> | [Office and SharePoint application services](office-and-sharepoint-application-services.md) <br/> |
 |Work with user access, roles, rights, and claims.  <br/> | [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md) <br/> |
 |Discover content in electronic format for legal purposes  <br/> | [eDiscovery in SharePoint](ediscovery-in-sharepoint.md) <br/> |

docs/general-development/advanced-scenarios-and-additional-samples.md

@@ -14,7 +14,7 @@ This topic describes some advanced REST scenarios and additional samples. It pro
 
 
 > **Note:**
-> The Excel Services REST API applies to SharePoint 2013 and SharePoint 2016 on-premises. For Office 365 Education, Business, and Enterprise accounts, use the Excel REST APIs that are part of the  [Microsoft Graph](http://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/excel
+> The Excel Services REST API applies to SharePoint and SharePoint 2016 on-premises. For Office 365 Education, Business, and Enterprise accounts, use the Excel REST APIs that are part of the  [Microsoft Graph](http://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/excel
 ) endpoint.
 
 

docs/general-development/architecture-of-the-windows-phone-sharepoint-list-application-template.md

@@ -131,7 +131,7 @@ The **EditForm** class (which represents the View component from the MVVM patter
 
 
 
-Software designs based on the MVVM pattern often confine business logic and validation routines to the Model component of the pattern. In projects based on the Windows Phone SharePoint List Application template, however, some operations that are typically considered part of the Model component have been implemented in the ViewModel component to make it more convenient for developers to extend the projects, at the cost of slightly blurring the conceptual distinction between the data layer (Model) and the presentation layer (ViewModel). For example, the ViewModel classes for editing and creating list items (that is, the **EditItemViewModel** and **NewItemViewModel** classes) expose a **Validate** method that developers can override to implement validation of data entered by users. (For information on implementing data validation with these ViewModels, see [How to: Implement business logic and data validation in a Windows Phone app for SharePoint 2013](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md).)
+Software designs based on the MVVM pattern often confine business logic and validation routines to the Model component of the pattern. In projects based on the Windows Phone SharePoint List Application template, however, some operations that are typically considered part of the Model component have been implemented in the ViewModel component to make it more convenient for developers to extend the projects, at the cost of slightly blurring the conceptual distinction between the data layer (Model) and the presentation layer (ViewModel). For example, the ViewModel classes for editing and creating list items (that is, the **EditItemViewModel** and **NewItemViewModel** classes) expose a **Validate** method that developers can override to implement validation of data entered by users. (For information on implementing data validation with these ViewModels, see [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md).)
 
 
 
@@ -151,7 +151,7 @@ The App.xaml file and its associated code-behind file, App.xaml.cs, are standard
 
 
 
-For information about the kinds of modifications you might make to the App.xaml.cs file in your projects, see  [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md) on implementing event handlers in the App.xaml.cs file to preserve application state information, and [How to: Use multiple SharePoint 2013 lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md) on instantiating and configuring additional **ListDataProvider** objects in App.xaml.cs.
+For information about the kinds of modifications you might make to the App.xaml.cs file in your projects, see  [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md) on implementing event handlers in the App.xaml.cs file to preserve application state information, and [How to: Use multiple SharePoint lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md) on instantiating and configuring additional **ListDataProvider** objects in App.xaml.cs.