Update README with details on Athena replication issues

Clarified the impact of writing operations on Athena's reading process and provided additional details on handling replication issues. Updated the numbering of the list items accordingly.

Author: iakov-gan

data-exports/README.md

@@ -45,9 +45,9 @@ For customers with additional requirements, an enhanced architecture is availabl
 
 7. When collecting data exports for Linked accounts (not for Management Accounts), you may also want to collect data exports for the Data Collection account itself. In this case, specify the Data Collection account as the first in the list of Source Accounts. Replication is still required to remove metadata.
 
-8. Athena's reading process can be affected by writing operations. When replication arrives, it might fail to update datasets, especially with high volumes of data. In such cases, consider scheduling temporary disabling and re-enabling of the Amazon S3 bucket policy that allows replication. Since exports typically arrive up to three times a day, this temporary deactivation has minimal side effects and the updated data will be available with the next data delivery.
+8. Athena's reading process can be affected by writing operations. This can be an issue, especially in cases when we collect and replicated data from many source accounts. When replication data arrives, it might fail updating quicksight datasets, especially with high volumes of data read and many write processes are running. In such cases, consider scheduling temporary disabling and re-enabling of the Amazon S3 bucket policy that allows replication. Since exports typically arrive up to three times a day, this temporary deactivation has minimal side effects and the updated data will be available with the next data delivery. Use `AddScheduleForBlockingWrite` and `DisableWriteCronSchedule`/`EnableWriteCronSchedule` parameters if you use Data Exports Stack. 
 
-9. (Optional) Secondary bucket replication enables customers to archive data exports, consolidating data exports from multiple AWS Organisations or deploying staging environments (as described below ). 
+10. (Optional) Secondary bucket replication enables customers to archive data exports, consolidating data exports from multiple AWS Organisations or deploying staging environments (as described below). 
 
 ### Using Secondary Replication Bucket
 There can be various situations where customers need to replicate data exports to multiple destinations. One common scenario is a large enterprise with multiple business units, each with one or more AWS organisations. For this large enterprise, the Headquarters requires a consolidated view across all Business Units while simultaneously enabling individual Business Units to have visibility into their own data.