From da43aa2d49cf48dcd9ee740f56c8150e1513576f Mon Sep 17 00:00:00 2001
From: Greg Bell <greg@bitwombat.com.au>
Date: Tue, 12 Jul 2016 16:05:20 +1000
Subject: [PATCH] Clarify language regarding ArrayCollections.
See https://groups.google.com/forum/#!topic/doctrine-user/yJ8ABqBP5mI
---
docs/en/tutorials/getting-started.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/en/tutorials/getting-started.rst b/docs/en/tutorials/getting-started.rst
index 6b5cb7294..ef4734317 100644
--- a/docs/en/tutorials/getting-started.rst
+++ b/docs/en/tutorials/getting-started.rst
@@ -616,12 +616,12 @@ domain model to match the requirements:
}
}
-Whenever an entity is recreated from the database, an Collection
-implementation of the type Doctrine is injected into your entity
-instead of an array. Compared to the ArrayCollection this
-implementation helps the Doctrine ORM understand the changes that
-have happened to the collection which are noteworthy for
-persistence.
+You use Doctrine's ArrayCollections in your Doctrine models, rather
+than plain PHP arrays, so that Doctrine can watch what happens with
+them and act appropriately. Note that if you dump your entities,
+you'll see a "PersistentCollection" in place of your ArrayCollection,
+which is just an
+internal Doctrine class with the same interface.
.. warning::