Subheader settings: Names of keys in documentation and implementation differ (subheader vs. subHeader)

[jpilkahn]

Preliminary note

<3 the extension.
Also, the source reads well.

Here's the bug

The 4 options pertaining to the subheader are documented in the README (and hence by proxy also in the in-app manual) as if "subheader" were two words. Here, the options are called subHeader<OptionName>, whereas the actual implementation is treating it as one word while parsing (i.e.looking for keys named subheader<OptionName>).

• package.json#L112
• package.json#L119
• package.json#L128
• package.json#L138
• README

[stackbreak]

@jpilkahn, Thank you! Fixed.