updates

Author: Sean-Bradley

abstract_factory/README.md

@@ -8,7 +8,7 @@ To begin with, in simple terms, think if it as a Factory that can return Factori
 
 ## Terminology
 
-* **Client**: The client application that calls the **Abstract Factory** and **Abstract Product** classes. It's the same process as the concrete creator in the [Factory](factory.md#terminology) design pattern.
+* **Client**: The client application that calls the **Abstract Factory** and **Abstract Product** classes. It's the same process as the concrete creator in the [Factory](factory#terminology) design pattern.
 
 * **Abstract Factory**: An interface to one of the Factories.
 

factory/README.md

@@ -101,7 +101,7 @@ and it will still work.
 
 While it is possible to ensure your classes are correct without using abstract classes, it is often easier to use abstract classes as a backup method of checking correctness, especially if your projects become very large and involve many developers.
 
-Note that in all my code examples, the abstract classes are prefixed with a capital **I**, to indicate that they are abstract interfaces. They have no code in their methods. They do not require a `self` or `cls` argument due to the use of `@staticmethod` . The inheriting class will implement the code in each of the methods that the abstract class is describing. If subclasses are inheriting an abstract base class, and they do not implement the methods as described, there will be [Pylint error or warning message (E0110)](coding-conventions.md#common-pylint-warning-and-error-messages).
+Note that in all my code examples, the abstract classes are prefixed with a capital **I**, to indicate that they are abstract interfaces. They have no code in their methods. They do not require a `self` or `cls` argument due to the use of `@staticmethod` . The inheriting class will implement the code in each of the methods that the abstract class is describing. If subclasses are inheriting an abstract base class, and they do not implement the methods as described, there will be [Pylint error or warning message (E0110)](/coding-conventions.md#common-pylint-warning-and-error-messages).
 
 See PEP 3119 : [https://www.python.org/dev/peps/pep-3119/](https://www.python.org/dev/peps/pep-3119/)
 

mediator/README.md

@@ -97,5 +97,5 @@ So, using the `_` prevents this warning.
 * A mediator replaces a structure with many-to-many interactions between its classes and processes, with a one-to-many centralized structure where the interface supports all of the methods of the many-to-many structure, but via the mediator component instead.
 * The mediator pattern encourages usage of shared objects that can now be centrally managed and synchronized.
 * The mediator pattern creates an abstraction between two or more components which then makes a system easier to understand and manage.
-* The mediator pattern is similar to the [Facade](facade/README.md) pattern, except the Mediator is expected to transact data both ways between two or more other classes or processes that would normally interact directly with each other.
+* The mediator pattern is similar to the [Facade](facade) pattern, except the Mediator is expected to transact data both ways between two or more other classes or processes that would normally interact directly with each other.