Merge pull request #92296 from EricPonvelle/OSDOCS-14351_Update-architecture-diagrams

OSDOCS-14351: Updated the text on some diagrams

Author: EricPonvelle

images/544_OpenShift_ROSA-HCP-and-ROSA-Classic-private.png

@@ -12,14 +12,14 @@ You can create a ROSA with HCP cluster with or without an internet-facing API se
 The worker nodes are deployed in your AWS account and run on your VPC private subnets. You can add additional private subnets from one or more availability zones to ensure high availability. Worker nodes are shared by OpenShift components and applications. OpenShift components such as the ingress controller, image registry, and monitoring are deployed on the worker nodes hosted on your VPC.
 
 .ROSA with HCP architecture
-image::ROSA-HCP-architecture-model.png[ROSA with HCP architecture]
+image::544_OpenShift_ROSA-HCP_architecture-model.png[ROSA with HCP architecture]
 
 [id="rosa-hcp-network-architecture_{context}"]
 == ROSA with HCP architecture on public and private networks
 With ROSA with HCP, you can create your clusters on public or private networks. The following images depict the architecture of both public and private networks.
 
 .ROSA with HCP deployed on a public network
-image::ROSA-HCP-and-ROSA-Classic-public.png[ROSA with HCP deployed on a public network]
+image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-public.png[ROSA with HCP deployed on a public network]
 
 .ROSA with HCP deployed on a private network
-image::ROSA-HCP-and-ROSA-Classic-private.png[ROSA with HCP deployed on a private network]
+image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-private.png[ROSA with HCP deployed on a private network]