There's another one in Table 29.

That one is possibly intentional, because 17.6.3.5p2 just before it says: "Within Tables 28 and 29, the use of move and forward always refers to std::move and std::forward, respectively."

Oh, right, that's true.

Could you perhaps make a diffpdf screenshot?

Why?

Anything that's overly long and contains things like \brk concerns me, so I'd like to see what the result looks like.

While you're at it, I think the specification of try_emplace/insert_or_assign may also be using naked forwards in a few places. I'm sure the author would be grateful for the fixes :-)

@Eelis: ping?

Oh, yeah, I saw a bunch of other unqualified things as well (not just forward, also move/forward_as_tuple/...), and then I got discouraged by the prospect of trying to figure out for each individual case whether the qualification is desired. :( Feel free to close if a partial fix is not worthwhile.

Hm, generally, only move and forward are qualified, except when they appear in certain requirements tables which have a blanket rule saying that all unqualified uses are understood to be qualified. Otherwise, nothing is qualified except when it's syntactically required (e.g. using reverse_iterator = std::reverse_iterator<T>;, because it's the same name).

Best left to a systematic review.