archimage

Author: mletalie

NewPSC.png

@@ -6,7 +6,7 @@
 [id="osd-gcp-architecture_{context}"]
 = Private {product-title} on {GCP} architecture on public and private networks
 
-You can customize the access patterns for your API service endpoint and Red Hat SRE management by choosing one of the following network configuration types:
+You can customize the access patterns for your API server endpoint and Red Hat SRE management by choosing one of the following network configuration types:
 
 * Private cluster with Private Service Connect (PSC).
 * Private cluster without PSC

images/NewPSC.png

@@ -20,15 +20,15 @@ The PSC architecture includes producer services and consumer services. Using PSC
 
 The following image depicts how Red HAT SREs and other internal resources access and support clusters created using PSC.
 
-* A unique PSC Service Attachment is created for each OSD cluster in the customer GCP project. The PSC Service Attachment points to the cluster API server load balancer created in the customer GCP project.
+* A unique PSC service attachment is created for each OSD cluster in the customer GCP project. The PSC service attachment points to the cluster API server load balancer created in the customer GCP project.
 
-* Similar to Service Attachments, a unique PSC Service Endpoint is created in the Red Hat Management GCP project for each OSD cluster.
+* Similar to service attachments, a unique PSC endpoint is created in the Red Hat Management GCP project for each OSD cluster.
 
-* A dedicated subnet for GCP Private Service Connect is created in the cluster’s network within the customer GCP project. This is a special subnet type where the producer services are published via PSC Service Attachments. This subnet is used to Source NAT (SNAT) incoming requests to the cluster API server. Additionally, the PSC subnet must be within the Machine CIDR range and cannot be used in more than one Service Attachment.
+* A dedicated subnet for GCP Private Service Connect is created in the cluster’s network within the customer GCP project. This is a special subnet type where the producer services are published via PSC service attachments. This subnet is used to Source NAT (SNAT) incoming requests to the cluster API server. Additionally, the PSC subnet must be within the Machine CIDR range and cannot be used in more than one service attachment.
 
-* Red Hat internal resources and SREs access private OSD clusters using the connectivity between a PSC Endpoint and Service Attachment. Even though the traffic transits multiple VPC networks, it remains entirely within Google Cloud.
+* Red Hat internal resources and SREs access private OSD clusters using the connectivity between a PSC endpoint and service attachment. Even though the traffic transits multiple VPC networks, it remains entirely within Google Cloud.
 
-* Access to PSC Service Attachments is possible only via the Red Hat Management project.
+* Access to PSC service attachments is possible only via the Red Hat Management project.
 
 .PSC architecture overview
-image::psc-arch-overview.png[PSC architecture overview]
+image::psc_arch_2.png[PSC architecture overview]