Merge pull request #754 from tendermint/improve-docs

add tm-migrator to docs

docs/ecosystem.rst

@@ -115,3 +115,8 @@ Deployment Tools
 See `deploy testnets <./deploy-testnets.html>`__ for information about all the tools built by Tendermint. We have Kubernetes, Ansible, and Terraform integrations.
 
 Cloudsoft built `brooklyn-tendermint <https://github.com/cloudsoft/brooklyn-tendermint>`__ for deploying a tendermint testnet in docker continers. It uses Clocker for Apache Brooklyn.
+
+Dev Tools
+---------
+
+For upgrading from older to newer versions of tendermint and to migrate your chain data, see `tm-migrator <https://github.com/hxzqlh/tm-tools>`__ written by @hxzqlh.

docs/getting-started.rst

@@ -153,11 +153,10 @@ The result should look like:
       }
     }
 
-Again, the ``112`` is the type-byte. Note the ``value`` in the result
+Note the ``value`` in the result (``61626364``); this is the
-(``61626364``); this is the hex-encoding of the ASCII of ``abcd``. You
+hex-encoding of the ASCII of ``abcd``. You can verify this in
-can verify this in a python shell by running
+a python shell by running ``"61626364".decode('hex')``. Stay
-``"61626364".decode('hex')``. Stay tuned for a future release that makes
+tuned for a future release that makes this output more human-readable.
-this output more human-readable ;).
 
 Now let's try setting a different key and value:
 

docs/using-tendermint.rst

@@ -386,3 +386,11 @@ the listening addresses of the various sockets don't conflict.
 Additionally, you must set ``addrbook_strict=false`` in the
 ``config.toml``, otherwise Tendermint's p2p library will deny making
 connections to peers with the same IP address.
+
+Ugrading
+~~~~~~~~
+
+The tendermint development cycle includes a lot of breaking changes. Upgrading from
+an old version to a new version usually means throwing away the chain data. Try out
+the `tm-migrate <https://github.com/hxzqlh/tm-tools>`__ tool written by @hxqlh if
+you are keen to preserve the state of your chain when upgrading to newer versions.