fixups: addressing comments from Jens

Author: notadragon

source/basic.tex

@@ -551,10 +551,10 @@
 between the point at which the entity is introduced and the scope
 (where \tcode{*\keyword{this}} is considered to be introduced
 within the innermost enclosing class or non-lambda function definition scope),
-either:  %JMB: Potential drive-by, we should remove the : and the first two "or"s.
+either
 \begin{itemize}
-\item the intervening scope is a block scope, or
-\item the intervening scope is a contract-assertion scope\iref{basic.scope.contract}, or
+\item the intervening scope is a block scope,
+\item the intervening scope is a contract-assertion scope\iref{basic.scope.contract},
 \item the intervening scope is the function parameter scope of
 a \grammarterm{lambda-expression} or \grammarterm{requires-expression}, or
 \item the intervening scope is the lambda scope of
@@ -6178,12 +6178,12 @@
 every argument expression and
 the postfix expression designating \placeholder{f}
 are sequenced before
-every precondition assertion of \placeholder{f}\iref{dcl.contract.func},  %JMB: This said "of the called function", changed to "of f"
+every precondition assertion of \placeholder{f}\iref{dcl.contract.func},
 which in turn are sequenced before
 every expression or statement
 in the body of \placeholder{f},
 which in turn are sequenced before
-every postcondition assertion of \placeholder{f}.  %JMB: This says "the called function" again in P2900
+every postcondition assertion of \placeholder{f}.
 
 \pnum
 For each
@@ -7004,7 +7004,7 @@
 \pnum
 \indextext{termination!program}%
 \indextext{\idxcode{main} function!return from}%
-A \keyword{return} statement\iref{stmt.return} in \tcode{main} has the effect of leaving the main  %JMB: Why is the second main here not in code font?
+A \keyword{return} statement\iref{stmt.return} in \tcode{main} has the effect of leaving the \tcode{main}
 function (destroying any objects with automatic storage duration
 and evaluating any postcondition assertions of \tcode{main})
 and calling \tcode{std::exit} with the return value as the argument.
@@ -7371,14 +7371,13 @@
 of the predicate of a contract assertion,
 no diagnostic required.
 
-%JMB: This paragraph was not in P2900, but the note is not directly tied to the paragraph above.
 \pnum
 \begin{note}
 Within the predicate of a contract assertion,
 \grammarterm{id-expression}s referring to
 variables declared outside the contract assertion
-are const\iref{expr.prim.id.unqual}, %JMB: P2900 had this const in code font
-\tcode{this} is a pointer to const\iref{expr.prim.this}, %JMB: P2900 had this const in code font
+are const\iref{expr.prim.id.unqual},
+\tcode{this} is a pointer to const\iref{expr.prim.this},
 and the result object can be named
 if a \grammarterm{result-name-introducer}\iref{dcl.contract.res} has been specified.
 \end{note}

source/intro.tex

@@ -795,7 +795,7 @@
 \begin{itemize}
 \item
 a preprocessing translation unit containing
-a \tcode{\#error} preprocessing directive\iref{cpp.error},  %JMB: this last comma was a mistake in P2900, it was not in green.
+a \tcode{\#error} preprocessing directive\iref{cpp.error},
 \item
 a translation unit with
 a \grammarterm{static_assert-declaration} that fails\iref{dcl.pre}, or
@@ -936,15 +936,6 @@
 are termed \defnadj{observable}{checkpoints}.
 \begin{note}
 A call to \tcode{std::observable}\iref{utility.undefined}
-is an observable checkpoint.
-\end{note}
-
-\pnum
-\indextext{observable checkpoint}
-Certain events in the execution of a program
-are termed \defnadj{observable}{checkpoints}.
-\begin{note}
-A call to \tcode{std::observable}\iref{utility.undefined}
 is an observable checkpoint,
 as are certain parts of
 the evaluation of contract assertions\iref{basic.contract}.

source/lib-intro.tex

@@ -3559,7 +3559,7 @@
 in~\ref{global.functions}, member functions in~\ref{member.functions}, data race
 avoidance in~\ref{res.on.data.races}, access specifiers
 in~\ref{protection.within.classes}, class derivation in~\ref{derivation}, and
-exceptions in~\ref{res.on.exception.handling}.  %JMB: This intro fluff should add "and contract assertions in~\ref{res.contract.assertions}  Also, the "its use" doesn't seem right in this sentence.   Can I make this a bulleted list so that it resembles a sentence again?
+exceptions in~\ref{res.on.exception.handling}.
 
 \rSec3[res.on.headers]{Headers}
 

source/overloading.tex

@@ -474,7 +474,7 @@
 \item
 otherwise,
 the implied object argument is
-\tcode{(*\keyword{this})}.  %JMB: The \keyword on this was missing
+\tcode{(*\keyword{this})}.
 \end{itemize}
 Otherwise,
 \begin{itemize}

source/statements.tex

@@ -1070,7 +1070,7 @@
 by those \grammarterm{assertion-statement}s.
 \begin{note}
 A sequence of \grammarterm{assertion-statement}s
-can thus be repeatedly evaluated as a group.  %JMB: Should we remove the "thus"?
+can thus be repeatedly evaluated as a group.
 \begin{example}
 \begin{codeblock}
 int f(int i)