@link2xt, you are right, I was far too vague. I should have written a list of examples. If a bunch of changes are about to be implemented I should probably not make a swarm of obsolescent suggestions?
Propinquitous information, info that is accessible right where you are making a decision about a setting, seems more likely to be used. I did read through the FAQ, at least twice, and large parts of the blog and SecureJoin and Autocrypt docs, before installing a client, but that is probably not typical. And I did still find myself confused, and I found I’d forgotten some things. The interface is more complex now than it was then. Dividing it into subject-matter setions should help, though.
I’d think info integrated with the settings might also be easier to maintain than a separate FAQ, but perhaps I am wrong. What would be the easiest format?
An earlier specific suggestion simply linked a term (“read receipt”) to the relevant Wikipedia article, which does outsource the maintenance. 