From: david-sarah <david-sarah@jacaranda.org>
Date: Mon, 7 Jun 2010 06:16:00 +0000 (-0700)
Subject: FTP-and-SFTP.txt: minor technical correction to doc for 'no-write' flag.
X-Git-Url: https://git.rkrishnan.org/simplejson/simplejson/encoder.py.html?a=commitdiff_plain;h=d7d0ae3c2c40c9f8294b955c3b8cde37b667aeaa;p=tahoe-lafs%2Ftahoe-lafs.git

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 281ecfdf..df6c4c0d 100644
--- 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