* include/std/chrono (system_clock): Fix typo in comment.

From-SVN: r240589

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 3ce95a1c3eaa5c4a20aa0cea3f1c3d406b0aa302..ee5a63fc45c9222dfc13d3c246c12d788837283c 100644 (file)
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,5 +1,7 @@
 2016-09-28  Jonathan Wakely  <jwakely@redhat.com>
 
+       * include/std/chrono (system_clock): Fix typo in comment.
+
        * include/experimental/bits/fs_fwd.h (file_time_type): Simplify
        definition.
        * src/filesystem/ops.cc (file_time): Take error_code parameter and

diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
index f29d8e1adbcdb6fdcc7134e88cac3be79ef3a356..11e7fa298c4f618188c5c6f6dfc4d6ad96b2c5e1 100644 (file)
--- a/libstdc++-v3/include/std/chrono
+++ b/libstdc++-v3/include/std/chrono
@@ -784,7 +784,7 @@ _GLIBCXX_END_NAMESPACE_VERSION
     // Clocks.
 
     // Why nanosecond resolution as the default?
-    // Why have std::system_clock always count in the higest
+    // Why have std::system_clock always count in the highest
     // resolution (ie nanoseconds), even if on some OSes the low 3
     // or 9 decimal digits will be always zero? This allows later
     // implementations to change the system_clock::now()