#354 Add maven model for feature toggle design pattern

event-aggregator/index.md

@@ -9,7 +9,8 @@ tags:
  - Difficulty-Beginner
 ---
 
-**Intent:** A system with lots of objects can lead to complexities when a
+## Intent
+A system with lots of objects can lead to complexities when a
 client wants to subscribe to events. The client has to find and register for
 each object individually, if each object has multiple events then each event
 requires a separate subscription. An Event Aggregator acts as a single source
@@ -18,7 +19,8 @@ allowing clients to register with just the aggregator.
 
 ![alt text](./etc/classes.png "Event Aggregator")
 
-**Applicability:** Use the Event Aggregator pattern when
+## Applicability
+Use the Event Aggregator pattern when
 
 * Event Aggregator is a good choice when you have lots of objects that are
   potential event sources. Rather than have the observer deal with registering
@@ -26,6 +28,6 @@ allowing clients to register with just the aggregator.
   Aggregator. As well as simplifying registration, a Event Aggregator also
   simplifies the memory management issues in using observers.
 
-**Credits:**
+## Credits
 
 * [Martin Fowler - Event Aggregator](http://martinfowler.com/eaaDev/EventAggregator.html)