Section on how to scale machineSets of machines using static IPs in vSphere is not very comprehensible and needs some additional points.
When we first start to explain about IPAddressClaims, there is no additional information about IPPools and what exactly is needed to make this work.
We are making the assumption all customers will have some IPAM service to controller these objects and will know what is this referring to.
Another point is that IPPools can be implemented by multiple controllers and can be easily confused. For example OCP deploys this object via whereabouts to be used by Multus. However this is completely unrelated and only used for pods.
When using static IPs, the installer deploys it's own IPPool that can be used later on and for this case the explanations we make about IPaddressclaims actual make sense. However we make no reference on this IPPool and its possible usability. This will be important for customers that don't have any IPAM service controller and/or don't know about this.
Finally the 5 point should be set as an option in case the IPAM controller is not capable of doing this association. This step  for example is required if a customer uses the default IPPool created by the installer.

    since OCP 4.16

    1.
    2.
    3.