fix broken-links for app-types document

docs/core/app-types.md

@@ -10,7 +10,7 @@ ms.prod: .net-core
 ms.technology: .net-core-technologies
 ms.devlang: dotnet
 ms.assetid: 93488a0b-c94c-4ed6-97ea-571bb23a862e
-redirect_url: /deploying/index
+redirect_url: /dotnet/articles/core/deploying/index
 ---
 
 # .NET Core App Types

docs/core/migrating-from-dnx.md

@@ -153,7 +153,7 @@ a fully *portable* application or you may want to have a *self-contained* applic
 like .NET Framework applications work: it needs a shared component to execute it on the target machine 
 (.NET Core). The self-contained application doesn't require .NET Core to be installed on the target, but you have to 
 produce one application for each OS you wish to support. These portability types and more are discussed in the
- [application portability type](app-types.md) document. 
+ [application portability type](deploying/index.md) document. 
 
 Once you make a call on what type of portability you want, you need to change your targeted framework(s). If you were 
 writing applications for .NET Core, you were most likely using `dnxcore50` as  your targeted framework. With the CLI 
@@ -169,7 +169,7 @@ for more information.
 
 Your `project.json` is now mostly ready. You need to go through your dependencies list and update the dependencies to 
 their newer versions, especially if you are using ASP.NET Core dependencies. If you were using separate packages for BCL APIs, 
-you can use the runtime package as explained in the [application portability type](app-types.md) document. 
+you can use the runtime package as explained in the [application portability type](deploying/index.md) document. 
 
 Once you are ready, you can try restoring with `dotnet restore`. Depending on the version of your dependencies, you 
 may encounter errors if NuGet cannot resolve the dependencies for one of the 

docs/core/tools/extensibility.md

@@ -28,7 +28,7 @@ The two extensibility mechanisms outlined above are not exclusive; you can use b
 depends largely on what is the goal you are trying to achieve with your extension.
 
 ## Per-project based extensibility
-Per-project tools are [portable console applications](../app-types.md) that are distributed as NuGet packages. Tools are 
+Per-project tools are [portable console applications](../deploying/index.md) that are distributed as NuGet packages. Tools are 
 only available in the context of the project that references them and for which they are restored; invocation outside 
 of the context of the project (for example, outside of the directory that contains the project) will fail as the command will 
 not be able to be found.

docs/core/tutorials/using-with-xplat-cli.md

@@ -95,7 +95,7 @@ You can also execute [`dotnet build`](../tools/dotnet-build.md) to compile the c
 
 ### Building a self-contained application
 
-Let's try compiling a self-contained application instead of a portable application. You can read more about the [types of portability in .NET Core](../app-types.md) to learn about the different application types, and how they are deployed.
+Let's try compiling a self-contained application instead of a portable application. You can read more about the [types of portability in .NET Core](../deploying/index.md) to learn about the different application types, and how they are deployed.
 
 You need to make some changes to your `project.json`
 file to direct the tools to build a self-contained application. You can see these in the