From 71a9ef5341e519b313adcfae7b905850f45bd67b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ion=20Gazta=C3=B1aga?= Date: Tue, 3 May 2022 23:01:03 +0200 Subject: [PATCH] Fix typos --- doc/intrusive.qbk | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/intrusive.qbk b/doc/intrusive.qbk index 99e4426..3571241 100644 --- a/doc/intrusive.qbk +++ b/doc/intrusive.qbk @@ -886,7 +886,7 @@ the section [link intrusive.usage How to use Boost.Intrusive]: * [*`linear`]: the singly linked list is implemented as a null-terminated list instead of a circular list. This allows `O(1)` swap, - but losses some operations like `container_from_end_iterator`. + but loses some operations like `container_from_end_iterator`. * [*`cache_last`]: `slist` also stores a pointer to the last element of the singly linked list. This allows `O(1)` swap, `splice_after(iterator, slist &)` and makes the list offer new functions @@ -2392,7 +2392,7 @@ Let's see a small function that shows the use of `iterator_to` and [section:any_hooks Any Hooks: A single hook for any Intrusive container] Sometimes, a class programmer wants to place a class in several intrusive -containers but no at the same time. In this case, the programmer might +containers but not at the same time. In this case, the programmer might decide to insert two hooks in the same class. [c++]