x_ite 8.8.7 → 8.9.0

package/docs/_posts/components/Layering/Viewport.md

@@ -1,6 +1,6 @@
 ---
 title: Viewport
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Layering
 categories: [components, Layering]
 tags: [Viewport, Layering]
@@ -15,7 +15,7 @@ tags: [Viewport, Layering]
 
 Viewport is a Grouping node that can contain most nodes. Viewport specifies a set of rectangular clip boundaries against which the children nodes are clipped as they are rendered.
 
-The Viewport node belongs to the **Layering** component and its default container field is *viewport.* It is available since X3D version 3.2 or later.
+The Viewport node belongs to the **Layering** component and its default container field is *viewport.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -33,7 +33,11 @@ The Viewport node belongs to the **Layering** component and its default containe
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### MFFloat [in, out] **clipBoundary** [ 0, 1, 0, 1 ] <small>[0,1]</small>
 
@@ -47,10 +51,10 @@ Metadata are not part of the X3D world and not interpreted by the X3D browser, b
 
 Whether or not renderable content within this node is visually displayed.
 
-#### Hint
+#### Hints
 
-- The visible field has no effect on animation behaviors, event passing or other non-visual characteristics.
-- Content must be visible to be collidable and to be pickable.
+- The *visible* field has no effect on animation behaviors, event passing or other non-visual characteristics.
+- Content must be *visible* to be collidable and to be pickable.
 
 ### SFBool [in, out] **bboxDisplay** FALSE
 
@@ -64,34 +68,46 @@ Whether to display bounding box for associated geometry, aligned with world coor
 
 Bounding box size is usually omitted, and can easily be calculated automatically by an X3D player at scene-loading time with minimal computational cost. Bounding box size can also be defined as an optional authoring hint that suggests an optimization or constraint.
 
-#### Hint
+#### Hints
 
 - Can be useful for collision computations or inverse-kinematics (IK) engines.
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### SFVec3f [ ] **bboxCenter** 0 0 0 <small>(-∞,∞)</small>
 
-Bounding box center: optional hint for position offset from origin of local coordinate system.
+Bounding box center accompanies bboxSize and provides an optional hint for bounding box position offset from origin of local coordinate system.
+
+#### Hints
+
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### MFNode [in] **addChildren**
 
-Input field addChildren.
+Input field *addChildren*.
 
 ### MFNode [in] **removeChildren**
 
-Input field removeChildren.
+Input field *removeChildren*.
 
 ### MFNode [in, out] **children** [ ] <small>[X3DChildNode]</small>
 
-Grouping nodes contain a list of children nodes.
+Grouping nodes contain an ordered list of *children* nodes.
 
-#### Hint
+#### Hints
 
-- Each grouping node defines a coordinate space for its children, relative to the coordinate space of its parent node. Thus transformations accumulate down the scene graph hierarchy.
+- Each grouping node defines a coordinate space for its *children*, relative to the coordinate space of its parent node. Thus transformations accumulate down the scene graph hierarchy.
+- InputOnly MFNode addChildren field can append new X3DChildNode nodes via a ROUTE connection, duplicate input nodes (i.e. matching DEF, USE values) are ignored.
+- InputOnly MFNode removeChildren field can remove nodes from the *children* list, unrecognized input nodes (i.e. nonmatching DEF, USE values) are ignored.
+- [X3D Architecture 10.2.1 Grouping and *children* node types](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#GroupingAndChildrenNodes){:target="_blank"}
 
 ## Example
 
 <x3d-canvas src="https://create3000.github.io/media/examples/Layering/Viewport/Viewport.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of Viewport](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layering.html#Viewport){:target="_blank"}
+- [X3D Specification of Viewport node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layering.html#Viewport){:target="_blank"}

package/docs/_posts/components/Layout/Layout.md

@@ -1,6 +1,6 @@
 ---
 title: Layout
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Layout
 categories: [components, Layout]
 tags: [Layout, Layout]
@@ -15,7 +15,7 @@ tags: [Layout, Layout]
 
 Layout node is used as layout field of LayoutLayer and LayoutGroup nodes. Layout provides all parameters required to define the size, location and scale of a 2D rectangular region.
 
-The Layout node belongs to the **Layout** component and its default container field is *layout.* It is available since X3D version 3.2 or later.
+The Layout node belongs to the **Layout** component and its default container field is *layout.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -30,11 +30,15 @@ The Layout node belongs to the **Layout** component and its default container fi
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### MFString [in, out] **align** [ "CENTER", "CENTER" ] <small>["LEFT"|"CENTER"|"RIGHT"]</small>
 
-The align field values align the sized rectangle to an edge or center of the parent rectangle. Two quoted string values are provided. The first value is for horizontal direction (LEFT \| CENTER \| RIGHT) and the second value is for vertical direction (BOTTOM \| CENTER \| TOP). Examples: "CENTER" "CENTER" (default value), "LEFT" "TOP" or "RIGHT" "BOTTOM".
+The *align* field values *align* the sized rectangle to an edge or center of the parent rectangle. Two quoted string values are provided. The first value is for horizontal direction (LEFT or CENTER or RIGHT) and the second value is for vertical direction (BOTTOM or CENTER or TOP). Examples: "CENTER" "CENTER" (default value), "LEFT" "TOP" or "RIGHT" "BOTTOM".
 
 #### Hint
 
@@ -42,15 +46,17 @@ The align field values align the sized rectangle to an edge or center of the par
 
 #### Warnings
 
-- Two values (or possibly one value) only. If the align field has only one value, that value shall be "CENTER" and apply both horizontally and vertically.
+- Two values (or possibly one value) only.
+- If the *align* field has only one value, that value shall be "CENTER" and apply both horizontally and vertically.
 
 ### MFString [in, out] **offsetUnits** [ "WORLD", "WORLD" ] <small>["WORLD"|"FRACTION"|"PIXEL"]</small>
 
-The offsetUnits field values are used to interprete the offset values. Two quoted string values are provided. The first value is for horizontal offset, and the second value is for vertical offset. Examples: "WORLD" "WORLD" (default value), "FRACTION" "FRACTION" or "PIXEL" "PIXEL".
+The *offsetUnits* field values are used to interprete the offset values. Two quoted string values are provided. The first value is for horizontal offset, and the second value is for vertical offset. Examples: "WORLD" "WORLD" (default value), "FRACTION" "FRACTION" or "PIXEL" "PIXEL".
 
 #### Hints
 
-- If the value of the offsetUnits field is FRACTION, the size of the corresponding dimension is interpreted as a fraction of the corresponding parent’s dimension. MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
+- If the value of the *offsetUnits* field is FRACTION, the size of the corresponding dimension is interpreted as a fraction of the corresponding parent’s dimension.
+- MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
 
 #### Warning
 
@@ -58,7 +64,7 @@ The offsetUnits field values are used to interprete the offset values. Two quote
 
 ### MFFloat [in, out] **offset** [ 0, 0 ] <small>(-∞,∞)</small>
 
-The values of the offset field are used to translate the location of this rectangle after the initial alignment. The offsetUnits field specifies how to interpret the offset field.
+The values of the *offset* field are used to translate the location of this rectangle after the initial alignment. The offsetUnits field specifies how to interpret the *offset* field.
 
 #### Warning
 
@@ -66,11 +72,12 @@ The values of the offset field are used to translate the location of this rectan
 
 ### MFString [in, out] **sizeUnits** [ "WORLD", "WORLD" ] <small>["WORLD"|"FRACTION"|"PIXEL"]</small>
 
-The sizeUnits field values are used to interprete the offset values. Two quoted string values are provided. The first value is for horizontal size, and the second value is for vertical size. Examples: "WORLD" "WORLD" (default value), "FRACTION" "FRACTION" or "PIXEL" "PIXEL".
+The *sizeUnits* field values are used to interprete the offset values. Two quoted string values are provided. The first value is for horizontal size, and the second value is for vertical size. Examples: "WORLD" "WORLD" (default value), "FRACTION" "FRACTION" or "PIXEL" "PIXEL".
 
 #### Hints
 
-- If the value of the sizeUnits field is FRACTION, the size of the corresponding dimension is interpreted as a fraction of the corresponding parent’s dimension. MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
+- If the value of the *sizeUnits* field is FRACTION, the size of the corresponding dimension is interpreted as a fraction of the corresponding parent’s dimension.
+- MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
 
 #### Warning
 
@@ -78,7 +85,7 @@ The sizeUnits field values are used to interprete the offset values. Two quoted
 
 ### MFFloat [in, out] **size** [ 1, 1 ] <small>(0,∞)</small>
 
-The two values in the size field define the width and height of the layout rectangle. The sizeUnits field specifies how to interpret the size values.
+The two values in the *size* field define the width and height of the layout rectangle. The sizeUnits field specifies how to interpret the *size* values.
 
 #### Warning
 
@@ -86,22 +93,26 @@ The two values in the size field define the width and height of the layout recta
 
 ### MFString [in, out] **scaleMode** [ "NONE", "NONE" ] <small>["NONE"|"FRACTION"|"STRETCH"|"PIXEL"]</small>
 
-The scaleMode field specifies how the scale of the parent is modified. Two quoted string values are provided. The first value is for horizontal scale and the second value is for vertical scale. Examples: "NONE" "NONE" (default value), "FRACTION" "FRACTION", "STRETCH" "STRETCH" or "PIXEL" "PIXEL".
+The *scaleMode* field specifies how the scale of the parent is modified. Two quoted string values are provided. The first value is for horizontal scale and the second value is for vertical scale. Examples: "NONE" "NONE" (default value), "FRACTION" "FRACTION", "STRETCH" "STRETCH" or "PIXEL" "PIXEL".
 
 #### Hints
 
-- A scaleMode field value of NONE specifies that the corresponding scale value is not modified. Instead, the scale is inherited from its parent. Since a LayoutLayer node does not have a parent, the value of NONE reverts to FRACTION. A scaleMode value of FRACTION specifies a scale in the corresponding direction so that one unit is equal to the dimension (width or height) of this rectangle. A scaleMode value of STRETCH specifies a scale in the corresponding direction such that the resulting scale in the horizontal direction is equal to the scale in the vertical direction, thus producing a uniform scale. A value of PIXEL specifies a scale in the corresponding direction such that one unit is equal to one pixel. MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
+- A *scaleMode* field value of NONE specifies that the corresponding scale value is not modified. Instead, the scale is inherited from its parent. Since a LayoutLayer node does not have a parent, the value of NONE reverts to FRACTION.
+- A *scaleMode* value of FRACTION specifies a scale in the corresponding direction so that one unit is equal to the dimension (width or height) of this rectangle.
+- A *scaleMode* value of STRETCH specifies a scale in the corresponding direction such that the resulting scale in the horizontal direction is equal to the scale in the vertical direction, thus producing a uniform scale.
+- A value of PIXEL specifies a scale in the corresponding direction such that one unit is equal to one pixel.
+- MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
 
 #### Warning
 
 - If only one value is provided, it applies equally to horizontal and vertical directions (width and height). More than two values are not allowed.
 
-## Description
+## Advisories
 
 ### Hint
 
 - The align, offset, and offsetUnits fields are used to determine the location of the layout region.
 
-## External Links
+## See Also
 
-- [X3D Specification of Layout](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layout.html#Layout){:target="_blank"}
+- [X3D Specification of Layout node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layout.html#Layout){:target="_blank"}

package/docs/_posts/components/Layout/LayoutGroup.md

@@ -1,6 +1,6 @@
 ---
 title: LayoutGroup
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Layout
 categories: [components, Layout]
 tags: [LayoutGroup, Layout]
@@ -15,7 +15,7 @@ tags: [LayoutGroup, Layout]
 
 LayoutGroup is a Grouping node that can contain most nodes, whose children are related by a common layout within a parent layout. The layout field contains an X3DLayoutNode node that provides the information required to locate and size the layout region of the LayoutGroup node relative to its parent’s layout region. LayoutGroup content is clipped by the specified viewport node.
 
-The LayoutGroup node belongs to the **Layout** component and its default container field is *children.* It is available since X3D version 3.2 or later.
+The LayoutGroup node belongs to the **Layout** component and its default container field is *children.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -30,24 +30,28 @@ The LayoutGroup node belongs to the **Layout** component and its default contain
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFNode [in, out] **layout** NULL <small>[X3DLayoutNode]</small>
 
-The layout field contains an X3DLayoutNode node that provides the information required to locate and size the layout region of the LayoutGroup node relative to its parent’s layout region, and also to scale the contents of the LayoutGroup.
+The *layout* field contains an X3DLayoutNode node that provides the information required to locate and size the *layout* region of the LayoutGroup node relative to its parent’s *layout* region, and also to scale the contents of the LayoutGroup.
 
 ### SFNode [in, out] **viewport** NULL <small>[X3DViewportNode]</small>
 
-The content of the LayoutGroup is clipped by the specified viewport.
+The content of the LayoutGroup is clipped by the specified *viewport*.
 
 ### SFBool [in, out] **visible** TRUE
 
 Whether or not renderable content within this node is visually displayed.
 
-#### Hint
+#### Hints
 
-- The visible field has no effect on animation behaviors, event passing or other non-visual characteristics.
-- Content must be visible to be collidable and to be pickable.
+- The *visible* field has no effect on animation behaviors, event passing or other non-visual characteristics.
+- Content must be *visible* to be collidable and to be pickable.
 
 ### SFBool [in, out] **bboxDisplay** FALSE
 
@@ -61,31 +65,43 @@ Whether to display bounding box for associated geometry, aligned with world coor
 
 Bounding box size is usually omitted, and can easily be calculated automatically by an X3D player at scene-loading time with minimal computational cost. Bounding box size can also be defined as an optional authoring hint that suggests an optimization or constraint.
 
-#### Hint
+#### Hints
 
 - Can be useful for collision computations or inverse-kinematics (IK) engines.
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### SFVec3f [ ] **bboxCenter** 0 0 0 <small>(-∞,∞)</small>
 
-Bounding box center: optional hint for position offset from origin of local coordinate system.
+Bounding box center accompanies bboxSize and provides an optional hint for bounding box position offset from origin of local coordinate system.
+
+#### Hints
+
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### MFNode [in] **addChildren**
 
-Input field addChildren.
+Input field *addChildren*.
 
 ### MFNode [in] **removeChildren**
 
-Input field removeChildren.
+Input field *removeChildren*.
 
 ### MFNode [in, out] **children** [ ] <small>[X3DChildNode]</small>
 
-Grouping nodes contain a list of children nodes.
+Grouping nodes contain an ordered list of *children* nodes.
 
-#### Hint
+#### Hints
 
-- Each grouping node defines a coordinate space for its children, relative to the coordinate space of its parent node. Thus transformations accumulate down the scene graph hierarchy.
+- Each grouping node defines a coordinate space for its *children*, relative to the coordinate space of its parent node. Thus transformations accumulate down the scene graph hierarchy.
+- InputOnly MFNode addChildren field can append new X3DChildNode nodes via a ROUTE connection, duplicate input nodes (i.e. matching DEF, USE values) are ignored.
+- InputOnly MFNode removeChildren field can remove nodes from the *children* list, unrecognized input nodes (i.e. nonmatching DEF, USE values) are ignored.
+- [X3D Architecture 10.2.1 Grouping and *children* node types](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#GroupingAndChildrenNodes){:target="_blank"}
 
-## Description
+## Advisories
 
 ### Hints
 
@@ -97,6 +113,6 @@ Grouping nodes contain a list of children nodes.
 
 - A LayoutGroup can only be a child of a LayoutLayer node or another LayoutGroup node.
 
-## External Links
+## See Also
 
-- [X3D Specification of LayoutGroup](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layout.html#LayoutGroup){:target="_blank"}
+- [X3D Specification of LayoutGroup node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layout.html#LayoutGroup){:target="_blank"}

package/docs/_posts/components/Layout/LayoutLayer.md

@@ -1,6 +1,6 @@
 ---
 title: LayoutLayer
-date: 2022-01-07
+date: 2023-01-07
 nav: components-Layout
 categories: [components, Layout]
 tags: [LayoutLayer, Layout]
@@ -15,7 +15,7 @@ tags: [LayoutLayer, Layout]
 
 LayoutLayer is a Grouping node that can contain most nodes. LayoutLayer content is clipped by the specified viewport node.
 
-The LayoutLayer node belongs to the **Layout** component and its default container field is *layers.* It is available since X3D version 3.2 or later.
+The LayoutLayer node belongs to the **Layout** component and its default container field is *layers.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -29,7 +29,11 @@ The LayoutLayer node belongs to the **Layout** component and its default contain
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFBool [in, out] **pickable** TRUE
 
@@ -37,41 +41,50 @@ Metadata are not part of the X3D world and not interpreted by the X3D browser, b
 
 ### MFString [in, out] **objectType** "ALL" <small>["ALL", "NONE", "TERRAIN", ...]</small>
 
-The objectType field specifies a set of labels used in the picking process. Each string specified is treated as an independent label that needs to be matched against the same type in one of the pick sensor instances.
+The *objectType* field specifies a set of labels used in the picking process. Each string specified is treated as an independent label that needs to be matched against the same type in one of the pick sensor instances. Example: labeling a PickableGroup with the *objectType* value "WATER" and then attempting to intersect a pick sensor with *objectType* value "GROUND" fails since the *objectType* values do not match. Example: the special value "ALL" means that each node is available for picking regardless of the type specified by the pick sensor. Example: the special value "NONE" effectively disables all picking for this node and is the equivalent of setting the pickable field to false.
 
 #### Hints
 
-- Authors may define any value for objectType. MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
+- Authors may define any value for *objectType*.
+- MFString arrays can have multiple values, so "separate each individual string" "by using quote marks".
 
 ### SFBool [in, out] **visible** TRUE
 
 Whether or not renderable content within this node is visually displayed.
 
+#### Hints
+
+- The *visible* field has no effect on animation behaviors, event passing or other non-visual characteristics.
+- Content must be *visible* to be collidable and to be pickable.
+
 ### SFNode [in, out] **layout** NULL <small>[X3DLayoutNode]</small>
 
-The layout field contains an X3DLayoutNode node that provides the information required to locate and size the layout region of the LayoutGroup node relative to its parent’s layout region, and also to scale the contents of the LayoutGroup.
+The *layout* field contains an X3DLayoutNode node that provides the information required to locate and size the *layout* region of the LayoutGroup node relative to its parent’s *layout* region, and also to scale the contents of the LayoutGroup.
 
 ### SFNode [in, out] **viewport** NULL <small>[X3DViewportNode]</small>
 
-The content of the LayoutGroup is clipped by the specified viewport.
+The content of the LayoutGroup is clipped by the specified *viewport*.
 
 ### MFNode [in] **addChildren**
 
-Input field addChildren.
+Input field *addChildren*.
 
 ### MFNode [in] **removeChildren**
 
-Input field removeChildren.
+Input field *removeChildren*.
 
 ### MFNode [in, out] **children** [ ] <small>[X3DChildNode]</small>
 
-Grouping nodes contain a list of children nodes.
+Grouping nodes contain an ordered list of *children* nodes.
 
-#### Hint
+#### Hints
 
-- Each grouping node defines a coordinate space for its children, relative to the coordinate space of its parent node. Thus transformations accumulate down the scene graph hierarchy.
+- Each grouping node defines a coordinate space for its *children*, relative to the coordinate space of its parent node. Thus transformations accumulate down the scene graph hierarchy.
+- InputOnly MFNode addChildren field can append new X3DChildNode nodes via a ROUTE connection, duplicate input nodes (i.e. matching DEF, USE values) are ignored.
+- InputOnly MFNode removeChildren field can remove nodes from the *children* list, unrecognized input nodes (i.e. nonmatching DEF, USE values) are ignored.
+- [X3D Architecture 10.2.1 Grouping and *children* node types](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#GroupingAndChildrenNodes){:target="_blank"}
 
-## Description
+## Advisories
 
 ### Hint
 
@@ -81,6 +94,6 @@ Grouping nodes contain a list of children nodes.
 
 - Better functional description needed in X3D specification.
 
-## External Links
+## See Also
 
-- [X3D Specification of LayoutLayer](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layout.html#LayoutLayer){:target="_blank"}
+- [X3D Specification of LayoutLayer node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/layout.html#LayoutLayer){:target="_blank"}