From d0025dc52c4192c88b4cb046a72a443dc0ce1407 Mon Sep 17 00:00:00 2001
From: Valentin <udaltsov.valentin@gmail.com>
Date: Sat, 17 Feb 2018 14:04:38 +0300
Subject: [PATCH 1/4] Compound option explained.

---
 reference/forms/types/options/compound.rst.inc | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/reference/forms/types/options/compound.rst.inc b/reference/forms/types/options/compound.rst.inc
index 7736a77567c..b5095d5dd00 100644
--- a/reference/forms/types/options/compound.rst.inc
+++ b/reference/forms/types/options/compound.rst.inc
@@ -3,6 +3,17 @@ compound
 
 **type**: ``boolean`` **default**: ``true``
 
-This option specifies if a form is compound. This is independent of whether
-the form actually has children. A form can be compound but not have any
-children at all (e.g. an empty collection form).
+The compound option determines whether a form can have children,
+in other words is a parent form for other forms.
+
+In terms of data a compound form usually represents an object or an array.
+In terms of view a compound form might be a simple ``<div>`` container or
+a ``<form>`` element (the whole form).
+
+A non compound form usually represents an object property or an array value
+and is rendered with actual form elements: ``<input>`` (``TextType``, ``HiddenType``),
+``<textarea>`` (``TextareType``) and ``<select>`` (``ChoiceType``).
+
+A interesting case is the ``ChoiceType``. With ``expanded=false`` it is rendered as
+a ``<select>`` form element and thus it is not a compound form. With ``expanded=true``
+the ``ChoiceType`` is rendered as a set of radios or checkboxes and becomes a compound form.

From b5f1a41f49a435a9645742fdc94446d473e578c3 Mon Sep 17 00:00:00 2001
From: Valentin <udaltsov.valentin@gmail.com>
Date: Fri, 9 Mar 2018 20:51:13 +0300
Subject: [PATCH 2/4] Rewritten.

---
 .../forms/types/options/compound.rst.inc      | 25 +++++++++++--------
 1 file changed, 14 insertions(+), 11 deletions(-)

diff --git a/reference/forms/types/options/compound.rst.inc b/reference/forms/types/options/compound.rst.inc
index b5095d5dd00..cb4f9b61e41 100644
--- a/reference/forms/types/options/compound.rst.inc
+++ b/reference/forms/types/options/compound.rst.inc
@@ -3,17 +3,20 @@ compound
 
 **type**: ``boolean`` **default**: ``true``
 
-The compound option determines whether a form can have children,
-in other words is a parent form for other forms.
+The compound option determines whether a form is compound.
 
-In terms of data a compound form usually represents an object or an array.
-In terms of view a compound form might be a simple ``<div>`` container or
-a ``<form>`` element (the whole form).
+Compound forms are structural elements in a form tree.
+Only a compound form can have children, in other words can be a parent for other forms.
 
-A non compound form usually represents an object property or an array value
-and is rendered with actual form elements: ``<input>`` (``TextType``, ``HiddenType``),
-``<textarea>`` (``TextareType``) and ``<select>`` (``ChoiceType``).
+In a view a compound form is rendered as a ``<div>`` container or
+a ``<form>`` element (the whole form is obviously a compound form).
 
-A interesting case is the ``ChoiceType``. With ``expanded=false`` it is rendered as
-a ``<select>`` form element and thus it is not a compound form. With ``expanded=true``
-the ``ChoiceType`` is rendered as a set of radios or checkboxes and becomes a compound form.
+Non-compound forms are always leaves in a form tree, they cannot have children.
+
+A non-compound form is rendered as one of the html form elements: ``<input>``
+(``TextType``, ``FileType``, ``HiddenType``), ``<textarea>`` (``TextareType``)
+or ``<select>`` (``ChoiceType``).
+
+An interesting case is the ``ChoiceType``. With ``expanded=false`` it is a non-compound form
+and is rendered as a ``<select>`` tag. With ``expanded=true`` the ``ChoiceType`` becomes a
+compound form and is rendered as a set of radios or checkboxes.

From c668925d07a31e399bbdc0b994b105ae2c91d98a Mon Sep 17 00:00:00 2001
From: Valentin <udaltsov.valentin@gmail.com>
Date: Tue, 13 Mar 2018 12:59:17 +0300
Subject: [PATCH 3/4] Fixed a typo in TextareaType.

---
 reference/forms/types/options/compound.rst.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reference/forms/types/options/compound.rst.inc b/reference/forms/types/options/compound.rst.inc
index cb4f9b61e41..8d6158ff033 100644
--- a/reference/forms/types/options/compound.rst.inc
+++ b/reference/forms/types/options/compound.rst.inc
@@ -14,7 +14,7 @@ a ``<form>`` element (the whole form is obviously a compound form).
 Non-compound forms are always leaves in a form tree, they cannot have children.
 
 A non-compound form is rendered as one of the html form elements: ``<input>``
-(``TextType``, ``FileType``, ``HiddenType``), ``<textarea>`` (``TextareType``)
+(``TextType``, ``FileType``, ``HiddenType``), ``<textarea>`` (``TextareaType``)
 or ``<select>`` (``ChoiceType``).
 
 An interesting case is the ``ChoiceType``. With ``expanded=false`` it is a non-compound form

From 65b0eefd5051e9b7a32b2acadc74d6cded64ddf1 Mon Sep 17 00:00:00 2001
From: Valentin <udaltsov.valentin@gmail.com>
Date: Mon, 19 Mar 2018 01:58:50 +0300
Subject: [PATCH 4/4] Reformulated the intro, added usage paragraph.

---
 reference/forms/types/options/compound.rst.inc | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/reference/forms/types/options/compound.rst.inc b/reference/forms/types/options/compound.rst.inc
index 8d6158ff033..10fe4d35a9e 100644
--- a/reference/forms/types/options/compound.rst.inc
+++ b/reference/forms/types/options/compound.rst.inc
@@ -3,10 +3,12 @@ compound
 
 **type**: ``boolean`` **default**: ``true``
 
-The compound option determines whether a form is compound.
+If ``true`` this option creates the form as "compound", meaning that it
+can contain children and be a parent of other forms.
 
-Compound forms are structural elements in a form tree.
-Only a compound form can have children, in other words can be a parent for other forms.
+Most of the time you won't need to override this option.
+You might want to control for it when creating a custom form type
+with advanced rendering logic.
 
 In a view a compound form is rendered as a ``<div>`` container or
 a ``<form>`` element (the whole form is obviously a compound form).