Skip to content

Commit 81024d9

Browse files
committed
Rollup merge of #26369 - IvanUkhov:collections, r=eddyb
2 parents 3afc385 + 8e969de commit 81024d9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/libstd/collections/mod.rs

+3-3
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@
6666
//! ### Use a `BTreeMap` when:
6767
//! * You're interested in what the smallest or largest key-value pair is.
6868
//! * You want to find the largest or smallest key that is smaller or larger
69-
//! than something
69+
//! than something.
7070
//! * You want to be able to get all of the entries in order on-demand.
7171
//! * You want a sorted map.
7272
//!
@@ -147,7 +147,7 @@
147147
//! relation to the number of elements in the collection. VecMap should only be
148148
//! seriously considered for small keys.
149149
//!
150-
//! Note also that BTreeMap's precise preformance depends on the value of B.
150+
//! Note also that BTreeMap's precise performance depends on the value of B.
151151
//!
152152
//! # Correct and Efficient Usage of Collections
153153
//!
@@ -309,7 +309,7 @@
309309
//! If a `Vacant(entry)` is yielded, then the key *was not* found. In this case
310310
//! the only valid operation is to `insert` a value into the entry. When this is
311311
//! done, the vacant entry is consumed and converted into a mutable reference to
312-
//! the the value that was inserted. This allows for further manipulation of the
312+
//! the value that was inserted. This allows for further manipulation of the
313313
//! value beyond the lifetime of the search itself. This is useful if complex
314314
//! logic needs to be performed on the value regardless of whether the value was
315315
//! just inserted.

0 commit comments

Comments
 (0)