Skip to content

docs: fixed grammar error by adding missing "be" #4915

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roji merged 2 commits into from
Jan 2, 2025
Merged

docs: fixed grammar error by adding missing "be" #4915

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4b06e99
docs: fixed grammar error by adding missing "be"
ashkantaravati Dec 30, 2024
6348627
Update entity-framework/core/modeling/relationships.md
roji Jan 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion entity-framework/core/modeling/relationships.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ public class Blog
This connection from `Blog` to `Post` and, inversely, from `Post` back to `Blog` is known as a "relationship" in EF Core.

> [!IMPORTANT]
> A **single** relationship can typically traversed in either direction. In this example, that is from `Blog` to `Post` via the `Blog.Posts` property, and from `Post` back to `Blog` via the `Post.Blog` property. This is **one** relationship, not two.
> A **single** relationship can typically be traversed in either direction. In this example, that is from `Blog` to `Post` via the `Blog.Posts` property, and from `Post` back to `Blog` via the `Post.Blog` property. This is **one** relationship, not two.

> [!TIP]
> In EF Core, the `Blog.Posts` and `Post.Blog` properties are called "navigations".
Expand Down