Various typography, code and style adherence, and small fixes

[alimony]

I have a large number of small fixes in a branch of my fork, and I am wondering how I should do pull requests for these.

Should I do one huge pull request for all my fixes, or one per changed page of the site, or something else?

I guess I want to open pull requests early, so incremental changes can happen, and to avoid any double work if someone else out there is doing the same fixes in their own fork.

But on the other hand, I don't want to spam you with a large number of requests :)

[rmurphey]

I'd suggest opening a "content fixes" PR assuming that they're all content fixes, not content changes. The only place this gets potentially tricky is with code, where a "fix" might actually be a "change" (see e.g. #215). Long story short, if you're very confident that they're all just corrections, I'd say one pull request is fine :)

[ajpiano]

Right on @alimony - for small fixes it's better to do it all in one PR, as we'd just squash the multiple PRs into a single fix. As @rmurphey indicated, any "substantive" change should be in its own PR so it can be evaluated on its merits.

Big +1 to getting small fixes in ASAP - I've been merging and pushing live all the typo fixes you and others have been supplying (thanks) as soon as I can so that people browsing the site don't notice and report already-fixed errors.

[alimony]

To have some sort of structure, I've decided to do these changes one section at the time, opening a new pull request for each one. I will keep code style adherence fixes in its own commit, and generally try to put groups of fixes into separate commits for easy overview. Hope this works for you.