updated README caveats

Wes Kendall · Wes Kendall · commit 1b071b837d71 · 2014-02-20T10:49:33.000-05:00
diff --git a/README.md b/README.md
@@ -139,4 +139,4 @@ One can also filter on the sub/super entities by their type. This is useful if t
     0
 
 ## Caveats With Django Entity
-Django entity connects to the post_save and post_delete signals defined in Django to sync up your entity models when they are changed or deleted. However, since Django does not send any signals upon bulk creates or updates, you will have to ensure that your app calls sync_entities() after any bulk create or update. If your application does not depend on having entities fully synced at all times, a simpler solution is to set up a recurring job that syncs your entities to catch these caveats.
+Django Entity has some current caveats worth noting. Currently, Djagno Entity links with post_save and post_delete signals so that any BaseEntityModel will be mirrored when updated. However, if the BaseEntityModel uses other models in its metadata or in defining its relationships to other models, these will not be updated when those other models are updated. For example, if there is a GroupMembership model that defines a if a User is active within a Group, changing the GroupMembership model will not remirror the Entity tables since GroupMembership does not inherit from BaseEntityModel. Future methods will be put in place to eliminate this caveat.

Original file line number	Diff line number	Diff line change
`@@ -139,4 +139,4 @@ One can also filter on the sub/super entities by their type. This is useful if t`
`139`	`139`	`0`
`140`	`140`
`141`	`141`	`## Caveats With Django Entity`
`142`		`-Django entity connects to the post_save and post_delete signals defined in Django to sync up your entity models when they are changed or deleted. However, since Django does not send any signals upon bulk creates or updates, you will have to ensure that your app calls sync_entities() after any bulk create or update. If your application does not depend on having entities fully synced at all times, a simpler solution is to set up a recurring job that syncs your entities to catch these caveats.`
	`142`	+Django Entity has some current caveats worth noting. Currently, Djagno Entity links with post_save and post_delete signals so that any BaseEntityModel will be mirrored when updated. However, if the BaseEntityModel uses other models in its metadata or in defining its relationships to other models, these will not be updated when those other models are updated. For example, if there is a GroupMembership model that defines a if a User is active within a Group, changing the GroupMembership model will not remirror the Entity tables since GroupMembership does not inherit from BaseEntityModel. Future methods will be put in place to eliminate this caveat.