From 9e38e3c578ec6ac7c95dd54f55e4ff786523a83b Mon Sep 17 00:00:00 2001 From: joaquintides Date: Sat, 16 Sep 2023 09:47:10 +0200 Subject: [PATCH] typos --- doc/unordered/concurrent.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/unordered/concurrent.adoc b/doc/unordered/concurrent.adoc index a0b3d998..1bb441b4 100644 --- a/doc/unordered/concurrent.adoc +++ b/doc/unordered/concurrent.adoc @@ -44,7 +44,7 @@ logical cores in the CPU). == Visitation-based API The first thing a new user of `boost::concurrent_flat_set` or `boost::concurrent_flat_map` -will notice is that these classes _do not provide iterators_ (which makes then technically +will notice is that these classes _do not provide iterators_ (which makes them technically not https://en.cppreference.com/w/cpp/named_req/Container[Containers^] in the C++ standard sense). The reason for this is that iterators are inherently thread-unsafe. Consider this hypothetical code: @@ -112,7 +112,7 @@ if (found) { } ---- -Visitation is prominent in the API provided by `boost::concurrent_flat_ser` and `boost::concurrent_flat_map`, and +Visitation is prominent in the API provided by `boost::concurrent_flat_set` and `boost::concurrent_flat_map`, and many classical operations have visitation-enabled variations: [source,c++]