Various grammar and typos

docs/ocis/adr/0013-locking.md

@@ -44,15 +44,15 @@ The CS3org WOPI server creates a `.sys.wopilock.<filename>.` and `.~lock.<filena
 
 **File based locking is bad**, because:
 
-- lock files should be checked by all partys manipulating files (eg. the WebDAV api)
+- lock files should be checked by all parties manipulating files (e.g. the WebDAV api)
 - lock files can be deleted by everyone
 - you can not lock files in a file-only share (you need a folder share to create a lock file besides the original file)
 
-If we have file based locks, we can also sync them with eg. the Desktop Client.
+If we have file based locks, we can also sync them with e.g. the Desktop Client.
 
 **Syncing lock files is good**: because
 
-- native office applications can notice lock files by the WOPI server and vice versa (Libre Office also creates `.lock.<filename>#` files)
+- native office applications can notice lock files by the WOPI server and vice versa (LibreOffice also creates `.lock.<filename>#` files)
 
 **Syncing lock files is bad**, because:
 
@@ -70,7 +70,7 @@ We remove or disable the file based locking of the CS3org WOPI server.
 
 **No locking is bad**, because:
 
-- merging changes from different versions is a pain, since there is no way to calculate differences for most of the files (eg. docx or xlsx files)
+- merging changes from different versions is a pain, since there is no way to calculate differences for most of the files (e.g. docx or xlsx files)
 - no locking breaks the WOPI specs, as the CS3 WOPI server won't be capable to honor the WOPI Lock related operations
 
 ### CS3 API locking
@@ -78,7 +78,7 @@ We remove or disable the file based locking of the CS3org WOPI server.
 - Add CS3 API for resource (files, directories) locking, unlocking and checking locks
   - locking always with timeout
   - lock creation is a "create-if-not-exists" operation
-  - locks need to have arbitrary metadata (eg. the CS3 WOPI server is stateless by storing information on / in the locks)
+  - locks need to have arbitrary metadata (e.g. the CS3 WOPI server is stateless by storing information on / in the locks)
 - Implement WebDAV locking using the CS3 API
 - Implement Locking in storage drivers
 - Change CS3 WOPI server to use CS3 API locking mechanism
@@ -89,7 +89,7 @@ We remove or disable the file based locking of the CS3org WOPI server.
 - you can lock files on the actual storage (if the storage supports that -> storage driver dependent)
 - you can lock files in ownCloud 10 when using the ownCloudSQL storage driver in the migration deployment (but oC10 Collabora / OnlyOffice also need to implement locking, to fully leverage that)
 - clients can get the lock information via the api without ignoring / hiding lock file changes
-- clients can use the lock information to lock the file in their context (eg. via some file explorer integration)
+- clients can use the lock information to lock the file in their context (e.g. via some file explorer integration)
 
 **CS3 API locking is bad**, because: