A document that contains the vocabulary of the synapse configuration and the expected values of those named fields would assist in keeping code consistent.

A few things have popped up recently, here and in other branches, so I thought i'd start an issue to collect examples.

I think we should first generate a statement on what the best naming scheme is for things, aim to apply that in future, then come back and deprecate/rename existing options to bring them into line.

Related issues:

• Rename email.riot_base_url config option #3913 (we should be clear this is used as a prefix or a template)
• Document the notif_from config parameter #2326 (we should be clear on what is a template and what isn't)
• Account for slash at the end of url in appservice config file #3523 (we should be consistent in requiring and handling trailing slashes in URLs in our configuration)