Suggested by Terry J. Reedy.

``code`` markup is enough to mark command-line fragments or to talk
about a character.  ``'c'`` is still used for actual Python string
objects.  I did a similar change in optparse.rst in r86521.

I’ve also ported two minor changes from the 3.3 version of the file
(removing an unnecessary module name in a class directive, adding a
comma).

I made the doc for the compat alias BadZipfile shorter and used a
directive to document deprecation.

I figured there was no point of talking about zipfile.error (“the old
name” that’s older than the other old name BadZipfile) in the 3.x docs
so I just removed it.

#12266: Fix str.capitalize() to correctly uppercase/lowercase titlecased and cased non-letter characters.

normalization is different between unicode builds, so use a new non-BMP char and add normalization test

This fixes the use of Unicode identifiers outside the BMP in narrow builds.

Changes to crlf originally by Victor Stinner for 3.3, copied to lfcr by
me.  Manually tested.

The line about the test suite will still get printed for changes in
Tools for example, which aren’t covered by the test suite, but it’s not
a big deal IMO.

Fix closes Issue10087 -  fixing the output of calendar display in the html format. Patch by Chris Lambacher. Test Contributed by catherine.

That pipes.quote thinks all non-ASCII characters need to be quoted may
be a bug, but right now I’m committing this test to make sure I haven’t
introduced a behavior change in 3.3 when I simplified the code to use a
regex (in 5966eeb0457d).

Confirm that the prime example is actually correct.  We get so many complaints about a "buggy example" on docs@python, let us hope this cuts them in half at least.