When reading over the sorting howto, I noticed redundancy of the form “the list.sort() method of a list”. Raymond, if you approve the attached patch, please assign back to me. There were no warnings during doc build and no link was broken. Note that :meth:`list.sort` (or :meth:`~list.sort`) does not trigger a link to the doc of the method, since sort is not marked up with a method directive but listed in a table alongside other list and bytearray methods (http://docs.python.org/dev/library/stdtypes#typesseq-mutable). This table is preceded by index-generating markup, but it does not create a target for :meth:`list.sort`; that’s a separate issue. Until it’s solved, the sorting howto could turn the first occurrence of “list” into a link to the right section, using :ref:`typesseq-mutable `, or continue to live without a link to list or list.sort.
You can put in the backslashes before the two periods, but not the other changes. I want the method names to continue to be spelled-out in full so that it is more clear what they are referring to. Even in spoken English, I typically say "list sort" or "sort method of the builtin list type". This helps distinguish it from the sorted() builtin.
Made some tweaks r88358. Sorry, I'm leaving the list.sort references as-is. I consider them to be important in a document that needs to clearly differentiate list.sort from __builtin__.sorted().
