diff --git a/TestGrid.md b/TestGrid.md
index 3270c99..9d42ade 100644
--- a/TestGrid.md
+++ b/TestGrid.md
@@ -11,22 +11,6 @@ The pubgrid also has two critical non-goals
   * The pubgrid is not intended to provide large-scale storage, and it is not intended to be reliable.   Don't store any data in the pubgrid if losing it would cause trouble.
   * Don't view the pubgrid as a free hundreds-of-MB backup service.
 
-## History
-
-Note that the introducer furl has changed recently (as of Feb. 2013).
-
-A version of the pubgrid existed until some time in 2012, when the introducer was lost.  In February of 2013, a new introducer was created, resulting in a change of furl.
-
-It is an interesting philosophical question as to whether the pubgrid with the new introducer is a different grid or not.  If servers that had been connecting to the new introducer are repointed to the new introducer, it can be considered the same grid with a change of introducer, with the property that files from the old grid may still be accessible.
-
-## Cautions
-
-The canonical way to access Tahoe-LAFS grids is to run your own client node.  Having one's own node is necessary for the data that should remain private (plaintext, capabilities) to remain on your computers, while storage nodes provide storage of ciphertext.  However, writing to the publically-writeable test directory (below) means that others can see and change your files.
-
-## Publicly writable test directory
-
-URI:DIR2:ddg5n76x6stjb35psrcn7i3ytu:etbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa .  Note that anyone may view and change this data.
-
 ## How To Connect To The Public Test Grid
 
 The test grid is subject to being updated at random times, so compatibility
@@ -59,6 +43,10 @@ Then run `bin/tahoe start`.
 
 We created a shared public directory: feel free to use it for experimentation -- once your node is up and listening on port 3456, [this URL](http://127.0.0.1:3456/uri/URI%3ADIR2%3Addg5n76x6stjb35psrcn7i3ytu%3Aetbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa/) should give you access to that directory.
 
+## Publicly writable test directory
+
+URI:DIR2:ddg5n76x6stjb35psrcn7i3ytu:etbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa .  Note that anyone may view and change this data.
+
 ## Social Norms
 
 By running a client node, you can store data in the pubgrid.  The storage is provided by people who run storage nodes, and they share disk space and network capacity as a courtesy to the tahoe community in order to help newcomers and promote experimentation.
@@ -73,6 +61,18 @@ Suggested server setup:
 
  * Enable expiration with 1-month lease maximums on your node, to keep it from just filling up.
 
+## History
+
+Note that the introducer furl has changed recently (as of Feb. 2013).
+
+A version of the pubgrid existed until some time in 2012, when the introducer was lost.  In February of 2013, a new introducer was created, resulting in a change of furl.
+
+It is an interesting philosophical question as to whether the pubgrid with the new introducer is a different grid or not.  If servers that had been connecting to the new introducer are repointed to the new introducer, it can be considered the same grid with a change of introducer, with the property that files from the old grid may still be accessible.
+
+## Cautions
+
+The canonical way to access Tahoe-LAFS grids is to run your own client node.  Having one's own node is necessary for the data that should remain private (plaintext, capabilities) to remain on your computers, while storage nodes provide storage of ciphertext.  However, writing to the publically-writeable test directory (below) means that others can see and change your files.
+
 ## Other Public Volunteer Grids
 
  * [VolunteerGrid2](http://www.bigpig.org/) **(Discontinued)**