From b2af38a2c80adbb0cb5b8cd99194c01d81d953b3 Mon Sep 17 00:00:00 2001
From: Peter <pfeerick@users.noreply.github.com>
Date: Thu, 31 Oct 2019 18:41:40 +1000
Subject: [PATCH] Re-wording of ATOMIC_FS_UPDATE documenation
---
doc/ota_updates/readme.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ota_updates/readme.rst b/doc/ota_updates/readme.rst
index f5c76f0d2c..4d717df59f 100644
--- a/doc/ota_updates/readme.rst
+++ b/doc/ota_updates/readme.rst
@@ -646,7 +646,7 @@ Update process - memory view
- the new sketch is now copied "over" the old one.
- the new sketch is started.
-By default, filesystem updates are overriding the target flash directly. In order to use the same two step process set the `ATOMIC_FS_UPDATE` flag.
+By default, OTA filesystem updates overwrite the target flash directly. This can lead to the file system being corrupted if there is a power outage during the update process. In order to use the same two step process that is used for OTA application firmware updates, set the `ATOMIC_FS_UPDATE` flag. Note that you will need to have enough unused space for the new filesystem image to be stored, hence is why this is not the default behaviour.
.. figure:: update_memory_copy.png
:alt: Memory layout for OTA updates