1 files changed, 8 insertions, 10 deletions

diff --git a/llvm/tools/dsymutil/BinaryHolder.h b/llvm/tools/dsymutil/BinaryHolder.h
index 0d3c6d2b69a..f3ab7f6726a 100644
--- a/llvm/tools/dsymutil/BinaryHolder.h
+++ b/llvm/tools/dsymutil/BinaryHolder.h
@@ -26,17 +26,15 @@
 namespace llvm {
 namespace dsymutil {
 
-/// \brief The BinaryHolder class is responsible for creating and
-/// owning ObjectFile objects and their underlying MemoryBuffer. This
-/// is different from a simple OwningBinary in that it handles
-/// accessing to archive members.
+/// The BinaryHolder class is responsible for creating and owning ObjectFile
+/// objects and their underlying MemoryBuffer. This is different from a simple
+/// OwningBinary in that it handles accessing to archive members.
 ///
-/// As an optimization, this class will reuse an already mapped and
-/// parsed Archive object if 2 successive requests target the same
-/// archive file (Which is always the case in debug maps).
-/// Currently it only owns one memory buffer at any given time,
-/// meaning that a mapping request will invalidate the previous memory
-/// mapping.
+/// As an optimization, this class will reuse an already mapped and parsed
+/// Archive object if 2 successive requests target the same archive file (Which
+/// is always the case in debug maps).
+/// Currently it only owns one memory buffer at any given time, meaning that a
+/// mapping request will invalidate the previous memory mapping.
 class BinaryHolder {
   std::vector<std::unique_ptr<object::Archive>> CurrentArchives;
   std::unique_ptr<MemoryBuffer> CurrentMemoryBuffer;