Markdown linting

Author: dancergraham

README.md

@@ -4,41 +4,41 @@
 
 I am aiming for a literal translation without trying to make the code pythonic beyond, e.g. using python conventions for `ClassNames` and `method_names` and putting all of the code in a single file where it makes sense to do so.
 
-### Sample Code : Java 
+## Sample Code : Java
 
 From the book 📖:
 
 ```java
 package headfirst.designpatterns.strategy;
 
 public abstract class Duck {
-	FlyBehavior flyBehavior;
-	QuackBehavior quackBehavior;
+    FlyBehavior flyBehavior;
+    QuackBehavior quackBehavior;
 
-	public Duck() {
-	}
+    public Duck() {
+    }
 
-	public void setFlyBehavior(FlyBehavior fb) {
-		flyBehavior = fb;
-	}
+    public void setFlyBehavior(FlyBehavior fb) {
+        flyBehavior = fb;
+    }
 
-	public void setQuackBehavior(QuackBehavior qb) {
-		quackBehavior = qb;
-	}
+    public void setQuackBehavior(QuackBehavior qb) {
+        quackBehavior = qb;
+    }
 
-	abstract void display();
+    abstract void display();
 
-	public void performFly() {
-		flyBehavior.fly();
-	}
+    public void performFly() {
+        flyBehavior.fly();
+    }
 
-	public void performQuack() {
-		quackBehavior.quack();
-	}
+    public void performQuack() {
+        quackBehavior.quack();
+    }
 
-	public void swim() {
-		System.out.println("All ducks float, even decoys!");
-	}
+    public void swim() {
+        System.out.println("All ducks float, even decoys!");
+    }
 }
 ```
 
@@ -68,4 +68,4 @@ class Duck():
 
     def swim():
         print("All ducks float, even decoys! 〰🦆〰")
-```
+```

chapter01_strategy/readme.md

@@ -1,5 +1,5 @@
 # Chapter 1: Strategy design pattern
 
-> **Strategy**: defines a family of algorithms, encapsulates each one and makes them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
+**Strategy**: defines a family of algorithms, encapsulates each one and makes them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
 
-I think the more pythonic approach would be to define methods rather than classes, and this would not violate the above definition.  The class-based approach is needed in Java and has the advantage of explicitly setting out the required method in an abstract base class. 
+I think the more pythonic approach would be to define methods rather than classes, and this would not violate the above definition.  The class-based approach is needed in Java and has the advantage of explicitly setting out the required method in an abstract base class.

chapter02_observer/readme.md

@@ -2,6 +2,6 @@
 
 > **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. 
+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 ? 
+I find the name contradictory: shouldn't it be called the 'Subject' design pattern as the subject is the key actor ?

chapter03_decorator/readme.md

@@ -1,7 +1,7 @@
 # Chapter 3: Decorator design pattern
 
-> **Decorator**: Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.
+**Decorator**: Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.
 
 Not quite the same as python decorator syntax as in python you call the _decorated function_ and the decorating function is called first whereas the _decorating function_ must be called here.
 
-I subclass `ABC` and used the `@abstractmethod` decorator from the `abc` module here but do not use any of this functionality - it just serves as documentation.
+I subclass `ABC` and used the `@abstractmethod` decorator from the `abc` module here but do not use any of this functionality - it just serves as documentation.