diff --git a/error-handling-mailbox-uploads.md b/error-handling-mailbox-uploads.md
index d7d3860..67e6a16 100644
--- a/error-handling-mailbox-uploads.md
+++ b/error-handling-mailbox-uploads.md
@@ -3,13 +3,18 @@ Circumstances that could cause messages to be lost:
 - app shutdown
 - app crash
 - device crash
-during the messages and acks are being written to a file
 
-If this happens, that it means that we cannot be sure that the messages/acks are written to the file correctly.  
+## Errors while the messages and acks are being written to a file
+
+If this happen it means that we cannot be sure that the messages/acks are written to the file correctly.  
+
+Q: How to know the precise moment when the messages are being written to a file? Is there anything visible on screen to indicate that? 
+A: no
+
+Q: is there another way that the tester can know exactly when the messages are bieng written to a file? 
+A: yes, a log file - **but TBD how and where it is and what to look for**
 
-How to know the precise moment when the messages are being written to a file? Is there anything visible on screen to indicate that? 
 
-How to know, as a user, if the file is sent and thus which messages were sent correctly or received correctly by the mailbox (own or contact's in case that the writer doesn't have one)?  This would be necessary to know, so we can check that any messages not delivered correctly still show in Briar mailbox as 'not sent' and can still be re-sent?
 
 This can include scenarios: 
 - Sender sending a message file to own mailbox, when mailbox is online or when it is offline, recipient can come online before the mailbox returns online, or they cancoem online after the mailbox has returned online.