Use `Implicit wrapper` instead of `Implicit Child`

[kildom]

This new name may be easier to understand, e.g.:

---

When you place a node that is not allowed directly in current context, it will be wrapped using implicit wrapper tag.
For example, if you put <font> directly inside <document>, the DocTML will internally wrap <font> element with <p> element before placing it in the <document> element. This happens because <document> element has implicit wrapper <p>. In other words, the following code:

<document>
  <font size="8pt">foo</font>
</document>

will be interpret as:

<document>
  <p>
    <font size="8pt">foo</font>
  </p>
</document>

The implicit wrapper may be applied multiple times until valid hierarchy is reached.
For example, if you put text directly inside <document>, it will be wrapped with <p> first and then <font>. In other words, the following code:

<document>
  foo
</document>

will be interpret as:

<document>
  <p>
    <font>foo</font>
  </p>
</document>

[kildom]

HTML has a similar mechanism where certain elements are implicitly inserted by the browser when parsing HTML that’s missing required structure.

In the HTML spec and documentation, this behavior is commonly referred to as:

---

✅ "Implied elements" or "implied tags"

This is the most common term used in both the HTML specification and developer-facing documentation (like MDN or WHATWG).

Example usage:

When a <tr> is placed directly inside a <table>, the browser implies a <tbody> element as its container, even if it's not explicitly present in the markup.

---

🔄 Also commonly called:

• Implicit insertion
• Implicit DOM construction
• Tag omission / implied tag insertion
• Parser-generated elements
• Automatic element inference

---

📘 Official sources use phrasing like:

• HTML Parsing algorithm (WHATWG spec):

  “The user agent will automatically insert elements that are required by the content model (such as <tbody> inside <table>) if they are omitted.”

• MDN (Mozilla Developer Network):

  “The <tbody> element is implied when a <tr> is placed inside a <table> without it.”

---

🏷️ So in your XML spec, analogous naming might include:

• Implied wrapper element
• Implicitly inferred structure
• Parser-inserted node
• Auto-generated intermediate element

These mirror the HTML terminology and will feel intuitive to developers familiar with HTML.