Run through spell checker

This commit is contained in:
Howard Hinnant
2017-06-16 13:35:13 -04:00
parent 27410b5095
commit ff07f87b5b

View File

@@ -1731,7 +1731,7 @@ constexpr time_point& operator-=(const duration& d);
</pre></blockquote>
<p class = note>
Moidfy section 23.17.6 Class template <code>time_point</code> [time.point]/p1:
Modify section 23.17.6 Class template <code>time_point</code> [time.point]/p1:
</p>
<blockquote>
@@ -1805,7 +1805,7 @@ Modify 23.17.7 [time.clock]:
<p>
1 The types defined in this subclause shall satisfy the TrivialClock requirements (23.17.3)
<ins>unless otherwise sepcified</ins>.
<ins>unless otherwise specified</ins>.
</p>
</blockquote>
@@ -3011,7 +3011,7 @@ formatting string specifier according to the following specification:
<p>
The <code>fmt</code> string consists of zero or more conversion specifiers and ordinary
mulibyte characters. A conversion specifier consists of a <code>%</code> character,
multibyte characters. A conversion specifier consists of a <code>%</code> character,
possibly followed by an <code>E</code> or <code>O</code> modifier character (described
below), followed by a character that determines the behavior of the conversion specifier.
All ordinary multibyte characters (excluding the terminating null character) are streamed
@@ -3508,7 +3508,7 @@ alternative representation.</td>
<td>Matches one white space character.
[<i>Note:</i> <code>%n</code>, <code>%t</code> and a space, can be combined to match
a wide range of white-space patterns. For example <code>"%n "</code> matches one or
more white space charcters, and <code>"%n%t%t"</code> matches one to three white
more white space characters, and <code>"%n%t%t"</code> matches one to three white
space characters. &mdash; <i>end note</i>]</td>
</tr>
@@ -8979,7 +8979,7 @@ pointer to a valid <code>time_zone</code>. <i>&mdash; end note</i>]
<a name="time.timezone.database.remote"></a><h3>23.17.12.1.1 Remote time zone database support [time.timezone.database.remote]</h3>
<p class = note>
This subsection is optional/seperable and needs further discussion in the LEWG. No
This subsection is optional/separable and needs further discussion in the LEWG. No
other sections depend upon this subsection.
</p>