[associative.reqmts.general,unord.req.general] Fix cross-references to [container.alloc.reqmts] and [container.reqmts] (#7249)

Both paragraphs incorrectly point to [container.reqmts] instead of [container.alloc.reqmts] for "the requirements of an allocator-aware container".

Author: CaseyCarter

source/containers.tex

@@ -2726,12 +2726,12 @@
 \pnum
 A type \tcode{X} meets the \defnadj{associative}{container} requirements
 if \tcode{X} meets all the requirements of an allocator-aware
-container\iref{container.reqmts} and
+container\iref{container.alloc.reqmts} and
 the following types, statements, and expressions are well-formed and
 have the specified semantics,
 except that for
 \tcode{map} and \tcode{multimap}, the requirements placed on \tcode{value_type}
-in \ref{container.alloc.reqmts} apply instead to \tcode{key_type}
+in \ref{container.reqmts} apply instead to \tcode{key_type}
 and \tcode{mapped_type}.
 \begin{note}
 For example, in some cases \tcode{key_type} and \tcode{mapped_type}
@@ -4225,11 +4225,11 @@
 A type \tcode{X} meets
 the \defnadj{unordered associative}{container} requirements
 if \tcode{X} meets all the requirements of
-an allocator-aware container\iref{container.reqmts} and
+an allocator-aware container\iref{container.alloc.reqmts} and
 the following types, statements, and expressions are well-formed and
 have the specified semantics,
 except that for \tcode{unordered_map} and \tcode{unordered_multimap},
-the requirements placed on \tcode{value_type} in \ref{container.alloc.reqmts}
+the requirements placed on \tcode{value_type} in \ref{container.reqmts}
 apply instead to \tcode{key_type} and \tcode{mapped_type}.
 \begin{note}
 For example, \tcode{key_type} and \tcode{mapped_type}