Merge branch 'master' of https://github.com/Azure/azure-api-management-devops-example into lucashh-templateupdates

Author: lucashuet93

README.md

@@ -28,7 +28,7 @@ The proposed approach is illustrated in the below picture.
 
 In this example, there are two deployment environments: Development and Production, each has its own API Management instance. API developers have access to the Development instance and can use it for developing and testing their APIs. The Production instance is managed by a designated team called the API publishers.
 
-The key in this proposed approach is to keep all API Management configurations in Azure [Resource Manager templates](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-authoring-templates). These templates should be kept in a source control system. We will use GIT throughout this example. As illustrated in the picture, there is a Publisher repository that contains all configurations of the Production API Management instance in a collection of tempaltes.
+The key in this proposed approach is to keep all API Management configurations in Azure [Resource Manager templates](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-authoring-templates). These templates should be kept in a source control system. We will use GIT throughout this example. As illustrated in the picture, there is a Publisher repository that contains all configurations of the Production API Management instance in a collection of templates.
 
 * **Service template**: contains all the service-level configurations of the API Management instance (e.g., pricing tier and custom domains). 
 * **Shared templates**: contain shared resources throughout an API Management instance (e.g., groups, products, loggers).