Azure Learning Module - Describe the core architectural components of Azure (Unit 5 of 9)

There is an *important note in this module regarding regional pairs in Azure. I feel it has some errors in the writing and also could be worded better (potential error in <error>): Most <directions> (should be "regional pairs?") are paired in two directions, meaning they are the backup for the region that provides a backup for them (West US and East US back each other up). However, some regions, such as West India and Brazil South, are paired in only one direction. In a one-direction pairing, the Primary region does not provide backup for its secondary region. So, even though West India’s secondary region is South India, South India does not rely on West India. West India's secondary region is South India, but South India's secondary region is Central India. Brazil South is unique because it's paired with a region outside of its geography. Brazil South's secondary region is South Central US. The secondary region of South Central US isn't Brazil South.

Also could this not simply be worded as if working in <insert region> regions - work done on secondary region will not be backed up to the primary, as seen in bi-directional regional pairs.