Change:
<ins> ## `BootstrapToken`     {#BootstrapToken} **Appears in:** - [InitConfiguration](#kubeadm-k8s-io-v1beta3-InitConfiguration) <p>BootstrapToken describes one bootstrap token, stored as a Secret in the cluster</p> <table class="table"> <thead><tr><th width="30%">Field</th><th>Description</th></tr></thead> <tbody> <tr><td><code>token</code> <B>[Required]</B><br/> <a href="#BootstrapTokenString"><code>BootstrapTokenString</code></a> </td> <td> <p><code>token</code> is used for establishing bidirectional trust between nodes and control-planes. Used for joining nodes in the cluster.</p> </td> </tr> <tr><td><code>description</code><br/> <code>string</code> </td> <td> <p><code>description</code> sets a human-friendly message why this token exists and what it's used for, so other administrators can know its purpose.</p> </td> </tr> <tr><td><code>ttl</code><br/> <a href="https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Duration"><code>meta/v1.Duration</code></a> </td> <td> <p><code>ttl</code> defines the time to live for this token. Defaults to <code>24h</code>. <code>expires</code> and <code>ttl</code> are mutually exclusive.</p> </td> </tr> <tr><td><code>expires</code><br/> <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.23/#time-v1-meta"><code>meta/v1.Time</code></a> </td> <td> <p><code>expires</code> specifies the timestamp when this token expires. Defaults to being set dynamically at runtime based on the <code>ttl</code>. <code>expires</code> and <code>ttl</code> are mutually exclusive.</p> </td> </tr> <tr><td><code>usages</code><br/> <code>[]string</code> </td> <td> <p><code>usages</code> describes the ways in which this token can be used. Can by default be used for establishing bidirectional trust, but that can be changed here.</p> </td> </tr> <tr><td><code>groups</code><br/> <code>[]string</code> </td> <td> <p><code>groups</code> specifies the extra groups that this token will authenticate as when/if used for authentication</p> </td> </tr> </tbody> </table> ## `BootstrapTokenString`     {#BootstrapTokenString} **Appears in:** - [BootstrapToken](#BootstrapToken) <p>BootstrapTokenString is a token of the format <code>abcdef.abcdef0123456789</code> that is used for both validation of the practically of the API server from a joining node's point of view and as an authentication method for the node in the bootstrap phase of &quot;kubeadm join&quot;. This token is and should be short-lived.</p> <table class="table"> <thead><tr><th width="30%">Field</th><th>Description</th></tr></thead> <tbody> <tr><td><code>-</code> <B>[Required]</B><br/> <code>string</code> </td> <td> <span class="text-muted">No description provided.</span></td> </tr> <tr><td><code>-</code> <B>[Required]</B><br/> <code>string</code> </td> <td> <span class="text-muted">No description provided.</span></td> </tr> </tbody> </table> </ins> ## `ClusterConfiguration`     {#kubeadm-k8s-io-v1beta3-ClusterConfiguration}

Discussion:
file: kubeadm- ignorePreflightErrors need to under nodeRegistration.
That is exactly what the reference is saying.
I think you're suggesting a clarification to Have I got that right?
In the example:
Hi I'm going to edit your follow-up for readability - to make the YAML formatting more obvious.
That YAML from the email message is equivalent to:
It looks like the rest of your follow-up message is missing I can see the start of a sentence, “In the example:”, but not the remainder. /triage needs-information.
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : It looks like the rest of your follow-up message is missing I can see the start of a sentence, “In the example:”, but not the remainder. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage needs-information
Okay, that makes sense. The example might be wrong. I'll look into it.
/sig cluster-lifecycle
looks like both and have some minor indentation issues. i though that we fixed these (apparently not). i can send PR for k/k later today.
PR for k/k is here:
/triage accepted /kind bug /remove-triage needs-information
/assign Reference is being regenerated using the updated doc comments.