Fixes #204 ("Inconsistent noexcept-ness of static_vector::reserve").

doc/container.qbk

@@ -750,7 +750,7 @@ the last template parameter and defined using the utility class
 
 *  [classref boost::container::throw_on_overflow throw_on_overflow]: A boolean that specifies if the
    container should throw an exception when the compile-time capacity is not enough to hold the requesteed number
-   of objects. When "false", if the capacit is overflowd, the implementation calls to BOOST_ASSERT and if that assertion
+   of objects. When "false", if the capacit is overflowed, the implementation calls to BOOST_ASSERT and if that assertion
    does not throw or abort, undefined behavior is triggered.
 
 See the following example to see how [classref boost::container::static_vector_options static_vector_options] can be
@@ -1343,6 +1343,7 @@ use [*Boost.Container]? There are several reasons for that:
 * The library now compiles without warnings with GCC's -Wcast-align=strict
 * Fixed bugs/issues:
    * [@https://github.com/boostorg/container/issues/199    GitHub #199: ['"Apply LWG issue 3471 to memory_resource"]].
+   * [@https://github.com/boostorg/container/issues/204    GitHub #204: ['"Inconsistent noexcept-ness of static_vector::reserve"]].
    * [@https://github.com/boostorg/container/issues/206    GitHub #206: ['"operator-> on static_vector::iterator causes cast alignment warning"]].
 
 [endsect]