Reported on my G+ share of the latest reworking:

"""
The only part I found confusing is when you first introduce "from _future_ import unicode_literals" --- it looks like you forgot to explain what it does. It turns out that you explain it somewhat two paragraphs below it, so maybe you can just move this down a bit?

Maybe "bytes literals" section should be called "Bytes and unicode literals" or something and move the "unicode_literals" line in there.
"""

"""
The only issue I noticed is that "Eliminate -3 Warnings" section still mentions 2to3 before it's even introduced.
"""

I've created a patch that addresses the first criticism (explaining unicode_literals), as well as the first mention of print_function. It also addresses a small concern regarding "map", which I've mentioned in my G+ comment:

"""
Also, a friend was confused by http://docs.python.org/dev/howto/pyporting.html#update-map-for-imbalanced-input-sequences , until I understood that he didn't know map can take several sequences. I assume a lot of less experienced Python programmers only use map with a single sequence, and might be confused as well. A sentence mentioning that might help.
"""

I see that the current version of the doc on hg already addresses the 2to3 mention.

BTW, there remains another concern I mentioned on G+:

"""
A note on formatting: I found some of 4th- and 5th-level headings too subtle. For instance, http://docs.python.org/dev/howto/pyporting.html#from-future-import-absolute-import got me thinking for a second if it was part of the previous paragraph or a new heading. Maybe underlining, or a bullet-like marker, or some indentation could help there.
"""

But I don't know enough of the formatting standards, so I haven't addressed this in the patch.

There's actually no way to tweak that formatting as that is all done by Sphinx automatically.

New changeset 863b8e71cfee by Brett Cannon in branch 'default':
Issue #20208: Clarify some things in the Python porting HOWTO.
http://hg.python.org/cpython/rev/863b8e71cfee