docs: fix helper.txt to describe new config style

diff --git a/docs/architecture.txt b/docs/architecture.txt
index fc2e67c5e296212076a7585e40ff67925d110d38..5119f442b39ea2406fa0656edb695c42cf9e54ca 100644 (file)
--- a/docs/architecture.txt
+++ b/docs/architecture.txt
@@ -1,5 +1,7 @@
 
-   Allmydata "Tahoe" Architecture
+   Tahoe-LAFS Architecture
+
+(See the docs/specifications directory for more details.)
 
 OVERVIEW
 

diff --git a/docs/helper.txt b/docs/helper.txt
index 3be57960b76eb874d28daaae25e875d953b8f397..b78f77421b2c9b1fa73a4a6e124e0ef414e0c035 100644 (file)
--- a/docs/helper.txt
+++ b/docs/helper.txt
@@ -65,10 +65,10 @@ What sorts of machines are good candidates for running a helper?
    much free disk space as there will be simultaneous uploads. When an upload
    is interrupted, that space will be used for a longer period of time.
 
-To turn a Tahoe client node into a helper (i.e. to run a helper service in
-addition to whatever else that node is doing), just create a file in your
-node's base directory named "run_helper", and put any non-empty string in it.
-Then restart the node:
+To turn a Tahoe-LAFS node into a helper (i.e. to run a helper service in
+addition to whatever else that node is doing), edit the tahoe.cfg file in your
+node's base directory and set "enabled = true" in the section named 
+"[helper]". Then restart the node:
 
  echo "yes" >$BASEDIR/run_helper
  tahoe restart $BASEDIR