Skip to content

Commit d70783c

Browse files
authored
Fix typo (#5002)
Closes #5001
1 parent ae747af commit d70783c

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

entity-framework/core/modeling/relationships/many-to-many.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ EF allows for a more natural mapping through the introduction of two collection
8989
> [!TIP]
9090
> These new navigations are known as "skip navigations", because they skip over the join entity to provide direct access to the other side of the many-to-many relationship.
9191
92-
As is shown in the examples below, a many-to-many relationship can be mapped in this way--that is, with a .NET class for the join entity, and with both navigations for the two one-to-many relationships _and_ skip navigations exposed on the entity types. However, EF can manage the join entity transparently, without a .NET class defined for it, and without navigations for the two one-to-many relationships. For example:
92+
As is shown in the example above, a many-to-many relationship can be mapped in this way--that is, with a .NET class for the join entity, and with both navigations for the two one-to-many relationships _and_ skip navigations exposed on the entity types. However, EF can manage the join entity transparently, without a .NET class defined for it, and without navigations for the two one-to-many relationships. For example:
9393

9494
<!--
9595
public class Post

0 commit comments

Comments
 (0)