M3709: Misspelled word: "Servides"

@kraigb, 
It seems that there is a typo mistake in "Servides." Could you help to review this and merge?
Many thanks in advance.

Author: carolinacmoravia

docs/porting/port-migrate-and-upgrade-visual-studio-projects.md

@@ -71,11 +71,11 @@ The following list describes support in Visual Studio 2017 for projects that wer
 | SharePoint 2010 | When a SharePoint solution project is opened with Visual Studio 2017, it will be upgraded to either SharePoint 2013 or SharePoint 2016. The “.NET Desktop Development” workload must be installed in Visual Studio 2017 for the upgrade.<br/><br/>For more information about how to upgrade SharePoint projects, see [Upgrade to SharePoint 2013](https://technet.microsoft.com/en-us/library/cc303420.aspx), [Update Workflow in SharePoint Server 2013](https://technet.microsoft.com/en-us/library/dn133867.aspx), and [Create the SharePoint Server 2016 farm for a database attach upgrade](https://technet.microsoft.com/en-us/library/cc263026(v=office.16).aspx). |
 | SharePoint 2016 | SharePoint Add-In projects created in Office Developer Tools Preview 2 cannot be opened in Visual Studio 2017. To work around this you will need to update the `MinimumVisualStudioVersion` to 12.0 and `MinimumOfficeToolsVersion` to 12.2 in the `.csproj` or `.vbproj` file. |
 | Silverlight | Silverlight projects not supported in Visual Studio 2017. To maintain Silverlight applications, continue to use Visual Studio 2015. |
-| SQL Server Reporting Services, SQL Server Analysis Services (SSDT, SSAS, MSAS, SSDT) | Support for these project types are provided for through two extensions in the Visual Studio Gallery:  [Microsoft Analysis Servides Modeling Projects](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects) and [Microsoft Report Projects for Visual Studio](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio). |
+| SQL Server Reporting Services, SQL Server Analysis Services (SSDT, SSAS, MSAS, SSDT) | Support for these project types are provided for through two extensions in the Visual Studio Gallery:  [Microsoft Analysis Services Modeling Projects](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects) and [Microsoft Report Projects for Visual Studio](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio). |
 | Visual C++ | You can use Visual Studio 2017 to open solutions and projects that were created in Visual Studio 2015 as-is, but projects that were created in older versions of Visual Studio may require upgrading the project or retargeting to a more recent toolset to build with Visual Studio 2017. For more information, see [How to: Upgrade Visual C++ Projects to Visual Studio 2015](https://msdn.microsoft.com/en-us/library/hh690665.aspx) and [Visual C++ Porting and Upgrading Guide](https://msdn.microsoft.com/en-us/library/dn986839.aspx). |
 | Visual Studio Extensibility/VSIX | Projects with MinimumVersion 14.0 or less will be updated to declare MinimumVersion 15.0, which prevents the project from being opened in earlier versions of Visual Studio. To allow a project to open in earlier versions, set MinimumVersion to `$(VisualStudioVersion)`. See also [How to: Migrate Extensibility Projects to Visual Studio 2017](../extensibility/how-to-migrate-extensibility-projects-to-visual-studio-2017.md). |
 | Visual Studio Lab Management | You can use Microsoft Test Manager or Visual Studio 2010 SP1 and later to open environments created in any of these versions. However, for Visual Studio 2010 SP1 the version of Microsoft Test Manager must match the version of Team Foundation Server before you can create environments. |
 | Visual Studio Tools for Apache Cordova |This project can be opened in Visual Studio 2017, but it is not backwards compatible. Upon opening a project from Visual Studio 2015, you will be prompted to allow modifications to your project. This upgrades the project to use toolsets instead of a `taco.json` file to manage the versioning of the Cordova library, its platforms and plugins, as well as its node/npm dependencies. See the [migration guide](http://taco.visualstudio.com/docs/vs-taco-2017-migration/) for more information. |
 | Windows Communication Foundation, Windows Workflow Foundation | You can open this project in Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012 |
 | Windows Presentation Foundation | You can open this project in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. |
-| Windows Store/Phone apps | Projects for Windows Store 8.1 and 8.0, and Windows Phone 8.1 and 8.0 are not supported in Visual Studio 2017. To maintain these apps, continue to use Visual Studio 2015. To maintain Windows Phone 7.x projects, use Visual Studio 2012. |
+| Windows Store/Phone apps | Projects for Windows Store 8.1 and 8.0, and Windows Phone 8.1 and 8.0 are not supported in Visual Studio 2017. To maintain these apps, continue to use Visual Studio 2015. To maintain Windows Phone 7.x projects, use Visual Studio 2012. |