Disable stylish-haskell header formatting

It mangles the haddock sections.
See haskell/stylish-haskell#466

And fix one whitespace issue stylish-haskell found.

.stylish-haskell.yaml

@@ -21,16 +21,16 @@ steps:
   # Currently, this option is not configurable and will format all exports and
   # module declarations to minimize diffs
   #
-  - module_header:
+  #- module_header:
   #     # How many spaces use for indentation in the module header.
-       indent: 2
+  #     indent: 2
   #
   #     # Should export lists be sorted?  Sorting is only performed within the
   #     # export section, as delineated by Haddock comments.
-       sort: False
+  #     sort: False
   #
   #     # See `separate_lists` for the `imports` step.
-       separate_lists: true
+  #     separate_lists: true
   #
   #     # When to break the "where".
   #     # Possible values:
@@ -40,14 +40,14 @@ steps:
   #     #   determined by the `columns` setting. Not applicable when the export
   #     #   list contains comments as newlines will be required.
   #     # - always: always break before the "where".
-       break_where: single
+  #     break_where: single
   #
   #     # Where to put open bracket
   #     # Possible values:
   #     # - same_line: put open bracket on the same line as the module name, before the
   #     #              comment of the module
   #     # - next_line: put open bracket on the next line, after module comment
-       open_bracket: same_line
+  #     open_bracket: same_line
 
   # Format record definitions. This is disabled by default.
   #
@@ -510,4 +510,4 @@ language_extensions:
 #
 # We run stylish from the root of the repo which is a project so this flag
 # doesn't apply
-cabal: false
+cabal: false

src/Database/LSMTree/Normal.hs

@@ -133,7 +133,7 @@ import           Database.LSMTree.Common (IOLike, Range (..), Session,
 -- * 'updates'
 -- * 'close'
 --
--- In particular it is possible to read a stable view of a table while 
+-- In particular it is possible to read a stable view of a table while
 -- concurrently modifying it: 'duplicate' the table handle first and then
 -- perform reads on the duplicate, while modifying the original handle. Note
 -- however that it would still be a race to 'duplicate' concurrently with