diff --git a/modules/installation-about-restricted-network.adoc b/modules/installation-about-restricted-network.adoc
index 7852be968471..05e5163309bc 100644
--- a/modules/installation-about-restricted-network.adoc
+++ b/modules/installation-about-restricted-network.adoc
@@ -54,13 +54,6 @@ endif::[]
 In {product-title} {product-version}, you can perform an installation that does not
 require an active connection to the internet to obtain software components. Restricted network installations can be completed using installer-provisioned infrastructure or user-provisioned infrastructure, depending on the cloud platform to which you are installing the cluster.
 
-ifdef::ipi-powervs[]
-[NOTE]
-====
-For installer-provisioned infrastructure in {product-title} {product-version}, you need to deploy your restricted network cluster in {product-title} 4.16 and upgrade it to {product-title} {product-version}.
-====
-endif::ipi-powervs[]
-
 ifndef::ibm-power,ibm-cloud[]
 If you choose to perform a restricted network installation on a cloud platform, you
 still require access to its cloud APIs. Some cloud functions, like
diff --git a/modules/installation-ibm-power-vs-config-yaml.adoc b/modules/installation-ibm-power-vs-config-yaml.adoc
index b6959889add2..96734c08d67b 100644
--- a/modules/installation-ibm-power-vs-config-yaml.adoc
+++ b/modules/installation-ibm-power-vs-config-yaml.adoc
@@ -322,19 +322,17 @@ platform:
     region: "powervs-region"
     vpcRegion: "vpc-region"
     vpcName: name-of-existing-vpc <10>
-    vpcSubnets: <11>
-       - name-of-existing-vpc-subnet
     zone: "powervs-zone"
     serviceInstanceID: "service-instance-id"
 publish: Internal
 credentialsMode: Manual
-pullSecret: '{"auths":{"<local_registry>": {"auth": "<credentials>","email": "you@example.com"}}}' <12>
-sshKey: ssh-ed25519 AAAA... <13>
-additionalTrustBundle: | <14>
+pullSecret: '{"auths":{"<local_registry>": {"auth": "<credentials>","email": "you@example.com"}}}' <11>
+sshKey: ssh-ed25519 AAAA... <12>
+additionalTrustBundle: | <13>
     -----BEGIN CERTIFICATE-----
     <MY_TRUSTED_CA_CERT>
     -----END CERTIFICATE-----
-imageContentSources: <15>
+imageContentSources: <14>
 - mirrors:
   - <local_registry>/<local_repository_name>/release
   source: quay.io/openshift-release-dev/ocp-release
@@ -362,11 +360,10 @@ When simultaneous multithreading (SMT), or hyperthreading is not enabled, one vC
 <8> The cluster network plugin to install. The default value `OVNKubernetes` is the only supported value.
 <9> The name of an existing resource group. The existing VPC and subnets should be in this resource group. The cluster is deployed to this resource group.
 <10> Specify the name of an existing VPC.
-<11> Specify the name of the existing VPC subnet. The subnets must belong to the VPC that you specified. Specify a subnet for each availability zone in the region.
-<12> For `<local_registry>`, specify the registry domain name, and optionally the port, that your mirror registry uses to serve content. For example, registry.example.com or registry.example.com:5000. For `<credentials>`, specify the base64-encoded user name and password for your mirror registry.
-<13> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
-<14> Provide the contents of the certificate file that you used for your mirror registry.
-<15> Provide the `imageContentSources` section from the output of the command to mirror the repository.
+<11> For `<local_registry>`, specify the registry domain name, and optionally the port, that your mirror registry uses to serve content. For example, registry.example.com or registry.example.com:5000. For `<credentials>`, specify the base64-encoded user name and password for your mirror registry.
+<12> You can optionally provide the `sshKey` value that you use to access the machines in your cluster.
+<13> Provide the contents of the certificate file that you used for your mirror registry.
+<14> Provide the `imageContentSources` section from the output of the command to mirror the repository.
 +
 [NOTE]
 ====
diff --git a/modules/installation-initializing.adoc b/modules/installation-initializing.adoc
index fa83d3136ac8..dfb7ebcc3ad9 100644
--- a/modules/installation-initializing.adoc
+++ b/modules/installation-initializing.adoc
@@ -513,15 +513,14 @@ For `platform.gcp.network`, specify the name for the existing Google VPC. For `p
 endif::gcp+restricted[]
 
 ifdef::ibm-power-vs+restricted[]
-.. Define the network and subnets for the VPC to install the cluster in under the parent `platform.powervs` field:
+.. Define the network for the VPC to install the cluster in under the parent `platform.powervs` field:
 +
 [source,yaml]
 ----
 vpcName: <existing_vpc>
-vpcSubnets: <vpcSubnet>
 ----
 +
-For `platform.powervs.vpcName`, specify the name for the existing {ibm-cloud-name}. For `platform.powervs.vpcSubnets`, specify the existing subnets.
+For `platform.powervs.vpcName`, specify the name for the existing {ibm-cloud-name} VPC.
 endif::ibm-power-vs+restricted[]
 ifdef::ibm-cloud+restricted[]
 .. Define the network and subnets for the VPC to install the cluster in under the parent `platform.ibmcloud` field:
@@ -587,7 +586,7 @@ Only one VPE can be specified per service.
 ====
 endif::ibm-cloud[]
 ifdef::restricted[]
-.. Optional: Set the publishing strategy to `Internal`:
+.. Set the publishing strategy to `Internal`:
 +
 [source,yaml]
 ----