Browse Source

docs: organize the directory, #656

pull/658/head
Zach Ramsay 7 years ago
parent
commit
b46da19b74
14 changed files with 14 additions and 14 deletions
  1. +1
    -1
      docs/app-architecture.rst
  2. +11
    -11
      docs/specification.rst
  3. +0
    -0
      docs/specification/block-structure.rst
  4. +0
    -0
      docs/specification/byzantine-consensus-algorithm.rst
  5. +0
    -0
      docs/specification/configuration.rst
  6. +0
    -0
      docs/specification/fast-sync.rst
  7. +0
    -0
      docs/specification/genesis.rst
  8. +1
    -1
      docs/specification/light-client-protocol.rst
  9. +0
    -0
      docs/specification/merkle.rst
  10. +0
    -0
      docs/specification/rpc.rst
  11. +0
    -0
      docs/specification/secure-p2p.rst
  12. +0
    -0
      docs/specification/validators.rst
  13. +0
    -0
      docs/specification/wire-protocol.rst
  14. +1
    -1
      docs/using-tendermint.rst

+ 1
- 1
docs/app-architecture.rst View File

@ -58,7 +58,7 @@ Tendermint Core RPC
The concept is that the ABCI app is completely hidden from the outside
world and only communicated through a tested and secured `interface
exposed by the tendermint core <./rpc.html>`__. This interface
exposed by the tendermint core <./specification/rpc.html>`__. This interface
exposes a lot of data on the block header and consensus process, which
is quite useful for externally verifying the system. It also includes
3(!) methods to broadcast a transaction (propose it for the blockchain,


+ 11
- 11
docs/specification.rst View File

@ -7,14 +7,14 @@ Here you'll find details of the Tendermint specification. See `the spec repo <ht
.. toctree::
:maxdepth: 2
block-structure.rst
byzantine-consensus-algorithm.rst
configuration.rst
fast-sync.rst
genesis.rst
light-client-protocol.rst
merkle.rst
rpc.rst
secure-p2p.rst
validators.rst
wire-protocol.rst
specification/block-structure.rst
specification/byzantine-consensus-algorithm.rst
specification/configuration.rst
specification/fast-sync.rst
specification/genesis.rst
specification/light-client-protocol.rst
specification/merkle.rst
specification/rpc.rst
specification/secure-p2p.rst
specification/validators.rst
specification/wire-protocol.rst

docs/block-structure.rst → docs/specification/block-structure.rst View File


docs/byzantine-consensus-algorithm.rst → docs/specification/byzantine-consensus-algorithm.rst View File


docs/configuration.rst → docs/specification/configuration.rst View File


docs/fast-sync.rst → docs/specification/fast-sync.rst View File


docs/genesis.rst → docs/specification/genesis.rst View File


docs/light-client-protocol.rst → docs/specification/light-client-protocol.rst View File


docs/merkle.rst → docs/specification/merkle.rst View File


docs/rpc.rst → docs/specification/rpc.rst View File


docs/secure-p2p.rst → docs/specification/secure-p2p.rst View File


docs/validators.rst → docs/specification/validators.rst View File


docs/wire-protocol.rst → docs/specification/wire-protocol.rst View File


+ 1
- 1
docs/using-tendermint.rst View File

@ -117,7 +117,7 @@ Configuration
-------------
Tendermint uses a ``config.toml`` for configutation. For details, see
`the documentation <./configuration.html>`__.
`the documentation <./specification/configuration.html>`__.
Notable options include the socket address of the application
(``proxy_app``), the listenting address of the tendermint peer


Loading…
Cancel
Save