Improved description of remote access and single-file shares

docs/advanced/corner_cases.md

@@ -11,13 +11,13 @@ As a consequence, if the public link is read-only, you won't be able to edit fil
 
 ## Microsoft Office and other Windows applications with single-file shares
 
-If you edit a Microsoft Office document via remote Windows access (e.g. via `\\cernbox-smb`, `\\eosproject-smb`, `\\cernbox-drive`, etc.), most metadata associated to the file, such as the previous versions of the document as well as its permissions if the file was shared as single-file share, are lost each time you save the file.
+If you edit a Microsoft Office document via remote access (e.g. via `\\cernbox-smb`, `\\eosproject-smb`, `\\cernbox-drive`, etc.), both on Windows and on Mac OSes (the latter via the `Connect to server...` option in the Finder), most metadata associated to the file, such as the previous versions of the document as well as its permissions if the file was shared as single-file share, are lost each time you save the file.
 
 This is a consequence of how Microsoft Office manipulates files on save operations, coupled with how metadata information such as shares is stored by CERNBox. Similarly, other Windows applications may exhibit the same behavior. Possible workarounds are:
 
 * Use the online Web editors or the Desktop sync client to edit Microsoft Office files.
 
-* If remote Windows access must be ensured, share the containing folder instead. Note that if remote Windows access is required also for the sharee of your file, you must share the containing folder, otherwise your collaborator won't be able to navigate to the file.
+* If remote native (Windows/Mac) access must be ensured, share the containing folder instead. Note that if remote access is required also for the sharee of your file, you must share the containing folder, otherwise your collaborator won't be able to navigate to the file.
 
 
 ## Git and EOS/CERNBox