Documentation shows wrong VPC security group port range for AWS PrivateLink Connection

When adding an AWS PrivateLink Connection, for adding inbound rules to VPC SG IPv4 CIDR, we recommend to use the following port ranges:

11207–(11207 + Number of data nodes).

However, Our documentation seems to have overlooked the case of scaling the Capella cluster in which case the above range may not be sufficient as most likely user would just add the port range for the initial number of nodes based on the example shown.This can cause connection issues, reference CBSE-14719.

Please rectify and suggest the logical port range which can cover different scenarios, including scaling out and scaling up.

This is a blocker for customers.