Merge pull request #278867 from jim-minter/fleet-patch

Remove incorrect difference between hubless/hubful - both have a limit of 100 members, which is documented elsewhere.

Author: prmerger-automator[bot]

articles/kubernetes-fleet/concepts-choosing-fleet.md

@@ -23,7 +23,6 @@ The following table compares the scenarios enabled by the hub cluster:
 | Capability | Kubernetes Fleet resource without hub cluster | Kubernetes Fleet resource with hub cluster |
 |----|----|----|
 |**Hub cluster hosting**|<span class='red-x'>&#10060;</span>|<span class='green-check'>&#9989;</span>|
-|**Member cluster limit**|Up to 100 clusters|Up to 20 clusters|
 |**Update orchestration**|<span class='green-check'>&#9989;</span>|<span class='green-check'>&#9989;</span>|
 |**Workload orchestration**|<span class='red-x'>&#10060;</span>|<span class='green-check'>&#9989;</span>|
 |**Layer 4 load balancing**|<span class='red-x'>&#10060;</span>|<span class='green-check'>&#9989;</span>|

articles/kubernetes-fleet/faq.md

@@ -24,7 +24,7 @@ Today, Azure Kubernetes Fleet Manager supports joining existing AKS clusters as
 
 ## Number of clusters
 
-The number of member clusters that can be joined to the same fleet resource depends on whether the fleet resource has a hub cluster or not. Fleets without a hub cluster support joining up to 100 AKS clusters. Fleet resources with a hub cluster support joining up to 20 AKS clusters.
+Fleets support joining up to 100 AKS clusters, regardless of whether they have a hub cluster or not.
 
 ## AKS clusters that can be joined as members