LWG2091 Misplaced effect in m.try_lock_for()
LWG2092 Vague Wording for condition_variable_any

This change was made in [thread.condition.condvar] as the context and
issue description would suggest, rather than
[thread.timedmutex.requirements] as the proposed wording indicates
(presumably a copy-o from issue 2091).
LWG2145 error_category default constructor
LWG2147 Unclear hint type in Allocator's allocate function

"possibly const" formatted with "const" in code font, since that is
the prevalent (though not uniform) style in the draft.
LWG2163 nth_element requires inconsistent post-conditions
LWG2169 Missing reset() requirements in unique_ptr specialization
LWG2172 Does atomic_compare_exchange_* accept v == nullptr arguments?
LWG2080 Specify when once_flag becomes invalid
LWG2144 Missing noexcept specification in type_index
LWG2174 wstring_convert::converted() should be noexcept
LWG2175 wstring_convert and wbuffer_convert validity

Improved the grammar of the first added sentence with a comma.
LWG2177 Requirements on Copy/MoveInsertable

I rephrased the new wording for grammar and clarity. Specifically, I
replaced "when evaluated the following postconditions hold" with
"its evaluation causes the following postcondition to hold" and I
changed "satisfying the MoveInsertable requirements" to "T being
MoveInsertable into X".
LWG2187 vector<bool> is missing emplace and emplace_back member functions
LWG2197 Specification of is_[un]signed unclear for non-arithmetic types
LWG2200 Data race avoidance for all containers, not only for sequences
LWG2211 Replace ambiguous use of "Allocator" in container requirements
LWG2222 Inconsistency in description of forward_list::splice_after single-element overload
LWG2225 Unrealistic header inclusion checks required
LWG2231 DR 704 removes complexity guarantee for clear()

General issues with this table logged at
https://github.com/cplusplus/draft/issues/120
LWG2209 assign() overspecified for sequence containers