Fix some xrefs (#3677)

dotnet · Jan 12, 2022 · ef32c22 · ef32c22
1 parent f91f42d
commit ef32c22
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/entity-framework/efcore-and-ef6/porting/port-detailed-cases.md b/entity-framework/efcore-and-ef6/porting/port-detailed-cases.md
@@ -156,6 +156,6 @@ EF6 has some query capabilities that do not exist in EF Core. These include:
 - Interception of the command tree for queries and updates.
 - Support for table-valued parameters (TVPs).
 
-EF6 has built-in support for lazy-loading proxies. This is an opt-in package for EF Core (see [Lazy Loading of Related Data]xref:core/querying/related-data/lazy)).
+EF6 has built-in support for lazy-loading proxies. This is an opt-in package for EF Core (see [Lazy Loading of Related Data](xref:core/querying/related-data/lazy)).
 
 EF Core allows you to compose over raw SQL using `FromSQL`.
diff --git a/entity-framework/efcore-and-ef6/porting/port-edmx.md b/entity-framework/efcore-and-ef6/porting/port-edmx.md
@@ -47,6 +47,6 @@ Just because your application compiles, does not mean it is successfully ported
 
 EF Core does not support the `EntityClient` provider and therefore any [EntitySQL](/dotnet/framework/data/adonet/ef/language-reference/entity-sql-language) queries must be migrated to LINQ or `FromRawSql`.
 
-Furthermore, there is no support for [EntityClient connection strings]xref:ef6/fundamentals/configuring/connection-strings#databasemodel-first-with-connection-string-in-appconfigwebconfig-file).
+Furthermore, there is no support for [EntityClient connection strings](xref:ef6/fundamentals/configuring/connection-strings#databasemodel-first-with-connection-string-in-appconfigwebconfig-file).
 
 For more considerations, read the complete guide to [differences between EF6 and EF Core](/efcore-and-ef6/porting/port-detailed-cases.md).