May 8, 2014 · Apr 14, 2014 · Apr 14, 2014
diff --git a/cookbook/form/form_collections.rst b/cookbook/form/form_collections.rst
    work to ensure that the relationship between the ``Task`` and the removed
    ``Tag`` is properly removed.

    In Doctrine, you have twoside of the relationship: the owning side and the
    inverse side. Normally in this case you'll have a many-to-manyrelation
    In Doctrine, you have twosides of the relationship: the owning side and the
    inverse side. Normally in this case you'll have a many-to-manyrelationship
    and the deleted tags will disappear and persist correctly (adding new
    tags also works effortlessly).

    But if you havean one-to-manyrelation or a many-to-many with a
    But if you havea one-to-manyrelationship or a many-to-many relationship with a
    ``mappedBy`` on the Task entity (meaning Task is the "inverse" side),
    you'll need to do more work for the removed tags to persist correctly.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -653,12 +653,12 @@ the relationship between the removed ``Tag`` and ``Task`` object.
		work to ensure that the relationship between the ``Task`` and the removed
		``Tag`` is properly removed.

		In Doctrine, you have twoside of the relationship: the owning side and the
		inverse side. Normally in this case you'll have a many-to-manyrelation
		In Doctrine, you have twosides of the relationship: the owning side and the
		inverse side. Normally in this case you'll have a many-to-manyrelationship
		and the deleted tags will disappear and persist correctly (adding new
		tags also works effortlessly).

		But if you havean one-to-manyrelation or a many-to-many with a
		But if you havea one-to-manyrelationship or a many-to-many relationship with a
		``mappedBy`` on the Task entity (meaning Task is the "inverse" side),
		you'll need to do more work for the removed tags to persist correctly.

Expand Down