Update Session Consistency Level explanation

I think a proper explanation of the illustration, should mention the West US 2 Writer and the "East US 2" Reader that are using the same session token, in order to emphasise the concept of having a session consistency level.
p.s. is it  just a typo ?

Author: DarthMouayed

articles/cosmos-db/consistency-levels.md

@@ -97,7 +97,7 @@ Clients outside of the session performing writes will see the following guarante
 - Consistency for clients writing to multiple regions for an account with multiple write regions = [Eventual](#eventual-consistency)
 - Consistency for clients using the [Azure Cosmos DB integrated cache](integrated-cache.md) = [Eventual](#eventual-consistency)
 
-  Session consistency is the most widely used consistency level for both single region as well as globally distributed applications. It provides write latencies, availability, and read throughput comparable to that of eventual consistency but also provides the consistency guarantees that suit the needs of applications written to operate in the context of a user. The following graphic illustrates the session consistency with musical notes. The "West US 2 writer" and the "West US 2 reader" are using the same session (Session A) so they both read the same data at the same time. Whereas the "Australia East" region is using "Session B" so, it receives data later but in the same order as the writes.
+  Session consistency is the most widely used consistency level for both single region as well as globally distributed applications. It provides write latencies, availability, and read throughput comparable to that of eventual consistency but also provides the consistency guarantees that suit the needs of applications written to operate in the context of a user. The following graphic illustrates the session consistency with musical notes. The "West US 2 writer" and the "East US 2 reader" are using the same session (Session A) so they both read the same data at the same time. Whereas the "Australia East" region is using "Session B" so, it receives data later but in the same order as the writes.
 
   :::image type="content" source="media/consistency-levels/session-consistency.gif" alt-text="Illustration of session consistency level":::