Changes between Version 5 and Version 6 of Tutorial

Timestamp:

2010-08-05T03:06:44Z (14 years ago)

Author:

terrell

Comment:

typos and grammar

Tutorial

@@ -48 +48 @@
 now Tahoe is installed \o/
 
-= Instanciate the nodes =
+= Instantiate the nodes =
 
 So, after reading running.html, configuration.txt and architecture.txt, we'll first 
@@ -65 +65 @@
 }}}
 Then we copy that last string we got from 'cat', and paste it in tahoe.cfg,
-as follows (edit it using your favorite editor, mine is vim) :
+as follows :
 {{{
  vm2% vim ~/.tahoe/tahoe.cfg
@@ -96 +96 @@
 myuser    5360  1.2  7.4 158820 28348 ?        S<   02:13   0:00 /usr/bin/python /usr/bin/twistd -y tahoe-client.tac --logfile logs/twistd.log
 }}}
-and you shall see an output that looks alike. If not, tahoe failed to start.
-You've got to check ~/.tahoe/logs/ what got wrong.
+and you should see output that looks similar. If not, tahoe failed to start.
+You've got to check ~/.tahoe/logs/ to see what went wrong.
 
 = Configure the nodes =
@@ -130 +130 @@
 }}}
 
-Then get your favorite browser and browse to the following URLs, you
-should get pages similar to the ones below
+Then browse to the following URLs and you should get pages similar to the ones below
 
   * http://172.16.23.1:3456/
@@ -142 +141 @@
 [[Image(http://tahoe-lafs.org/trac/tahoe-lafs/attachment/wiki/Tutorial/172.16.23.130_3456_1.png)]]
 
-Now it's time to be able to store something on the grid, as
-the whole purpose of Tahoe-LAFS, and thus of this tutorial is
-to get a grid to store files.
+Now it's time to be able to store something on the grid :
 
 On host and vm2, edit again ~/.tahoe/tahoe.cfg and modify it
@@ -155 +152 @@
  32 enabled = true
  33 readonly = false
- 34 reserved_space = 1GB # here you tell the storage server how much space you would like to use
+ 34 reserved_space = 1GB # here you tell the storage server how much disk space it cannot use
 ------------->8---------------------->8----------------
  vm2% tahoe restart
@@ -178 +175 @@
 = File capabilities ? =
 
-Now it's time for a bit of litterature. File capabilities are unique "keys"
-associated with the files. It's used internally by Tahoe-LAFS to identify
+Now it's time for a bit of literature. File capabilities are unique "keys"
+associated with the files. They are used internally by Tahoe-LAFS to identify
 every file, and used as an URL to locate the file.
 
@@ -188 +185 @@
 For mutable files, there are read-only and read-write capabilities.
 A read-only capability will point to a version of a file. A read-write
-capability represant the ability to read the file, the ability to write 
+capability represent the ability to read the file and the ability to write 
 a new version of a file.
 
@@ -198 +195 @@
 = Access your shares =
 
-You can store and access files on Tahoe-LAFS using a lot of 
-different ways. The fatest is to either use the Web UI, or
-the CLI though you need to remember the caps of the files.
-
-Using the WUI is straight forward, connect to a storage client,
+You can store and access files on Tahoe-LAFS in many 
+different ways. The fastest is to either use the Web UI (WUI), or
+the command line (CLI) though you need to know the caps of the files.
+
+Using the WUI is straightforward: connect to a storage client,
 use the forms to add/get/remove files and directories. Just
-always remember that once you created a directory, you need to
-save the file's URI, or you won't be able to find it again later
-on.
+always remember that once you create a directory, you need to
+save the directory's URI, or you won't be able to find it again.
 
 == Using the CLI ==
 
 The CLI behaves mostly like a standard shell, with all
-commands prefixed by 'tahoe', the same way version control
-system work.
+commands prefixed by 'tahoe'.
 
 If you execute for the first time :
@@ -231 +226 @@
 }}}
 
-What happens here is that the Tahoe client tries to connect to the URL 
+What happens here is that the Tahoe-LAFS client tries to connect to the URL 
 given in the ~/.tahoe/node.url file. So, you need to edit ~/.tahoe/node.url
 {{{