https://gcc.gnu.org/g:ebc61a9c4c730bf5562db25b1fcc06d615e33e66
commit r13-8769-gebc61a9c4c730bf5562db25b1fcc06d615e33e66
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Thu Apr 25 13:52:00 2024 +0100
libstdc++: Fix typo in Doxygen comment
libstdc++-v3/ChangeLog:
* include/std/chrono (tzdb_list): Fix typo in Doxygen comment.
(cherry picked from commit 6391cf8bd9c1d71805d9aba00b25fdaa550f39c8)
Diff:
---
libstdc++-v3/include/std/chrono | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
index edb782f6f10e..1f3f897d932a 100644
--- a/libstdc++-v3/include/std/chrono
+++ b/libstdc++-v3/include/std/chrono
@@ -2790,7 +2790,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
/** Remove the tzdb object _after_ the one the iterator refers to.
*
- * Calling this function concurently with any of `front()`, `begin()`,
+ * Calling this function concurrently with any of `front()`, `begin()`,
* or `end()` does not cause a data race, but in general this function
* is not thread-safe. The behaviour may be undefined if erasing an
* element from the list while another thread is calling the same
