docs: fixes minor issues in nodeadm kep

Author: faiq

docs/proposal/20250922-nodeadm-bootstrap.md

@@ -88,7 +88,6 @@ This KEP proposes a new type that handles bootstrapping with `nodeadm` alone. Th
  The **cons** are:
 
    * The scope of work to support EKS nodes grows significantly and is pushed out.
-   * Users need to know that setting `AWSMachine.Spec.Ami.EKSLookupType` to `AmazonLinux` won’t work with the new `nodeadm` bootstrap method.
 
  ### User Stories
 
@@ -111,10 +110,6 @@ This KEP proposes a new type that handles bootstrapping with `nodeadm` alone. Th
  // +optional
  Containerd *ContainerdOptions `json:"containerd,omitempty"`
 
- // Instance contains options for the node's operating system and devices.
- // +optional
- Instance *InstanceOptions `json:"instance,omitempty"`
-
  // FeatureGates holds key-value pairs to enable or disable application features.
  // +optional
  FeatureGates map[Feature]bool `json:"featureGates,omitempty"`
@@ -282,6 +277,7 @@ A valid concern that CAPA users will have is upgrading existing clusters to mach
            kind: NodeadmConfigTemplate
            name: default-133
        infrastructureRef:
+         apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
          kind: AWSMachinePool
          name: default
        version: v1.33.0
@@ -294,11 +290,6 @@ A valid concern that CAPA users will have is upgrading existing clusters to mach
     * E2e tests exercising the migration from EKSConfig to NodeadmConfig,
 
 
- ## Drawbacks
-
-   * The scope of work to support EKS nodes grows significantly and is pushed out.
-   * Users need to know that setting `AWSMachine.Spec.Ami.EKSLookupType` to `AmazonLinux` won’t work with the new `nodeadm` bootstrap method.
-
  -----
 
  ## Alternatives