Fixup: review comments

Author: jensmaurer

source/atomics.tex

@@ -642,7 +642,7 @@
 That is,
 atomic operations on the same memory location via two different addresses will
 communicate atomically.}.
-The implementation should not depend on any per-process state.
+The implementation of these operations should not depend on any per-process state.
 \begin{note}
 This restriction enables communication by memory that is
 mapped into a process more than once and by memory that is shared between two

source/future.tex

@@ -570,7 +570,7 @@
 \begin{itemize}
 \item
 \tcode{allocated}, set when a dynamic array object has been
-allocated, and hence to be freed by the destructor for the
+allocated, and hence will be freed by the destructor for the
 \tcode{strstreambuf} object;
 \item
 \tcode{constant}, set when the array object has

source/iostreams.tex

@@ -431,11 +431,6 @@
 time prior to or during the first time an object of class
 \tcode{ios_base::Init} is constructed, and in any case before the body
 of \tcode{main}\iref{basic.start.main} begins execution.
-
-\recommended
-If it is possible for them to do so, implementations should
-initialize the objects earlier than required.
-
 The objects are not destroyed during program execution.\footnote{Constructors and destructors for objects with
 static storage duration can
 access these objects to read input from
@@ -445,6 +440,13 @@
 or
 \tcode{stderr}.
 }
+
+\pnum
+\recommended
+If it is possible for them to do so, implementations should
+initialize the objects earlier than required.
+
+\pnum
 The results of including \libheader{iostream} in a translation unit shall be as if
 \libheader{iostream} defined an instance of \tcode{ios_base::Init} with static
 storage duration.
@@ -9625,7 +9627,7 @@
 \remarks
 An
 implementation may provide an overriding definition for this function
-signature if it can determine that more characters can be read from the input
+signature if it can determine whether more characters can be read from the input
 sequence.
 \end{itemdescr}
 
@@ -11151,8 +11153,8 @@
 \pnum
 \begin{note}
 The member functions of the provided stream buffer
-can called from \tcode{emit()} while a lock is held,
-which might result in a deadlock.
+can be called from \tcode{emit()} while a lock is held,
+which might result in a deadlock if used incautiously.
 \end{note}
 
 \pnum

source/threads.tex

@@ -6446,6 +6446,7 @@
 \begin{note}
 It is valid to move from a future object for which \tcode{valid() == false}.
 \end{note}
+
 \recommended
 Implementations should detect this case and throw an object of type
 \tcode{future_error} with an error condition of \tcode{future_errc::no_state}.
@@ -6745,6 +6746,7 @@
 It is valid to copy or move from a \tcode{shared_future}
 object for which \tcode{valid()} is \tcode{false}.
 \end{note}
+
 \recommended
 Implementations should detect this case and throw an object of type
 \tcode{future_error} with an error condition of \tcode{future_errc::no_state}.

source/utilities.tex

@@ -4580,7 +4580,7 @@
 \tcode{t} are as defined by the exception safety guarantee of the assignment
 expression; \tcode{valueless_by_exception()} will be \tcode{false}.
 \item If an exception is thrown during the initialization of the contained value,
-the \tcode{variant} object is permitted not to hold a value.
+the \tcode{variant} object is permitted to not hold a value.
 \end{itemize}
 \end{itemdescr}
 
@@ -4664,7 +4664,7 @@
 \pnum
 \remarks
 If an exception is thrown during the initialization of the contained value,
-the \tcode{variant} is permitted not to hold a value.
+the \tcode{variant} is permitted to not hold a value.
 \end{itemdescr}
 
 \indexlibrarymember{emplace}{variant}%
@@ -4705,7 +4705,7 @@
 \pnum
 \remarks
 If an exception is thrown during the initialization of the contained value,
-the \tcode{variant} is permitted not to hold a value.
+the \tcode{variant} is permitted to not hold a value.
 \end{itemdescr}
 
 \rSec3[variant.status]{Value status}