message: Headers more pretty
diff: [![Build Status](https://travis-ci.org/BitcoinUnlimited/BitcoinUnlimited.svg?branch=dev)](https://travis-ci.org/BitcoinUnlimited/BitcoinUnlimited)
  -What is Bitcoin?
  +# What is Bitcoin?
  Bitcoin is an experimental new digital currency that enables instant payments to
  anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate
  @@ -77,7 +77,7 @@ There are two modes of operation, one uses the QT UI and the other runs as a dae
  ### Initial Sync of the blockchain:
  -When you first run the node it must first sync the current blockchain. All block headers are first retrieved and then each block is downloaded, checked and the UTXO finally updated. This process can take from hours to `weeks` depending on the node configuration, and therefore, node configuration is crucial.
  +When you first run the node it must first sync the current blockchain. All block headers are first retrieved and then each block is downloaded, checked and the UTXO finally updated. This process can take from hours to *weeks* depending on the node configuration, and therefore, node configuration is crucial.
  The most important configuration which impacts the speed of the initial sync is the `dbcache` setting. The larger the dbcache the faster the initial sync will be, therefore, it is vital to make this setting as high as possible. If you are running on a Windows machine there is an automatically adjusting dbcache setting built in; it will size the dbcache in such a way as to leave only 10% of the physical memory free for other uses. On Linux and other OS's the sizing is such that one half the physical RAM will be used as dbcache. While these settings, particularly on non Windows setups, are not ideal they will help to improve the initial sync dramatically.
  @@ -87,11 +87,15 @@ However, even with the automatic configuration of the dbcache setting it is reco
  There are dozens of configuration and node policy options available but the two most important for the initial blockchain sync are as follows.
  -##### dbcache: As stated above, this setting is crucial to a fast initial sync. You can set this value from the command line by running
  +##### dbcache:
  +
  +As stated above, this setting is crucial to a fast initial sync. You can set this value from the command line by running
  `bitcoind -dbcache=<your size in MB>`, for example, a 1GB dbcache would be `bitcoind -dbcache=1000`. Similarly you can also add the setting to the bitcoin.conf file located in your installation folder. In the config file a simlilar entry would be `dbcache=1000`. When entering the size
  try to give it the maximum that your system can afford while still leaving enough memory for other processes.
  -##### maxoutconnections: It is generally fine to leave the default outbound connection settings for doing a sync, however, at times some users
  +##### maxoutconnections:
  +
  +It is generally fine to leave the default outbound connection settings for doing a sync, however, at times some users
  have reported issues with not being able to find enough useful connections. If that happens you can change this setting to override the default.
  For instance `bitcoind -maxoutconnections=30` will give you 30 outbound connections and should be more than enough in the event that the
  node is having difficulty.
  