From 62bdf3e2b5ad88c3c2a793909d19920c968cc070 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Thu, 25 Apr 2013 18:39:00 +0000
Subject: [PATCH] edit for clarity

[Imported from Trac: page FAQ, version 93]
---
 FAQ.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/FAQ.md b/FAQ.md
index 24e42e6..ea41e30 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -207,7 +207,7 @@ Practically the following results have been reported: **16Mbps in throughput for
 
 You can read the following section for more details: [Performance](https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Performance).
 
-**<a name="Q30_authorization">Q30:</a> How can I prevent intruders from using my Tahoe-LAFS web-interface? Even without knowing exact object caps they will be able to see stats and upload objects.**
+**<a name="Q30_authorization">Q30:</a> How can I prevent intruders from using my Tahoe-LAFS web-interface? Even without knowing exact object caps they will be able to see statistics and be able to upload objects.**
 
 A: There is no such built-in authorization capability in Tahoe-LAFS. Security is based on secret object caps.
 Meanwhile you can forbid unauthorized access to your Tahoe-LAFS WUI by using firewall (iptables, ipfw etc.) and combining it with proxy-server authorization and redirection (nginx, apache, squid etc.)
\ No newline at end of file