FTP-and-SFTP.txt: minor technical correction to doc for 'no-write' flag.

diff --git a/docs/frontends/FTP-and-SFTP.txt b/docs/frontends/FTP-and-SFTP.txt
index 281ecfdf89123a3ee90942d7e56f3dd5127817ae..df6c4c0dcf133de9f1de37911e79fb22feda9447 100644 (file)
--- a/docs/frontends/FTP-and-SFTP.txt
+++ b/docs/frontends/FTP-and-SFTP.txt
@@ -183,10 +183,10 @@ caps to it will remain valid. (See docs/garbage-collection.txt for how to
 reclaim the space used by files that are no longer needed.)
 
 The 'no-write' metadata field of a directory entry can override this
-behaviour. If the 'no-write' field holds a non-empty string (typically
-"true"), then a permission error will occur when trying to write to the
-file, even if it is in a writeable directory. This does not prevent the
-directory entry from being unlinked or replaced.
+behaviour. If the 'no-write' field holds a true value, then a permission
+error will occur when trying to write to the file, even if it is in a
+writeable directory. This does not prevent the directory entry from being
+unlinked or replaced.
 
 When using sshfs, the 'no-write' field can be set by clearing the 'w'
 bits in the Unix permissions, for example using the command