Rationale:

Solved by N3058.

[ 2010 Pittsburgh: Moved to NAD EditorialResolved. Rationale added below. ]

[futures.unique_future]/1 should be updated to mention async.

[futures.shared_future]/1 should also be updated for async. That paragraph also says

... Its value or exception can be set by use of a shared_future, promise ([futures.promise]), or packaged_task ([futures.task]) object that shares the same associated state.

How can the value be set by a shared_future?

[futures.atomic_future]/1 says

An atomic_future object can only be created by use of a promise ([futures.promise]) or packaged_task ([futures.task]) object.

which is wrong, it's created from a std::future, which could have been default-constructed. That paragraph should be closer to the text of [futures.shared_future]/1, and should also mention async.