Reformat comments in core/layout up until LayoutBox

third_party/WebKit/Source/core/layout/FragmentationContext.h

Index: third_party/WebKit/Source/core/layout/FragmentationContext.h
diff --git a/third_party/WebKit/Source/core/layout/FragmentationContext.h b/third_party/WebKit/Source/core/layout/FragmentationContext.h
index 885f7a34fbeb7f9d9da09271f3d248085eaf6ba2..1e62803302fc14f7978b2c57ec1cc1de64a9be3b 100644
--- a/third_party/WebKit/Source/core/layout/FragmentationContext.h
+++ b/third_party/WebKit/Source/core/layout/FragmentationContext.h
@@ -11,40 +11,46 @@
 
 namespace blink {
 
-// A fragmentation context is either established by a multicol container, or by pages when
-// printing. A fragmentation context consists of a series of fragmentainers. A fragmentainer is
-// simply a column or page, depending on the type of fragmentation context. [1]
+// A fragmentation context is either established by a multicol container, or by
+// pages when printing. A fragmentation context consists of a series of
+// fragmentainers. A fragmentainer is simply a column or page, depending on the
+// type of fragmentation context. [1]
 //
-// A couple of methods here take a |blockOffset| parameter. This is the offset from the start of the
-// fragmentation context, pretending that everything is laid out in one single strip (and not sliced
-// into pages or columns). In multicol, this is referred to as the flow thread coordinate space.
+// A couple of methods here take a |blockOffset| parameter. This is the offset
+// from the start of the fragmentation context, pretending that everything is
+// laid out in one single strip (and not sliced into pages or columns).
+// In multicol, this is referred to as the flow thread coordinate space.
 //
-// It should be noted that a multicol container may be nested inside another fragmentation context
-// (another multicol container, or the pages when printing), although this class doesn't deal with
-// that (it's internal to the multicol implementation).
+// It should be noted that a multicol container may be nested inside another
+// fragmentation context (another multicol container, or the pages when
+// printing), although this class doesn't deal with that (it's internal to the
+// multicol implementation).
 //
 // [1] http://www.w3.org/TR/css3-break/#fragmentation-model
 class CORE_EXPORT FragmentationContext {
  public:
   virtual ~FragmentationContext() {}
 
-  // The height of the fragmentainers may depend on the total height of the contents (column
-  // balancing), in which case false is returned if we haven't laid out yet. Otherwise, true is
-  // returned.
+  // The height of the fragmentainers may depend on the total height of the
+  // contents (column balancing), in which case false is returned if we haven't
+  // laid out yet. Otherwise, true is returned.
   virtual bool isFragmentainerLogicalHeightKnown() = 0;
 
-  // Return the height of the fragmentainer at the specified offset. The fragmentainer height
-  // isn't necessarily uniform all across the fragmentation context.
+  // Return the height of the fragmentainer at the specified offset. The
+  // fragmentainer height isn't necessarily uniform all across the fragmentation
+  // context.
   virtual LayoutUnit fragmentainerLogicalHeightAt(LayoutUnit blockOffset) = 0;
 
-  // Return how much is left of the fragmentainer at the specified offset. Callers typically want
-  // this information to decide whether some piece of content fits in this fragmentainer, or if it
-  // has to push the content to the next fragmentainer.
+  // Return how much is left of the fragmentainer at the specified offset.
+  // Callers typically want this information to decide whether some piece of
+  // content fits in this fragmentainer, or if it has to push the content to the
+  // next fragmentainer.
   virtual LayoutUnit remainingLogicalHeightAt(LayoutUnit blockOffset) = 0;
 
-  // Return the flow thread of the fragmentation context, if it is a multicol fragmentation
-  // context. Since multicol containers may be nested inside other fragmentation contexts,
-  // sometimes we need to know if it's a multicol container that we're dealing with.
+  // Return the flow thread of the fragmentation context, if it is a multicol
+  // fragmentation context. Since multicol containers may be nested inside other
+  // fragmentation contexts, sometimes we need to know if it's a multicol
+  // container that we're dealing with.
   virtual class LayoutMultiColumnFlowThread* associatedFlowThread() {
     return nullptr;
   }