From: Zooko Wilcox-O'Hearn Date: Sat, 5 Oct 2013 03:29:00 +0000 (+0000) Subject: fix small issues in formatting X-Git-Tag: allmydata-tahoe-1.10.1a1~215^2 X-Git-Url: https://git.rkrishnan.org/using.html?a=commitdiff_plain;h=4e0a8d8d4fe51696ac0b9e59e831d52d649321e8;p=tahoe-lafs%2Ftahoe-lafs.git fix small issues in formatting * fix warning from "rst2html --verbose" by not using the in-line hyperlink syntax. The warning said:: known_issues.rst:261: (INFO/1) Hyperlink target "google chart api" is not referenced. * remove dead code (no-longer-referenced link), thus fixing another warning * change links to relative files to be just $FILENAME instead of file:$FILENAME, which I think will fix the problem of broken links on the trac and github, e.g. the link in https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/known_issues.rst , which ought to go to https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/cautions.rst , but instead goes to file:///cautions.rst --- diff --git a/docs/known_issues.rst b/docs/known_issues.rst index 65610bc5..30918d63 100644 --- a/docs/known_issues.rst +++ b/docs/known_issues.rst @@ -1,7 +1,7 @@  -See also cautions.rst_. +See also `cautions.rst`_. -.. _cautions.rst: file:cautions.rst +.. _cautions.rst: cautions.rst ============ Known Issues @@ -264,9 +264,11 @@ Operations" link on the front welcome page, then through the "Status" column for "map-update" operations (which occur when mutable files, including directories, are read or written). This page contains per-server response times, as lines of text, and includes an image which displays the response -times in graphical form. The image is generated by constructing a URL for the -`Google Chart API `_, which is -then served by the `chart.apis.google.com` internet server. +times in graphical form. The image is generated by constructing a URL for +the `Google Chart API`_, which is then served by the `chart.apis.google.com` +internet server. + +.. _Google Chart API: https://developers.google.com/chart/image/ When you view this page, several parties may learn information about your Tahoe activities. The request will typically include a "Referer" header, @@ -336,9 +338,6 @@ There are three options: could write the corrupted data back into place, making the damage persistent) - -.. _#1654: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654 - ---- Known Issues in Tahoe-LAFS v1.8.2, released 30-Jan-2011