<!-- Thank you for your contribution!
Please file this form by replacing the Markdown comments
with your text. If a section needs no action - remove it.
Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
of code collaboration. Positive feedback is represented +1 from committers
and negative is a -1. The -1 also means veto, and needs to be addressed
to proceed. Once there are no objections, the PR can be merged by a
CouchDB committer.
See: http://couchdb.apache.org/bylaws.html#decisions for more info. -->
## Overview
I just gave the Getting Started Guide a go and noticed that some of the
responses and UI elements that are being referred to are out of sync with a
fresh 2.2.0 installation. This PR syncs the document with the values returned /
used.
## Testing recommendations
Run a fresh install of CouchDB 2.2.0, then do what is described in the Getting
Started Guide.
## Checklist
- [x] Documentation is written and is accurate;
- [x] `make check` passes with no errors
- [ ] Update
[rebar.config.script](https://github.com/apache/couchdb/blob/master/rebar.config.script)
with the commit hash once this PR is rebased and merged
[ Full content available at:
https://github.com/apache/couchdb-documentation/pull/335 ]
This message was relayed via gitbox.apache.org for [email protected]
