From b25548414b01ce101c87826f675d08b13a710c44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ad=C3=A1n=20Lobato?= Date: Thu, 31 May 2012 10:51:38 +0200 Subject: [PATCH] Fixed some typos on Inheritance docs --- en/reference/inheritance-mapping.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/en/reference/inheritance-mapping.rst b/en/reference/inheritance-mapping.rst index 9b44630a9..06ae0c656 100644 --- a/en/reference/inheritance-mapping.rst +++ b/en/reference/inheritance-mapping.rst @@ -4,7 +4,7 @@ Inheritance Mapping Mapped Superclasses ------------------- -An mapped superclass is an abstract or concrete class that provides +A mapped superclass is an abstract or concrete class that provides persistent entity state and mapping information for its subclasses, but which is not itself an entity. Typically, the purpose of such a mapped superclass is to define state and mapping information that @@ -142,7 +142,7 @@ very performant. There is a general performance consideration with Single Table Inheritance: If the target-entity of a many-to-one or one-to-one association is an STI entity, it is preferable for performance reasons that it -be a leaf entity in the inheritance heirarchy, (ie. have no subclasses). +be a leaf entity in the inheritance hierarchy, (ie. have no subclasses). Otherwise Doctrine *CANNOT* create proxy instances of this entity and will *ALWAYS* load the entity eagerly. @@ -245,7 +245,7 @@ subtypes after such a query is not safe. There is a general performance consideration with Class Table Inheritance: If the target-entity of a many-to-one or one-to-one association is a CTI entity, it is preferable for performance reasons that it -be a leaf entity in the inheritance heirarchy, (ie. have no subclasses). +be a leaf entity in the inheritance hierarchy, (ie. have no subclasses). Otherwise Doctrine *CANNOT* create proxy instances of this entity and will *ALWAYS* load the entity eagerly.