From f4f9ccafa62a0b433033bbd61950b7e895f52f9e Mon Sep 17 00:00:00 2001
From: wyatt-troia-msft <84938589+wyatt-troia-msft@users.noreply.github.com>
Date: Mon, 24 Mar 2025 15:25:06 -0400
Subject: [PATCH] Update create-edit-entity-relationships.md

---
 .../maker/data-platform/create-edit-entity-relationships.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/powerapps-docs/maker/data-platform/create-edit-entity-relationships.md b/powerapps-docs/maker/data-platform/create-edit-entity-relationships.md
index 561fa3c18f..02b54f5358 100644
--- a/powerapps-docs/maker/data-platform/create-edit-entity-relationships.md
+++ b/powerapps-docs/maker/data-platform/create-edit-entity-relationships.md
@@ -25,7 +25,7 @@ Table relationships in Microsoft Dataverse define the ways that table rows can b
 
 In a one-to-many table relationship, many referencing (related) table rows can be associated with a single referenced (primary) table row. The referenced table row is sometimes referred to as the ”parent” and rows of the referencing table are referred to as ”children.”  A many-to-one relationship is just the child perspective of a one-to-many relationship.
 
-For example, in a school scenario multiple courses might be delivered in a single classroom, so the class table would have a one-to-many relationship with the course table.
+For example, in a school scenario multiple courses might be delivered in a single classroom, so the classroom table would have a one-to-many relationship with the course table.
 
 ## Many-to-many relationships