Fix links

entity-framework/core/cli/dotnet.md

@@ -177,7 +177,7 @@ The [common options](#common-options) are listed above.
 
 Generates a compiled version of the model used by the `DbContext`. Added in EF Core 6.
 
-See [Compiled models](../performance/advanced-performance-topics.md#compiled-models) for more information.
+See [Compiled models](xref:core/performance/advanced-performance-topics#compiled-models) for more information.
 
 Options:
 
@@ -363,4 +363,4 @@ dotnet ef migrations script 20180904195021_InitialCreate
 
 * [Migrations](xref:core/managing-schemas/migrations/index)
 * [Reverse Engineering](xref:core/managing-schemas/scaffolding)
-* [Compiled models](../performance/advanced-performance-topics.md#compiled-models)
+* [Compiled models](xref:core/performance/advanced-performance-topics#compiled-models)

entity-framework/core/cli/powershell.md

@@ -174,7 +174,7 @@ The [common parameters](#common-parameters) are listed above.
 
 Generates a compiled version of the model used by the `DbContext`. Added in EF Core 6.
 
-See [Compiled models](../performance/advanced-performance-topics.md#compiled-models) for more information.
+See [Compiled models](xref:core/performance/advanced-performance-topics#compiled-models) for more information.
 
 Parameters:
 
@@ -326,4 +326,4 @@ Update-Database 20180904195021_InitialCreate -Connection your_connection_string
 
 * [Migrations](xref:core/managing-schemas/migrations/index)
 * [Reverse Engineering](xref:core/managing-schemas/scaffolding)
-* [Compiled models](../performance/advanced-performance-topics.md#compiled-models)
+* [Compiled models](xref:core/performance/advanced-performance-topics#compiled-models)

entity-framework/core/modeling/entity-properties.md

@@ -207,7 +207,7 @@ You can set an arbitrary text comment that gets set on the database column, allo
 > [!NOTE]
 > This feature was introduced in EF Core 6.0.
 
-By default when creating a table with [Migrations](../managing-schemas/migrations/index.md), EF Core orders primary key columns first, followed by properties of the entity type and owned types, and finally properties from base types. You can, however, specify a different column order:
+By default when creating a table with [Migrations](xref:core/managing-schemas/migrations/index), EF Core orders primary key columns first, followed by properties of the entity type and owned types, and finally properties from base types. You can, however, specify a different column order:
 
 ### [Data Annotations](#tab/data-annotations)
 

entity-framework/core/modeling/relationships.md

@@ -295,7 +295,7 @@ CREATE TABLE [PostTag] (
 );
 ```
 
-Internally, EF creates an entity type to represent the join table that will be referred to as the join entity type. `Dictionary<string, object>` is currently used for it to handle any combination of foreign key properties, see [property bag entity types](shadow-properties.md#property-bag-entity-types) for more information. More than one many-to-many relationships can exist in the model, therefore the join entity type must be given a unique name, in this case `PostTag`. The feature that allows this is called shared-type entity type.
+Internally, EF creates an entity type to represent the join table that will be referred to as the join entity type. `Dictionary<string, object>` is currently used for it to handle any combination of foreign key properties, see [property bag entity types](xref:core/modeling/shadow-properties#property-bag-entity-types) for more information. More than one many-to-many relationships can exist in the model, therefore the join entity type must be given a unique name, in this case `PostTag`. The feature that allows this is called shared-type entity type.
 
 > [!IMPORTANT]
 > The CLR type used for join entity types by convention may change in future releases to improve performance. Do not depend on the join type being `Dictionary<string, object>` unless this has been explicitly configured, as described in the next section.

entity-framework/core/modeling/shadow-properties.md

@@ -61,7 +61,7 @@ Indexer properties can be referenced in LINQ queries via the `EF.Property` stati
 > [!NOTE]
 > Support for Property bag entity types was introduced in EF Core 5.0.
 
-Entity types that contain only indexer properties are known as property bag entity types. These entity types don't have shadow properties, and EF creates indexer properties instead. Currently only `Dictionary<string, object>` is supported as a property bag entity type. It must be configured as a [shared-type entity type](entity-types.md#shared-type-entity-types) with a unique name and the corresponding `DbSet` property must be implemented using a `Set` call.
+Entity types that contain only indexer properties are known as property bag entity types. These entity types don't have shadow properties, and EF creates indexer properties instead. Currently only `Dictionary<string, object>` is supported as a property bag entity type. It must be configured as a [shared-type entity type](xref:core/modeling/entity-types#shared-type-entity-types) with a unique name and the corresponding `DbSet` property must be implemented using a `Set` call.
 
 [!code-csharp[Main](../../../samples/core/Modeling/ShadowAndIndexerProperties/SharedType.cs?name=SharedType&highlight=3,7)]
 

entity-framework/core/performance/advanced-performance-topics.md

@@ -184,7 +184,7 @@ PS C:\dotnet\efdocs\samples\core\Miscellaneous\CompiledModels>
 ```
 
 * For more information see [`dotnet ef dbcontext optimize`](xref:core/cli/dotnet#dotnet-ef-dbcontext-optimize).
-* If you're more comfortable working inside Visual Studio, you can also use [Optimize-DbContext](../cli/powershell.md#optimize-dbcontext)
+* If you're more comfortable working inside Visual Studio, you can also use [Optimize-DbContext](xref:core/cli/powershell#optimize-dbcontext)
 
 The output from running this command includes a piece of code to copy-and-paste into your `DbContext` configuration to cause EF Core to use the compiled model. For example: