Update files

* Update documentation

docs/application-security.md

@@ -71,9 +71,9 @@ When using the OneDrive Client for Linux, the above authentication scopes will b
 
 This is similar to the Microsoft Windows OneDrive Client:
 
-![Linux Authentication to Microsoft OneDrive](./puml/onedrive_windows_authentication.png)
+![Windows Authentication to Microsoft OneDrive](./puml/onedrive_windows_authentication.png)
 
-In a business environment, where IT Staff need to 'approve' the OneDrive Client for Linux, can do so knowing that the client is safe to use. The only concernt that the IT Staff should have is how is the client device, where the OneDrive Client for Linux is running, is being secured, as in a corporate setting, Windows would be controlled by Active Directory and applicable Group Policy Objects (GPO's) to ensure the security of corporate data on the client device. It is out of scope for this client to handle how Linux devices are being secure.
+In a business setting, IT staff who need to authorise the use of the OneDrive Client for Linux in their environment can be assured of its safety. The primary concern for IT staff should be securing the device running the OneDrive Client for Linux. Unlike in a corporate environment where Windows devices are secured through Active Directory and Group Policy Objects (GPOs) to protect corporate data on the device, it is beyond the responsibility of this client to manage security on Linux devices.
 
 ## Configuring read-only access to your OneDrive data
 In some situations, it may be desirable to configure the OneDrive Client for Linux totally in read-only operation.

docs/puml/database_schema.puml

@@ -0,0 +1,37 @@
+@startuml
+
+class item {
+    driveId: TEXT
+    id: TEXT
+    name: TEXT
+    remoteName: TEXT
+    type: TEXT
+    eTag: TEXT
+    cTag: TEXT
+    mtime: TEXT
+    parentId: TEXT
+    quickXorHash: TEXT
+    sha256Hash: TEXT
+    remoteDriveId: TEXT
+    remoteId: TEXT
+    deltaLink: TEXT
+    syncStatus: TEXT
+    size: TEXT
+}
+
+note right of item::driveId
+  PRIMARY KEY (driveId, id)
+  FOREIGN KEY (driveId, parentId) REFERENCES item
+end note
+
+item --|> item : parentId
+
+note "Indexes" as N1
+note left of N1
+  name_idx ON item (name)
+  remote_idx ON item (remoteDriveId, remoteId)
+  item_children_idx ON item (driveId, parentId)
+  selectByPath_idx ON item (name, driveId, parentId)
+end note
+
+@enduml