These are minor corrections to the What's New in Python 2.6[b3] doc.

Note: the PEP references are to the headers in What's New, not the
  actual PEPs

- PEP 371: The multiprocessing Package
    - "apply() or apply_async, adding a single request, and map() or
      map_async()" All four function names should link to the Pool
      docs. Currently apply and map link to the docs for the builtins
      of the same name; the other two don't link.

- PEP 3101: Advanced String Formatting
    - In the first example, "uid = 'root'" is not needed

- PEP 3112: Byte Literals
    - In the second example, the value of b should not have a space in
      the middle, i.e. bytearray(b'\xe2\x87\xaf\xe3\x89\x84') instead
      of bytearray(b'\xe2\x87\xaf \xe3\x89\x84')

- Other Language Changes
    - next(*iterator*, [*default*]) - the asterisks are not needed
    - "letting complex(repr(cmplx)) will now round-trip values" -> so
      complex(repr(cmplx)) will now round-trip values

- Interpreter Changes
    - "**encoding** or **encoding**:**errorhandler**" - Are the **
      truly part of the syntax?

- New, Improved, and Deprecated Modules
    - heapq.merge() returns a generator; the example should be
      list(heapq.merge([1, 3, 5, 9], [2, 8, 16]))
    - All the new itertools functions return iterators, not lists;
      their examples should also be wrapped in list()
    - itertools.product([1,2], repeat=3)) <- extra )
    - shutil - "ignore_patterns() takes an arbitrary number of
      glob-style patterns and will ignore any files and directories
      that match this pattern." -> ignore_patterns() takes an arbitrary
      number of glob-style patterns and returns a callable which will
      ignore any files and directories that match this pattern.
- The future_builtins module
    - I think all the ** are extraneous.

Many of the items are fixed in rev66217; thanks!  A few of them were
fixed in the revisions I did this past weekend.

Not fixed: 

* the links for apply() and map() in the PEP 371 section.  Georg, is
there a way to override where the methods link to, or at least prevent
them from being turned into links?

* the itertools section uses the -> to indicate the resulting stream of
values; this is why those examples aren't written in the
interpreter-prompt style.  So I'm not going to change the examples by
adding list().

For the itertools examples, perhaps you could remove the [ ] from the
result text so it doesn't look like a list. For example:
itertools.izip_longest([1,2,3], [1,2,3,4,5]) ->
 (1, 1), (2, 2), (3, 3), (None, 4), (None, 5)

In rev66217, the itertools example for "With two iterables, 2N-tuples
are returned." has a typo:
itertools(product([1,2], [3,4], repeat=2)
should be:
itertools.product([1,2], [3,4], repeat=2)

itertools(product typo fixed in rev. 66231.