Clarify grouped constructor retirement scope

docs/language.html

@@ -1674,7 +1674,7 @@ text, keys and uniqueness; it MUST NOT require a currently existing referenced
 object or current family applicability. In contrast, a new graphical or planned
 resolution MUST address the appropriate current record family and have at least
 one currently applicable side. Both-side NotApplicable facts are invalid persisted
-acknowledgements. A constructor decision retires such obsolete branch facts.</p>
+acknowledgements. A grouped constructor decision retires such obsolete branch facts.</p>
 <p>The following table is the exhaustive scalar catalog. <span class="docutils literal">T?</span> denotes an optional
 T, <span class="docutils literal">T[]</span> a list, and <span class="docutils literal">Id</span> a historical UUID. Existing enum and typed payload
 definitions in sections 3–4 apply. Every listed leaf wraps <span class="docutils literal">{ oa <span class="pre">...;</span> sa <span class="pre">...;</span> }</span>.</p>

docs/language.rst

@@ -1032,7 +1032,7 @@ text, keys and uniqueness; it MUST NOT require a currently existing referenced
 object or current family applicability. In contrast, a new graphical or planned
 resolution MUST address the appropriate current record family and have at least
 one currently applicable side. Both-side NotApplicable facts are invalid persisted
-acknowledgements. A constructor decision retires such obsolete branch facts.
+acknowledgements. A grouped constructor decision retires such obsolete branch facts.
 
 The following table is the exhaustive scalar catalog. ``T?`` denotes an optional
 T, ``T[]`` a list, and ``Id`` a historical UUID. Existing enum and typed payload