Fix bad cluster.database in documentation
Summary: This is mistaken.
Test Plan: Careful inspection, grep for other mistakes.
Reviewers: chad, eadler
Reviewed By: eadler
Differential Revision: https://secure.phabricator.com/D15717
I think this was because I was briefly running daemons against a replica database with a bad dataset. Let me know if it happens again, but I know a handful of duplicate / screwed up mail messages went out.
Possibly we should also make that message not echo the whole token. It's not really dangerous in any way that I can come up with, but it would be just as useful to print the first, say, "clr-ukkw...".