Merge branch 'master' of https://github.com/Azure/azure-content-pr

articles/api-management/api-management-key-concepts.md

@@ -13,7 +13,7 @@
 	ms.tgt_pltfrm="na" 
 	ms.devlang="na" 
 	ms.topic="article" 
-	ms.date="09/15/2015" 
+	ms.date="11/05/2015" 
 	ms.author="sdanie"/>
 
 #What is API Management?
@@ -78,7 +78,7 @@ For more information, see [How to create or invite developers][] and [How to ass
 
 Policies are a powerful capability of API Management that allow the publisher to change the behavior of the API through configuration. Policies are a collection of statements that are executed sequentially on the request or response of an API. Popular statements include format conversion from XML to JSON and call rate limiting to restrict the amount of incoming calls from a developer, and many other policies are available.
 
-Policy expressions can be used as attribute values or text values in any of the API Management policies, unless the policy specifies otherwise. Some policies such as the [Control flow][] and [Set variable][] policies are based on policy expressions. For more information, see [Advanced policies][], [Policy expressions][], and watch the following video.
+Policy expressions can be used as attribute values or text values in any of the API Management policies, unless the policy specifies otherwise. Some policies such as the [Control flow](https://msdn.microsoft.com/library/azure/dn894085.aspx#choose) and [Set variable](https://msdn.microsoft.com/library/azure/dn894085.aspx#set-variable) policies are based on policy expressions. For more information, see [Advanced policies](https://msdn.microsoft.com/library/azure/dn894085.aspx#AdvancedPolicies), [Policy expressions](https://msdn.microsoft.com/library/azure/dn910913.aspx), and watch the following video.
 
 > [AZURE.VIDEO policy-expressions-in-azure-api-management]
 

articles/app-service-api/app-service-api-dotnet-consume-internal.md

@@ -13,7 +13,7 @@
 	ms.tgt_pltfrm="dotnet" 
 	ms.devlang="na" 
 	ms.topic="article" 
-	ms.date="07/31/2015" 
+	ms.date="10/30/2015" 
 	ms.author="bradyg"/>
 
 # Consume an internal API app in Azure App Service from a .NET client 

articles/app-service-api/app-service-api-hybrid-on-premises-sql-server.md

@@ -361,7 +361,7 @@ The **Azure App Service Activity** window shows the deployment progress, and wil
 
 4. In the **API Apps** blade, locate your API app and click it.
 
-5. In your APII app's blade, click the value under **API app host**.  
+5. In your API app's blade, click the value under **API app host**.  
 
 	![API App blade](./media/app-service-api-hybrid-on-premises-sql-server/api-app-blade-api-app-host.png)
 

articles/app-service-api/app-service-api-javascript-client.md

@@ -13,7 +13,7 @@
 	ms.tgt_pltfrm="na" 
 	ms.devlang="JavaScript" 
 	ms.topic="article" 
-	ms.date="07/31/2015" 
+	ms.date="10/30/2015" 
 	ms.author="bradygaster"/>
 
 # Consume an Azure API App using HTML and JavaScript
@@ -141,7 +141,7 @@ The process of enabling CORS in Web API is documented in the ASP.NET article [En
 
 ## Creating a Web App to Consume the API App
 
-In this section, you'll create a new Empty Web Application, install and use AngularJS into it, and bind a simple HTML front end to the API App. You'll deploy the consuming Web App into Azure App Service. The HTML Web App will bind to and display the data retrieved from the API App, and provide users a simple UI for the Contacts API. 
+In this section, you'll create a new Empty Web Application, install and use AngularJS, and bind a simple HTML front end to the API App. You'll deploy the consuming Web App into Azure App Service. The HTML Web App will bind to and display the data retrieved from the API App, and provide users a simple UI for the Contacts API. 
 
 1. Right-click the solution that you created earlier in [Create an API App](app-service-dotnet-create-api-app.md), and select **Add -> New Project**
 
@@ -312,7 +312,7 @@ In this section, you'll create a new Empty Web Application, install and use Angu
 
 1, In the code you just added to index.html, replace the port number in the base URL (`http://localhost:1578`) with the actual port number for your API project.
 
-	> **Note** Don't use the port number of the HTML client project. You can right-click the API project and click **Debug > Start New Instance** to get a browser window that shows the port number.
+>[AZURE.NOTE] **Note** Don't use the port number of the HTML client project. You can right-click the API project and click **Debug > Start New Instance** to get a browser window that shows the port number.
 
 1. Make sure that the API App project is also running when you run the HTML client, or the JavaScript HTML will not function properly. Right-click the solution and select **Properties**. Then set both Web projects to **Start without Debugging**, and that the API project runs first. 
 

articles/app-service-mobile/app-service-mobile-dotnet-backend-how-to-use-server-sdk.md

@@ -20,6 +20,8 @@
 
 This topic shows you how to use the .NET backend server SDK in key Azure App Service Mobile Apps scenarios. The Azure Mobile Apps SDK helps you work with mobile clients from your ASP.NET application.
 
+>[AZURE.TIP] The [.NET server SDK for Azure Mobile Apps](https://github.com/Azure/azure-mobile-apps-net-server) is open source on GitHub. The repository contains the entire server SDK unit test suite as well as some sample projects.
+
 ## How to: Download and initialize the SDK
 
 The SDK is available on [NuGet.org]. This package includes the base functionality required to get started using the SDK. To initialize the SDK, you need to perform actions on the **HttpConfiguration** object. 
@@ -28,7 +30,7 @@ The SDK is available on [NuGet.org]. This package includes the base functionalit
 
 To install the SDK, right-click on the server project in Visual Studio, select **Manage NuGet Packages**, search for the [Microsoft.Azure.Mobile.Server](http://www.nuget.org/packages/Microsoft.Azure.Mobile.Server/) package, then click **Install**.  
 
-###Initialize the server project
+###<a name="server-project-setup"></a> Initialize the server project
 
 A .NET backend server project is initialized similar to other ASP.NET projects, by including an OWIN startup class. To add this class in Visual Studio, right-click on your server project and select **Add** -> **New Item**, then **Web** -> **General** -> **OWIN Startup class**.