known_issues: update chart-API text, with suggestions from Leif. refs #1942

diff --git a/docs/known_issues.rst b/docs/known_issues.rst
index 88aa88f6e3ef2214980aeae9d4a1b5f93fbfb159..4e349394ac537b0619973e2a197b75cf645c7f7e 100644 (file)
--- a/docs/known_issues.rst
+++ b/docs/known_issues.rst
@@ -279,13 +279,14 @@ buffer overflow. (Note that browsers do not execute scripts inside IMG tags,
 even for SVG images).
 
 In addition, if your Tahoe node connects to its grid over Tor or i2p, but the
-web browser you use to access it does not, then this image link may reveal
-your use of Tahoe to the outside world. It is not recommended to use a
-browser in this way, because other links in Tahoe-stored content would reveal
-even more information (e.g. an attacker could store an HTML file with unique
-CSS references into a shared Tahoe grid, then send your pseudonym a message
-with its URI, then observe your browser loading that CSS file, and thus link
-the source IP address of your web client to that pseudonym).
+web browser you use to access your node does not, then this image link may
+reveal your use of Tahoe (and that grid) to the outside world. It is not
+recommended to use a browser in this way, because other links in Tahoe-stored
+content would reveal even more information (e.g. an attacker could store an
+HTML file with unique CSS references into a shared Tahoe grid, then send your
+pseudonym a message with its URI, then observe your browser loading that CSS
+file, and thus link the source IP address of your web client to that
+pseudonym).
 
 A future version of Tahoe will probably replace the Google Chart API link
 (which was deprecated by Google in April 2012) with client-side javascript