update docs for 1.10.2 release

[tahoe-lafs/tahoe-lafs.git] / docs / known_issues.rst

diff --git a/docs/known_issues.rst b/docs/known_issues.rst
index 65610bc547090e775825677c884078d0db27ad93..79f51b6014cd9f453094223a6372382f4d72d392 100644 (file)
--- a/docs/known_issues.rst
+++ b/docs/known_issues.rst
@@ -1,7 +1,8 @@
-
-See also cautions.rst_.
+.. -*- coding: utf-8-with-signature -*-
 
-.. _cautions.rst: file:cautions.rst
+See also `cautions.rst`_.
+
+.. _cautions.rst: cautions.rst
 
 ============
 Known Issues
@@ -18,8 +19,8 @@ want to read `the "historical known issues" document`_.
 .. _the "historical known issues" document: historical/historical_known_issues.txt
 
 
-Known Issues in Tahoe-LAFS v1.10, released 01-May-2013
-======================================================
+Known Issues in Tahoe-LAFS v1.10.2, released 30-Jul-2015
+========================================================
 
   *  `Unauthorized access by JavaScript in unrelated files`_
   *  `Disclosure of file through embedded hyperlinks or JavaScript in that file`_
@@ -264,9 +265,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 <https://developers.google.com/chart/image/>`_, 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 +339,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