Merge pull request #17 from irajbalakrish/master

Update README.md with references to Azure Devops instead of VSTS

Author: priyaananthasankar

README.md

@@ -8,7 +8,7 @@ author: nzthiago
 
 In this sample, we have built four microservices that use an [Event Grid](https://docs.microsoft.com/en-us/azure/event-grid/overview) custom topic for inter-service eventing, and a front-end Angular.js app that uses [SignalR](https://www.asp.net/signalr) to forward Event Grid events to the user interface in real time.
 
-The application itself is a personal knowledge management system, and it allows users to upload text, images, and audio and for these to be placed into categories. Each of these types of data is managed by a dedicated microservice built on Azure serverless technologies including [Azure Functions](https://docs.microsoft.com/en-us/azure/azure-functions/functions-overview) and [Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/welcome). The web front-end communicates with the microservices through a SignalR-to-Event Grid bridge, allowing for real-time reactive UI updates based on the microservice updates. Each microservice is built and deployed independently using VSTS’s build and release management system, and use a variety of Azure-native data storage technologies.
+The application itself is a personal knowledge management system, and it allows users to upload text, images, and audio and for these to be placed into categories. Each of these types of data is managed by a dedicated microservice built on Azure serverless technologies including [Azure Functions](https://docs.microsoft.com/en-us/azure/azure-functions/functions-overview) and [Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/welcome). The web front-end communicates with the microservices through a SignalR-to-Event Grid bridge, allowing for real-time reactive UI updates based on the microservice updates. Each microservice is built and deployed independently using Azure DevOps’s build and release management system, and use a variety of Azure-native data storage technologies.
 
 The sample can be built and run by following the instructions in the [`setup.md` file](setup.md).
 
@@ -52,7 +52,7 @@ The sample also contains an Angular.js application that is bundled within an ASP
 
 ![Architecture Diagram](/_docs/architecture.png)
 
-Each microservice and other components within the sample are designed to be built and deployed in a fully automated manner. We used VSTS, although any other build and release management systems could also be used. We used [VSTS's Build YAML](https://docs.microsoft.com/en-us/vsts/build-release/actions/build-yaml?view=vsts) feature to declaratively specify our build process and used [VSTS Release Management](https://docs.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/what-is-release-management?view=vsts) to define our release process and publish the built components to Azure. Please see the `setup.md` file for more information on how to build and release the sample components for yourself.
+Each microservice and other components within the sample are designed to be built and deployed in a fully automated manner. We used Azure DevOps, although any other build and release management systems could also be used. We used [Azure DevOps's Build YAML](https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-yaml?view=vsts) feature to declaratively specify our build process and used [Azure DevOps Release Management](https://docs.microsoft.com/en-us/azure/devops/pipelines/release/what-is-release-management?view=vsts) to define our release process and publish the built components to Azure. Please see the `setup.md` file for more information on how to build and release the sample components for yourself.
 
 
 # Components