Update continuous-backup-restore-introduction.md

Fix for multiregion write support.

Author: kanshiG

articles/cosmos-db/continuous-backup-restore-introduction.md

@@ -48,25 +48,25 @@ All the writes that are performed on the [hub region](multi-region-writes.md#hub
 To summarize, the restore process only restores the entities that are confirmed with conflict resolution timestamp from the hub region.  
 
 > [!NOTE]
-> More information about multi write region accounts can be found [here](multi-region-writes.md#hub-region), hub region is the first region in the portal. 
+> This feature is in preview and suitable for non production workloads. More information about multi write region accounts and hub region concept can be found [here](multi-region-writes.md#hub-region), hub region is the first region in the portal. In preview period, restore in hub region is supported.
 
 ### What isn't restored for Multi region write account restores (preview)? 
-The mutations that are yet to be confirmed by the restore timestamp aren't restored. 
-The collections with custom conflict resolution policy are reset to last writer wins based on timestamp. 
+
+- The mutations that are yet to be confirmed by the restore timestamp aren't restored.
+- The collections with custom conflict resolution policy are reset to last writer wins based on timestamp. 
 
 Example: 
 Given a multi-write region account with two regions East us and West us, out of which East US is the hub region, consider the following sequence of events: 
-
-In this scenario, if the restore timestamp is T3, only entity1 is restored. Entity2 hasn't been confirmed by hub region by T3. Only if the restore timestamp > T4, the entity2 will be restored. 
-T1: Client writes a document Doc1 to East US. (Since East US is the hub region, the write is immediately confirmed)  
-T2: Client writes a document Doc2 to West US.
-T3: West US sends Doc2 to East US for confirmation.
-T4: East US receives Doc2, it confirms the document, and sends of Doc2 back to West US.
-T5: West US receives confirmed Doc2.
+- T1: Client writes a document Doc1 to East US. (Since East US is the hub region, the write is immediately confirmed)
+- T2: Client writes a document Doc2 to West US.
+- T3: West US sends Doc2 to East US for confirmation.
+- T4: East US receives Doc2, it confirms the document, and sends of Doc2 back to West US.
+- T5: West US receives confirmed Doc2.
 
 In this scenario, if the restore timestamp provided is T3, only Doc1 will get restored. Doc2 hasn't been confirmed by hub by T3. Only if the restore timestamp > T4, the doc2 will get restored.  
+
 > [!NOTE]
-> Restore in hub region is supported in public preview. 
+> The feature of Multi-region write-region support for continuous backup is in preview and suitable for non-production workloads. In preview period, restore in hub region is supported.