Apply updated phases diagrams with right-facing direction of Reads ar… (#143)

* Apply updated phases diagrams with right-facing direction of Reads arrows

* Modified Ph 4 diagram with Reads arrows going in right direction

Author: johnsmartco

docs-src/zdm-core/modules/migrate/images/migration-phase1ra.png

@@ -7,7 +7,7 @@ This topic explains how you can configure the {zdm-proxy} to route all reads to
 
 Illustrated view of this phase:
 
-image::{imagesprefix}migration-phase4.png[Phase 4 diagram shows read routing on ZDM Proxy was switched to Target.]
+image::{imagesprefix}migration-phase4ra.png[Phase 4 diagram shows read routing on ZDM Proxy was switched to Target.]
 
 For illustrations of all the migration phases, see the xref:introduction.adoc#_migration_phases[Introduction].
 

docs-src/zdm-core/modules/migrate/images/migration-phase2ra.png

@@ -17,7 +17,7 @@ Now we're ready to perform Phase 5, in which we will configure our client applic
 
 Illustrated view of this phase:
 
-image::{imagesprefix}migration-phase5.png[Phase 5 diagram shows apps no longer using proxy and instead connected directly to Target.]
+image::{imagesprefix}migration-phase5ra.png[Phase 5 diagram shows apps no longer using proxy and instead connected directly to Target.]
 
 For illustrations of all the migration phases, see the xref:introduction.adoc#_migration_phases[Introduction].
 

docs-src/zdm-core/modules/migrate/images/migration-phase3ra.png

@@ -7,7 +7,7 @@ In this phase, you can optionally enable asynchronous dual reads. The idea is to
 
 Illustrated view of this phase:
 
-image::{imagesprefix}migration-phase3.png[Phase 3 diagram shows optional step enabling async dual reads to test performance of Target.]
+image::{imagesprefix}migration-phase3ra.png[Phase 3 diagram shows optional step enabling async dual reads to test performance of Target.]
 
 For illustrations of all the migration phases, see the xref:introduction.adoc#_migration_phases[Introduction].
 

docs-src/zdm-core/modules/migrate/images/migration-phase4ra.png

@@ -53,39 +53,39 @@ image::{imagesprefix}migration-all-phases.png[Migration phases from start to fin
 
 Before we walk through illustrations of each phase, let's look at a pre-migration, high-level view. At this point, your client applications are performing read/write operations with an existing CQL-compatible database. That is, Apache Cassandra, DSE, or Astra DB.  
 
-image::{imagesprefix}pre-migration0.png[Diagram shows existing CQL-compatible environment before migration starts.]
+image::{imagesprefix}pre-migration0ra.png[Diagram shows existing CQL-compatible environment before migration starts.]
 
 Before your migration begins, you'll need to satisfy prerequisites, prepare your environment, and set up the recommended infrastructure.
 
 === Phase 1: Deploy ZDM Proxy and connect client applications
 
 Let's look at Phase 1 of the migration. We'll deploy the ZDM Proxy instances and connect client applications to the proxies. This step activates the dual-write logic. Writes will be "bifurcated" (sent to both Origin and Target), while reads will be executed on Origin only.
 
-image::{imagesprefix}migration-phase1.png[Phase 1 diagram shows deployed ZDM Proxy instances, client app connections to proxies, and Target is setup.]
+image::{imagesprefix}migration-phase1ra.png[Phase 1 diagram shows deployed ZDM Proxy instances, client app connections to proxies, and Target is setup.]
 
 === Phase 2: Migrate data
 
 In this phase, we migrate existing data using {cstar-data-migrator} and/or {dsbulk-migrator}. Validate that the migrated data is correct, while continuing to perform dual writes.
 
-image::{imagesprefix}migration-phase2.png[Phase 2 diagram shows using tools to migrate data from Origin to Target.]
+image::{imagesprefix}migration-phase2ra.png[Phase 2 diagram shows using tools to migrate data from Origin to Target.]
 
 === Phase 3: Async dual reads
 
 In this phase, you can optionally enable asynchronous dual reads. The idea is to test performance and verify that Target can handle your application's live request load before cutting over from Origin to Target.
 
-image::{imagesprefix}migration-phase3.png[Phase 3 diagram shows optional step enabling async dual reads to test performance of Target.]
+image::{imagesprefix}migration-phase3ra.png[Phase 3 diagram shows optional step enabling async dual reads to test performance of Target.]
 
 === Phase 4: Route reads to Target
 
 In this phase, the read routing on the {zdm-proxy} is switched to Target so that all reads are executed on it, while writes are still sent to both clusters. In other words, Target becomes the primary cluster.
 
-image::{imagesprefix}migration-phase4.png[Phase 4 diagram shows read routing on ZDM Proxy was switched to Target.]
+image::{imagesprefix}migration-phase4ra.png[Phase 4 diagram shows read routing on ZDM Proxy was switched to Target.]
 
 === Phase 5: Connect directly to Target
 
 In this phase, you'll move your client applications off the {zdm-proxy} and connect the apps directly to Target. Once that happens, the migration is complete.
 
-image::{imagesprefix}migration-phase5.png[Phase 5 diagram shows apps no longer using proxy and instead connected directly to Target.]
+image::{imagesprefix}migration-phase5ra.png[Phase 5 diagram shows apps no longer using proxy and instead connected directly to Target.]
 
 
 == A fun way to learn: {zdm-product} Interactive Lab