Describe the ledger as part of master The ledger branch has been merged, so the ledger pages no longer carry a banner that calls them upcoming, and the home page and sidebar list the ledger beside the other features. Pages that placed the ledger sporks, endpoints or mint entries on a separate branch now say they are on master and not in release 0.0.8. The note that no genesis comes with the node stays in the text of the ledger pages.
Note where the s3 branch replaces the REST object store The s3 branch drops the S3-style buckets of the REST interface, the --restmaxupload option and the s3data directory in favour of the S3 endpoint on port 52885. The pages keep the facts of the release and point to the endpoint where the branch differs.
Say that the REST token is checked before a body is read
Describe the limits on the body of a REST request
Document the ledger endpoints of the REST interface Add the four /ledger endpoints: the state of the ledger, an account or legacy address, a block, and the submit of a signed transaction. The page lists the fields of each answer, how amounts, hashes and keys are written, the status codes, the body limit and the limit of 16 submits that wait at once.
Document running Hedgehog 0.0.8 Add a page on downloading, verifying, starting and stopping a node, its options, data directory and commands. Mark the gridnode and storage material as arriving after 0.0.8.
Shorten every page to a brief overview Each page now says what the part is, how it works and where the source lives, instead of documenting the implementation in full.
Move the implementation documentation into the wiki Nine pages with a sidebar, and the figures they embed.