Updated strategy cookbook introduction

- Removed annoying tabs
- Removed some comments
- Hopefully, it will display now correctly

cookbook/en/strategy-cookbook-introduction.txt

@@ -32,9 +32,6 @@ Such an interface could look like this:
     * Every blockstrategy is *only* responsible for rendering a block and declaring some basic
     * support, but *not* for updating its configuration etc. For this purpose, use controllers
     * and models.
-	 *
-	 * @author Christian Heinrich
-	 * @version $Id: BlockStrategyInterface.php 657 2010-03-16 00:08:50Z cheinrich $
     */
    interface BlockStrategyInterface {
         /**
@@ -109,6 +106,7 @@ As you can see, we have a method "setBlockEntity" which ties a potential strateg
    abstract class AbstractBlock {
         /**
          * The id of the block item instance
+         * This is a doctrine field, so you need to setup generation for it
          * @var integer
          */
         private $id;
@@ -119,6 +117,8 @@ As you can see, we have a method "setBlockEntity" which ties a potential strateg
          * This var contains the classname of the strategy
          * that is used for this blockitem. (This string (!) value will be persisted by Doctrine 2)
          *
+         * This is a doctrine field, so make sure that you use an @column annotation or setup your
+         * yaml or xml files correctly
          * @var string
          */
         protected $strategyClassName;
@@ -174,8 +174,6 @@ This might look like this:
     /**
      * The BlockStrategyEventListener will initialize a strategy after the
      * block itself was loaded.
-	 *
-	 * @author Christian Heinrich
      */
     class BlockStrategyEventListener implements Common\EventSubscriber {