From 91d7a31820876ce26b5f83c47ad3468146149cdb Mon Sep 17 00:00:00 2001
From: davidsarah <>
Date: Sun, 12 Dec 2010 06:49:56 +0000
Subject: [PATCH] fix rst links

[Imported from Trac: page SftpFrontend, version 57]
---
 SftpFrontend.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/SftpFrontend.md b/SftpFrontend.md
index def8e63..f21c48a 100644
--- a/SftpFrontend.md
+++ b/SftpFrontend.md
@@ -1,6 +1,6 @@
 The SFTP frontend is a server that optionally runs as part of a gateway node, and provides read/write access to the Tahoe grid via the [SSH File Transfer Protocol](http://en.wikipedia.org/wiki/SSH_file_transfer_protocol).
 
-See [docs/frontends/FTP-and-SFTP.rst (.txt in releases before v1.8.1)](http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.txt) for how to enable and set up the SFTP frontend on a gateway. This page is for compatibility issues with particular SFTP clients, and assumes that you are using Tahoe-LAFS v1.7.0 or later. Please add any more issues that you discover.
+See [docs/frontends/FTP-and-SFTP.rst (.txt in releases before v1.8.1)](http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.rst) for how to enable and set up the SFTP frontend on a gateway. This page is for compatibility issues with particular SFTP clients, and assumes that you are using Tahoe-LAFS v1.7.0 or later. Please add any more issues that you discover.
 
 
 # Security
@@ -20,9 +20,9 @@ In the period after the close but before the upload has finished, the closed fil
 
 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.
 
-See the last section of [docs/frontends/FTP-and-SFTP.rst](http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.txt) for information on how the SFTP frontend treats immutable and mutable files.
+See the last section of [docs/frontends/FTP-and-SFTP.rst](http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.rst) for information on how the SFTP frontend treats immutable and mutable files.
 
-The '`ctime`' and '`mtime`' attributes will always be the same, and are set from the Tahoe `linkmotime` timestamp, which is changed only when the link from the parent directory is modified (see the 'About the metadata' section of [webapi.rst]source:doc/frontends/webapi.rst). These fields are not updated when the contents of a mutable file are changed. The SFTP protocol and the server are able to represent dates up to the year 2106, but some clients may print dates incorrectly after 2037.
+The '`ctime`' and '`mtime`' attributes will always be the same, and are set from the Tahoe `linkmotime` timestamp, which is changed only when the link from the parent directory is modified (see the ['About the metadata' section of webapi.rst](http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/webapi.rst#about-the-metadata)). These fields are not updated when the contents of a mutable file are changed. The SFTP protocol and the server are able to represent dates up to the year 2106, but some clients may print dates incorrectly after 2037.
 
 
 # Unicode filenames