doc: Update my thoughts on the observer design pattern

Author: dancergraham

chapter02_observer/readme.md

@@ -1,7 +1,10 @@
 # Chapter 2: Observer design pattern
 
-> **Observer**: defines a one-to-many dependency between objects so that when one object changes state, all of its dependents are notified and updated automatically.
+> **Observer**: defines a one-to-many dependency between objects so that when one object changes state, all of its
+> dependents are notified and updated automatically.
 
-Very useful design pattern, often used in user interfaces and as part of the popular Model-View-Controller design pattern used, for instance, in Django.
-
-I find the name contradictory: shouldn't it be called the 'Subject' design pattern as the subject is the key actor ?
+A very useful design pattern, often used in user interfaces 
+and as part of the popular Model-View-Controller (MVC) pattern used, 
+for instance, in Django.
+As I wrote out the code I found it very appealing that I did not need 
+to change the subject at all to add new observers.