diff --git a/SftpFrontend.md b/SftpFrontend.md
index 13befd5..2b790e8 100644
--- a/SftpFrontend.md
+++ b/SftpFrontend.md
@@ -7,7 +7,7 @@ See source:docs/frontends/FTP-and-SFTP.txt for how to enable and set up the SFTP
 
 Before uploading a file to a Tahoe filesystem, the whole file has to be available. This means that the upload can only start when the file has been closed in the SFTP session. Particularly when writing large files, the client may time out between sending the close request and receiving the response (ticket #1041). This is known to be a problem for at least the WinSCP client, which has a close timeout of 15 seconds.
 
-Since Tahoe uses capability access control rather than Unix-style permissions, the permission bits seen by SFTP clients are handled differently than on a local POSIX filesystem: they are only an approximation chosen to avoid confusing client programs. In particular the 'user', 'group' and 'world' permissions on a Tahoe file will always be the same. It is possible to clear all of the 'w' bits on a file, which will prevent that file from being opened for writing, but note that its directory entry can still be replaced via a write cap to the directory.
+Since Tahoe uses capability access control rather than Unix-style permissions, the permission bits seen by SFTP clients are only an approximation chosen to avoid confusing client programs. In particular the 'user', 'group' and 'world' permissions on a Tahoe file will always be the same. It is possible to clear all of the 'w' bits on a file, which will prevent that file from being opened for writing, but note that its directory entry can still be replaced via a write cap to the directory.
 
 
 ### sshfs