DOC-1497 update Customer-managed to BYOVPC (#352)

* DOC-1497 update Customer-managed to BYOVPC

* minor edit

Author: micheleRP

modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc

@@ -669,7 +669,7 @@ gcloud iam service-accounts add-iam-policy-binding <gke-service-account-name>@<s
 
 Log in to the https://cloud.redpanda.com[Redpanda Cloud UI^], and follow the steps to xref:get-started:cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc[create a BYOC cluster], with the following exceptions:
 
-. On the *Network* page, select the *Customer-managed* connection type, and enter the network, service account, storage bucket information, and GKE master CIDR range you created.
+. On the *Network* page, select the *BYOVPC* connection type, and enter the network, service account, storage bucket information, and GKE master CIDR range you created.
 
 . With customer-managed networks, you must grant yourself (the user deploying the cluster with `rpk`) the following permissions: 
 +

modules/reference/partials/tiers.adoc

@@ -19,7 +19,7 @@ When you create a BYOC cluster, you select your usage tier. Each tier provides t
 
 [NOTE]
 ==== 
-* Partition counts are based on clusters running Redpanda version 25.1 and on the assumption that the replication factor is 3 (default). If you set a higher replication factor, the maximum value for partitions will be lower.
+* Partition counts are based on clusters running Redpanda version 25.1 or higher and on the assumption that the replication factor is 3 (default). If you set a higher replication factor, the maximum value for partitions will be lower.
 * On Azure, tiers 1-5 are supported.
 * Redpanda supports compute-optimized tiers with AWS Graviton3 processors.
 * Depending on the workload, it may not be possible to achieve all maximum values. For example, a high number of partitions may make it more difficult to reach the maximum value in throughput.
@@ -122,7 +122,7 @@ When you create a Dedicated cluster, you select your usage tier. Each tier provi
 
 [NOTE]
 ====
-* Partition counts are based on clusters running Redpanda version 25.1 and on the assumption that the replication factor is 3 (default). If you set a higher replication factor, the maximum value for partitions will be lower.
+* Partition counts are based on clusters running Redpanda version 25.1 or higher and on the assumption that the replication factor is 3 (default). If you set a higher replication factor, the maximum value for partitions will be lower.
 * Depending on the workload, it may not be possible to achieve all maximum values. For example, a high number of partitions may make it more difficult to reach the maximum value in throughput.
 * Connections are regulated per broker for best performance. For example, in a tier 1 cluster with 3 brokers, there could be up to 3,000 connections per broker.