Move INCLUDES file (#7223)

aspnet/identity/overview/migrations/index.md

@@ -21,4 +21,4 @@ Migrating to ASP.NET Identity
 - [Migrating an Existing Website from SQL Membership to ASP.NET Identity](migrating-an-existing-website-from-sql-membership-to-aspnet-identity.md)
 - [Migrating Universal Provider Data for Membership and User Profiles to ASP.NET Identity (C#)](migrating-universal-provider-data-for-membership-and-user-profiles-to-aspnet-identity.md)
 
-[!INCLUDE[](~/includes/identity/alter-command-exception.md)]
+[!INCLUDE[](../../../includes/identity/alter-command-exception.md)]

aspnet/identity/overview/migrations/migrating-an-existing-website-from-sql-membership-to-aspnet-identity.md

@@ -111,7 +111,7 @@ With this information we can create SQL statements to create new tables. We can
 - Run command "Add-migration initial" which creates the initial setup code to create the database in C#/VB.
 - The final step is to run "Update-Database –Script" command that generates the SQL script based on the model classes.
 
-[!INCLUDE[](~/includes/identity/alter-command-exception.md)]
+[!INCLUDE[](../../../includes/identity/alter-command-exception.md)]
 
 This database generation script can be used as a start where we'll be making additional changes to add new columns and copy data. The advantage of this is that we generate the `_MigrationHistory` table which is used by EntityFramework to modify the database schema when the model classes change for future versions of Identity releases. 
 

aspnet/identity/overview/migrations/migrating-universal-provider-data-for-membership-and-user-profiles-to-aspnet-identity.md

@@ -101,7 +101,7 @@ Paste the SQL script from [https://raw.github.com/suhasj/UniversalProviders-Iden
 
 Copy the files in the **IdentityModels** and **IdentityAccount** folders from the download source ( [https://github.com/suhasj/UniversalProviders-Identity-Migrations/tree/master/UniversalProviders-Identity-Migrations](https://github.com/suhasj/UniversalProviders-Identity-Migrations/tree/master/UniversalProviders-Identity-Migrations) ). These have the remaining model classes and the new pages needed for user and role management using the ASP.NET Identity APIs. The approach used is similar to the SQL Membership and the detailed explanation can be found [here](migrating-an-existing-website-from-sql-membership-to-aspnet-identity.md).
 
-[!INCLUDE[](~/includes/identity/alter-command-exception.md)]
+[!INCLUDE[](../../../includes/identity/alter-command-exception.md)]
 
 ## Copying Profile data to the new tables