3742 zfs comments need cleaner, more consistent style
Submitted by:   Will Andrews <willa@spectralogic.com>
Submitted by:   Alan Somers <alans@spectralogic.com>
Reviewed by:    Matthew Ahrens <mahrens@delphix.com>
Reviewed by:    George Wilson <george.wilson@delphix.com>
Reviewed by:    Eric Schrock <eric.schrock@delphix.com>

*** 64,76 ****
   * to hold blocks. They are dynamically allocated and freed as
   * needed from the blocks available. Figure X shows the ZIL structure:
   */
  
  /*
!  * This global ZIL switch affects all pools
   */
! int zil_replay_disable = 0;    /* disable intent logging replay */
  
  /*
   * Tunable parameter for debugging or performance analysis.  Setting
   * zfs_nocacheflush will cause corruption on power loss if a volatile
   * out-of-order write cache is enabled.
--- 64,76 ----
   * to hold blocks. They are dynamically allocated and freed as
   * needed from the blocks available. Figure X shows the ZIL structure:
   */
  
  /*
!  * Disable intent logging replay.  This global ZIL switch affects all pools.
   */
! int zil_replay_disable = 0;
  
  /*
   * Tunable parameter for debugging or performance analysis.  Setting
   * zfs_nocacheflush will cause corruption on power loss if a volatile
   * out-of-order write cache is enabled.
*** 877,886 ****
--- 877,887 ----
          }
  }
  
  /*
   * Define a limited set of intent log block sizes.
+  *
   * These must be a multiple of 4KB. Note only the amount used (again
   * aligned to 4KB) actually gets written. However, we can't always just
   * allocate SPA_MAXBLOCKSIZE as the slog space could be exhausted.
   */
  uint64_t zil_block_buckets[] = {