There are several aspects of DenseMap that you should be aware of, however. The
iterators in a densemap are invalidated whenever an insertion occurs, unlike
map. Also, because DenseMap allocates space for a large number of key/value
-pairs (it starts with 64 by default) if you have large keys or values, it can
-waste a lot of space. Finally, you must implement a partial specialization of
+pairs (it starts with 64 by default), it will waste a lot of space if your keys
+or values are large. Finally, you must implement a partial specialization of
DenseMapKeyInfo for the key that you want, if it isn't already supported. This
is required to tell DenseMap about two special marker values (which can never be
-inserted into the map).</p>
+inserted into the map) that it needs internally.</p>
</div>