From e8ae1ce57053810e8ff5682ffd70bc37e690749b Mon Sep 17 00:00:00 2001
From: Matthias <121162196+Gre210675@users.noreply.github.com>
Date: Tue, 9 Dec 2025 18:10:12 +0100
Subject: [PATCH] Fix typo in one-to-one relationship documentation

---
 entity-framework/core/modeling/relationships/one-to-one.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/entity-framework/core/modeling/relationships/one-to-one.md b/entity-framework/core/modeling/relationships/one-to-one.md
index 048b462283..cea32d217b 100644
--- a/entity-framework/core/modeling/relationships/one-to-one.md
+++ b/entity-framework/core/modeling/relationships/one-to-one.md
@@ -176,7 +176,7 @@ Any one-to-one relationship where the foreign key is not discovered by conventio
 [!code-csharp[OneToOneRequiredPkToPkConfig](../../../../samples/core/Modeling/Relationships/OneToOne.cs?name=OneToOneRequiredPkToPkConfig)]
 
 > [!TIP]
-> `HasPrincipalKey` can also used for this purpose, but doing so is less common.
+> `HasPrincipalKey` can also be used for this purpose, but doing so is less common.
 
 When no property is specified in the call to `HasForeignKey`, and the primary key is suitable, then it is used as the foreign key. For cases where the navigations, foreign key, or required/optional nature of the relationship are not discovered by convention, these things can be configured explicitly. For example: