Updated Design choices

docs/source/designchoices.rst

@@ -3,13 +3,18 @@ Design choices
 
 .. contents:: :local:
 
+Introduction
+============
+
+In this chapter we explain some design choices made in the smart contracts.
+
 Timestamp vs. block number
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+==========================
 
 The code uses block timestamps instead of block numbers for start and events. We work on the assumption that crowdsale periods are not so short or time sensitive there would be need for block number based timing. Furthermore if the network miners start to skew block timestamps we might have a larger problem with dishonest miners.
 
 Crowdsale strategies and compound design pattern
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+================================================
 
 Instead of cramming all the logic into a single contract through mixins and inheritance, we assemble our crowdsale from multiple components. Benefits include more elegant code, better reusability, separation of concern and testability.
 
@@ -22,7 +27,6 @@ Mainly, our crowdsales have the following major parts
 * Finalizing strategy: What happens after a successful crowdsale: allow tokens to be transferable, give out extra tokens, etc.
 
 Background information
-^^^^^^^^^^^^^^^^^^^^^^
-
+======================
 
 * https://drive.google.com/file/d/0ByMtMw2hul0EN3NCaVFHSFdxRzA/view