From 69ba1c7c0017eb5d0864cfc0c0c11633802bc787 Mon Sep 17 00:00:00 2001 From: joaquintides Date: Tue, 9 May 2023 19:53:56 +0200 Subject: [PATCH] editorial --- doc/unordered/concurrent_flat_map_intro.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/unordered/concurrent_flat_map_intro.adoc b/doc/unordered/concurrent_flat_map_intro.adoc index 722e5ef4..3d701764 100644 --- a/doc/unordered/concurrent_flat_map_intro.adoc +++ b/doc/unordered/concurrent_flat_map_intro.adoc @@ -73,9 +73,10 @@ m.visit(k, [](const auto& x) { // x is the element with key k (if it exists) The visitation function passed by the user (in this case, a lambda function) is executed internally by `boost::concurrent_flat_map` in -a thread-safe manner, so it can access the element without worries about other -threads interfering in the process. On the other hand, a -visitation function can _not_ access the container itself: +a thread-safe manner, so it can access the element without worrying about other +threads interfering in the process. + +On the other hand, a visitation function can _not_ access the container itself: [source,c++] ---- @@ -110,7 +111,7 @@ if (found) { } ---- -Visitation is pervasive in the API provided by `boost::concurrent_flat_map`, and +Visitation is prominent in the API provided by `boost::concurrent_flat_map`, and many classical operations have visitation-enabled variations: [source,c++]