diff --git a/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst
--- a/llvm/docs/ProgrammersManual.rst
+++ b/llvm/docs/ProgrammersManual.rst
@@ -2200,8 +2200,9 @@
 
 The STL provides several other options, such as std::multiset and the various
 "hash_set" like containers (whether from C++ TR1 or from the SGI library).  We
-never use hash_set and unordered_set because they are generally very expensive
-(each insertion requires a malloc) and very non-portable.
+never use "hash_set" like containers, e.g., unordered_set, because they are
+generally very expensive (each insertion requires a malloc) and very
+non-portable.
 
 std::multiset is useful if you're not interested in elimination of duplicates,
 but has all the drawbacks of :ref:`std::set <dss_set>`.  A sorted vector
@@ -2391,8 +2392,9 @@
 
 The STL provides several other options, such as std::multimap and the various
 "hash_map" like containers (whether from C++ TR1 or from the SGI library).  We
-never use hash_set and unordered_set because they are generally very expensive
-(each insertion requires a malloc) and very non-portable.
+never use "hash_map" like containers, e.g., unordered_map, because they are
+generally very expensive (each insertion requires a malloc) and very
+non-portable.
 
 std::multimap is useful if you want to map a key to multiple values, but has all
 the drawbacks of std::map.  A sorted vector or some other approach is almost