Add diagram

File-Manager-and-Sync.md

@@ -7,6 +7,9 @@ You should see KeePassDX as a file editor and not a file manager. Links in the l
 # Native synchronization
 
 Native synchronization of KeePass files makes it possible to update the data of the same file opened and modified from two places at the same time.
+
+![file_sync](https://user-images.githubusercontent.com/19224038/151351073-402307fc-966f-442f-a528-f0dd809e2e97.png)
+
 Synchronization can therefore be seen as a two-step action:
  - **Data recovery from a predefined shared location.** It is not up to KeePassDX to handle this step, because the architecture of the Android system is built in such a way that a dedicated application manages to send and receive the files and then propose them through a [URI](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier). Here, KeePassDX is only an editor and many people blame it when most of the file synchronization problems are caused by the cloud application used because it doesn't handle file conflicts or has caching problems. See the [table below](https://github.com/Kunzisoft/KeePassDX/wiki/File-Manager-and-Sync#compatibility) for more explanations. **_The creation of a new file app fully compatible with open protocols and cloud clients is under study. (Dedicated app sync project : https://github.com/Kunzisoft/FileSync)_**
  - **The merge of the updated data.** When the URI provides new data, KeePassDX is able to merge the currently open data with this retrieved data. _(from version 3.2.0)_