Replace "could" and "might" in Annexes. (#4390)

Author: tkoeppe

source/compatibility.tex

@@ -632,7 +632,7 @@
 active, and has been superseded by \tcode{uncaught_exceptions}.
 \effect
 A valid \CppXVII{} program that calls \tcode{std::uncaught_exception} may fail
-to compile. It might be revised to use \tcode{std::uncaught_exceptions} instead,
+to compile. It can be revised to use \tcode{std::uncaught_exceptions} instead,
 for clear and portable semantics.
 
 \nodiffref
@@ -920,9 +920,9 @@
 if it has a potentially throwing dynamic exception specification,
 is rejected as ill-formed in this revision of \Cpp{}.
 Violating a non-throwing dynamic exception specification
-calls \tcode{terminate}
-rather than \tcode{unexpected}
-and might not perform stack unwinding prior to such a call.
+calls \tcode{terminate} rather than \tcode{unexpected},
+and it is unspecified whether stack unwinding is performed
+prior to such a call.
 
 \rSec2[diff.cpp14.library]{\ref{library}: library introduction}
 
@@ -1111,7 +1111,7 @@
 \rationale
 Required for sized deallocation.
 \effect
-Valid \CppXI{} code could declare a global placement allocation function and
+Valid \CppXI{} code can declare a global placement allocation function and
 deallocation function as follows:
 \begin{codeblock}
 void* operator new(std::size_t, std::size_t);
@@ -1996,7 +1996,7 @@
 \effect
 Deletion of semantically well-defined feature.
 \difficulty
-Could be automated.
+Can be automated.
 Violations will be diagnosed by the \Cpp{} translator.
 The
 fix is to add a  cast.
@@ -2255,7 +2255,7 @@
 Deletion of semantically well-defined feature.
 \difficulty
 Syntactic transformation.
-Could be automated.
+Can be automated.
 \howwide
 Common.
 
@@ -2585,7 +2585,7 @@
 \difficulty
 Semantic transformation.
 To make the struct type name visible in the scope of the enclosing
-struct, the struct tag could be declared in the scope of the
+struct, the struct tag can be declared in the scope of the
 enclosing struct, before the enclosing struct is defined.
 Example:
 \begin{codeblock}
@@ -2597,7 +2597,7 @@
 
 All the definitions of C struct types enclosed in other struct
 definitions and accessed outside the scope of the enclosing
-struct could be exported to the scope of the enclosing struct.
+struct can be exported to the scope of the enclosing struct.
 Note: this is a consequence of the difference in scope rules,
 which is documented in \ref{basic.scope}.
 \howwide

source/future.tex

@@ -204,8 +204,8 @@
 as defaulted is deprecated if the class has
 a user-declared copy constructor or
 a user-declared destructor.
-In a future revision of \Cpp{}, these implicit definitions
-could become deleted\iref{dcl.fct.def.delete}.
+It is possible that future versions of \Cpp{} will specify
+that these implicit definitions are deleted\iref{dcl.fct.def.delete}.
 
 \rSec1[depr.c.headers]{C headers}
 
@@ -2757,7 +2757,7 @@
 an atomic variable of static storage duration of a type that
 is initialization-compatible with \tcode{value}.
 \begin{note}
-This operation might need to initialize locks.
+This operation possibly needs to initialize locks.
 \end{note}
 Concurrent access to the variable being initialized,
 even via an atomic operation,