Committed to trunk.

commit 6246cb3120548a1dfc62bf7aa538f3e5538123c9
Author: Jonathan Wakely <jwak...@redhat.com>
Date:   Wed Sep 28 19:03:43 2016 +0100

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

diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
index f29d8e1..11e7fa2 100644
--- 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()

Reply via email to