Update continuous-integration-and-continuous-delivery.md (#2798)

* Update continuous-integration-and-continuous-delivery.md

Updated reference of VSO in this with VSTS and also modified the URL

* Update continuous-integration-and-continuous-delivery.md

Applied suggestions 
@GuardRex and also fixed one more instance of VSO with VSTS and link.

* Update continuous-integration-and-continuous-delivery.md

Added a blank line after the paragraph. I left "Summary" text alone, seems it was hanging with previous sentence and made no sense.

aspnet/aspnet/overview/developing-apps-with-windows-azure/building-real-world-cloud-apps-with-windows-azure/continuous-integration-and-continuous-delivery.md

@@ -37,9 +37,9 @@ The following diagram from [a Microsoft Patterns and Practices e-book about cont
 
 Automating these processes in Azure is easy. Because you're running everything in the cloud, you don't have to buy or manage servers for your builds or your test environments. And you don't have to wait for a server to be available to do your testing on. With every build that you do, you could spin up a test environment in Azure using your automation script, run acceptance tests or more in-depth tests against it, and then when you're done just tear it down. And if you only run that server for 2 hours or 8 hours or a day, the amount of money that you have to pay for it is minimal, because you're only paying for the time that a machine is actually running. For example, the environment required for the Fix it application basically costs about 1 cent per hour if you go one tier up from the free level. Over the course of a month, if you only ran the environment an hour at a time, your testing environment would probably cost less than a latte that you buy at Starbucks.
 
-## Visual Studio Online
+## Visual Studio Team Services (VSTS)
 
-One of the things we're working on with Visual Studio Online (VSO), formerly known as Team Foundation Service, is to make it work really well with continuous integration and delivery. Here are some key features of VSO:
+VSTS provides a number of features to assist you with application development from planning to deployment.
 
 - It supports both Git (distributed) and TFVC (centralized) source control.
 - It offers an elastic build service, which means it dynamically creates build servers when they're needed and takes them down when they're done. You can automatically kick off a build when someone checks in source code changes, and you don't have to have allocate and pay for your own build servers that lie idle most of the time. The build service is free as long as you don't exceed a certain number of builds. If you expect to do a high volume of builds, you can pay a little extra for reserved build servers.
@@ -48,9 +48,12 @@ One of the things we're working on with Visual Studio Online (VSO), formerly kno
 - It supports team room collaboration, which facilitates real-time communication and collaboration for small agile teams.
 - It supports agile project management.
 
-For more information about the continuous integration and delivery features of VSO, see [Visual Studio Lab Management](https://www.visualstudio.com/en-us/explore/lab-management-vs.aspx) and [Visual Studio Release Management](https://www.visualstudio.com/en-us/explore/release-management-vs.aspx). An application monitoring feature, [Application Insights for Visual Studio Online](https://msdn.microsoft.com/en-us/library/dn481095.aspx), is in preview (available to try but not released for production use yet).
 
-If you're looking for a turn-key project management, team collaboration, and source control solution, check out VSO. The service is free for up to 5 users, and you can sign up for it at [https://www.visualstudio.com](https://www.visualstudio.com/). Summary
+For more information on the continuous integration and delivery features of VSTS, see [Visual Studio Team Services](https://www.visualstudio.com/team-services/).
+
+If you're looking for a turn-key project management, team collaboration, and source control solution, check out VSTS. The service is free for up to 5 users, and you can sign up for it at [Visual Studio Team Services](https://www.visualstudio.com/team-services/).
+
+Summary
 
 The first three cloud development patterns have been about how to implement a repeatable, reliable, predictable development process with low cycle time. In the [next chapter](web-development-best-practices.md) we start to look at architectural and coding patterns.
 
@@ -69,4 +72,4 @@ See also the following resources:
 
 >[!div class="step-by-step"]
 [Previous](source-control.md)
-[Next](web-development-best-practices.md)
+[Next](web-development-best-practices.md)