get better readme

Author: QianMo

Assets/Abstract Factory Pattern/README.md

@@ -12,15 +12,15 @@ Provide an interface for creating families of related or dependent objects witho
 The classes and objects participating in this pattern are:
 
 ###AbstractFactory (ContinentFactory)
-declares an interface for operations that create abstract products
+* declares an interface for operations that create abstract products
 ###ConcreteFactory (AfricaFactory, AmericaFactory)
-implements the operations to create concrete product objects
+* implements the operations to create concrete product objects
 ###AbstractProduct (Herbivore, Carnivore)
-declares an interface for a type of product object
+* declares an interface for a type of product object
 ###Product (Wildebeest, Lion, Bison, Wolf)
-defines a product object to be created by the corresponding concrete factory
-implements the AbstractProduct interface
+* defines a product object to be created by the corresponding concrete factory
+* implements the AbstractProduct interface
 ###Client (AnimalWorld)
-uses interfaces declared by AbstractFactory and AbstractProduct classes
+* uses interfaces declared by AbstractFactory and AbstractProduct classes
 
 

Assets/Adapter Pattern/README.md

@@ -10,12 +10,12 @@ Convert the interface of a class into another interface clients expect. Adapter
 The classes and objects participating in this pattern are:
 
 ###Target (ChemicalCompound)
-defines the domain-specific interface that Client uses.
+* defines the domain-specific interface that Client uses.
 ###Adapter (Compound)
-adapts the interface Adaptee to the Target interface.
+* adapts the interface Adaptee to the Target interface.
 ###Adaptee (ChemicalDatabank)
-defines an existing interface that needs adapting.
+* defines an existing interface that needs adapting.
 ###Client (AdapterApp)
-collaborates with objects conforming to the Target interface.
+* collaborates with objects conforming to the Target interface.
 
 

Assets/Bridge Pattern/README.md

@@ -2,7 +2,7 @@
 ##Definition
 
 Decouple an abstraction from its implementation so that the two can vary independently.
-<br>将抽象化(Abstraction)与实现化(Implementation)脱耦，使得二者可以独立地变化。
+<br>将抽象和实现解耦，使得两者可以独立地变化。
 
 ![](https://github.com/QianMo/Unity-Design-Pattern/blob/master/UML_Picture/bridge.gif)
 
@@ -12,12 +12,12 @@ Decouple an abstraction from its implementation so that the two can vary indepen
 The classes and objects participating in this pattern are:
 
 ###Abstraction (BusinessObject)
-defines the abstraction's interface.
-maintains a reference to an object of type Implementor.
+* defines the abstraction's interface.
+* maintains a reference to an object of type Implementor.
 ###RefinedAbstraction (CustomersBusinessObject)
-extends the interface defined by Abstraction.
+* extends the interface defined by Abstraction.
 ###Implementor (DataObject)
-defines the interface for implementation classes. This interface doesn't have to correspond exactly to Abstraction's interface; in fact the two interfaces can be quite different. Typically the Implementation interface provides only primitive operations, and Abstraction defines higher-level operations based on these primitives.
+* defines the interface for implementation classes. This interface doesn't have to correspond exactly to Abstraction's interface; in fact the two interfaces can be quite different. Typically the Implementation interface provides only primitive operations, and Abstraction defines higher-level operations based on these primitives.
 ###ConcreteImplementor (CustomersDataObject)
-implements the Implementor interface and defines its concrete implementation.
+* implements the Implementor interface and defines its concrete implementation.
 

Assets/Builder Pattern/README.md

@@ -12,14 +12,14 @@ Separate the construction of a complex object from its representation so that th
 The classes and objects participating in this pattern are:
 
 ###Builder (VehicleBuilder)
-specifies an abstract interface for creating parts of a Product object
+* specifies an abstract interface for creating parts of a Product object
 ###ConcreteBuilder (MotorCycleBuilder, CarBuilder, ScooterBuilder)
-constructs and assembles parts of the product by implementing the Builder interface
-defines and keeps track of the representation it creates
-provides an interface for retrieving the product
+* constructs and assembles parts of the product by implementing the Builder interface
+* defines and keeps track of the representation it creates
+* provides an interface for retrieving the product
 ###Director (Shop)
-constructs an object using the Builder interface
+* constructs an object using the Builder interface
 ###Product (Vehicle)
-represents the complex object under construction. ConcreteBuilder builds the product's internal representation and defines the process by which it's assembled
-includes classes that define the constituent parts, including interfaces for assembling the parts into the final result
+* represents the complex object under construction. ConcreteBuilder builds the product's internal representation and defines the process by which it's assembled
+* includes classes that define the constituent parts, including interfaces for assembling the parts into the final result
 

Assets/Chain of Responsibility Pattern/README.md

@@ -12,12 +12,12 @@ Avoid coupling the sender of a request to its receiver by giving more than one o
 The classes and objects participating in this pattern are:
 
 ###Handler (Approver)
-defines an interface for handling the requests
-(optional) implements the successor link
+* defines an interface for handling the requests
+* (optional) implements the successor link
 ###ConcreteHandler (Director, VicePresident, President)
-handles requests it is responsible for
-can access its successor
-if the ConcreteHandler can handle the request, it does so; otherwise it forwards the request to its successor
+* handles requests it is responsible for
+* can access its successor
+* if the ConcreteHandler can handle the request, it does so; otherwise it forwards the request to its successor
 ###Client (ChainApp)
-initiates the request to a ConcreteHandler object on the chain
+* initiates the request to a ConcreteHandler object on the chain
 

Assets/Command Pattern/README.md

@@ -10,16 +10,16 @@ Encapsulate a request as an object, thereby letting you parameterize clients wit
 The classes and objects participating in this pattern are:
 
 ###Command
-declares an interface for executing an operation
+* declares an interface for executing an operation
 ###ConcreteCommand
-defines a binding between a Receiver object and an action
-implements Execute by invoking the corresponding operation(s) on Receiver
+* defines a binding between a Receiver object and an action
+* implements Execute by invoking the corresponding operation(s) on Receiver
 ###Client 
-creates a ConcreteCommand object and sets its receiver
+* creates a ConcreteCommand object and sets its receiver
 ###Invoker
-asks the command to carry out the request
+* asks the command to carry out the request
 ###Receiver
-knows how to perform the operations associated with carrying out the request.
+* knows how to perform the operations associated with carrying out the request.
 
 
 

Assets/Composite Pattern/README.md

@@ -12,17 +12,17 @@ Compose objects into tree structures to represent part-whole hierarchies. Compos
 The classes and objects participating in this pattern are:
 
 ###Component (DrawingElement)
-declares the interface for objects in the composition.
-implements default behavior for the interface common to all classes, as appropriate.
-declares an interface for accessing and managing its child components.
-(optional) defines an interface for accessing a component's parent in the recursive structure, and implements it if that's appropriate.
+* declares the interface for objects in the composition.
+* implements default behavior for the interface common to all classes, as appropriate.
+* declares an interface for accessing and managing its child components.
+* (optional) defines an interface for accessing a component's parent in the recursive structure, and implements it if that's appropriate.
 ###Leaf (PrimitiveElement)
-represents leaf objects in the composition. A leaf has no children.
-defines behavior for primitive objects in the composition.
+* represents leaf objects in the composition. A leaf has no children.
+* defines behavior for primitive objects in the composition.
 ###Composite (CompositeElement)
-defines behavior for components having children.
-stores child components.
-implements child-related operations in the Component interface.
+* defines behavior for components having children.
+* stores child components.
+* implements child-related operations in the Component interface.
 ###Client (CompositeApp)
-manipulates objects in the composition through the Component interface.
+* manipulates objects in the composition through the Component interface.
 

Assets/Decorator Pattern/README.md

@@ -12,11 +12,11 @@ Attach additional responsibilities to an object dynamically. Decorators provide
 The classes and objects participating in this pattern are:
 
 ###Component (LibraryItem)
-defines the interface for objects that can have responsibilities added to them dynamically.
+* defines the interface for objects that can have responsibilities added to them dynamically.
 ###ConcreteComponent (Book, Video)
-defines an object to which additional responsibilities can be attached.
-Decorator (Decorator)
-maintains a reference to a Component object and defines an interface that conforms to Component's interface.
+* defines an object to which additional responsibilities can be attached.
+###Decorator (Decorator)
+* maintains a reference to a Component object and defines an interface that conforms to Component's interface.
 ###ConcreteDecorator (Borrowable)
-adds responsibilities to the component.
+* adds responsibilities to the component.
 

Assets/Facade Pattern/README.md

@@ -12,10 +12,10 @@ Provide a unified interface to a set of interfaces in a subsystem. Façade defin
 The classes and objects participating in this pattern are:
 
 ###Facade (MortgageApplication)
-knows which subsystem classes are responsible for a request.
-delegates client requests to appropriate subsystem objects.
+* knows which subsystem classes are responsible for a request.
+* delegates client requests to appropriate subsystem objects.
 ###Subsystem classes (Bank, Credit, Loan)
-implement subsystem functionality.
-handle work assigned by the Facade object.
-have no knowledge of the facade and keep no reference to it.
+* implement subsystem functionality.
+* handle work assigned by the Facade object.
+* have no knowledge of the facade and keep no reference to it.
 

Assets/Factory Method Pattern/README.md

@@ -12,12 +12,12 @@ Define an interface for creating an object, but let subclasses decide which clas
 The classes and objects participating in this pattern are:
 
 ###Product (Page)
-defines the interface of objects the factory method creates
-ConcreteProduct (SkillsPage, EducationPage, ExperiencePage)
-implements the Product interface
+* defines the interface of objects the factory method creates
+* ConcreteProduct (SkillsPage, EducationPage, ExperiencePage)
+* implements the Product interface
 ###Creator (Document)
-declares the factory method, which returns an object of type Product. Creator may also define a default implementation of the factory method that returns a default ConcreteProduct object.
-may call the factory method to create a Product object.
+* declares the factory method, which returns an object of type Product. Creator may also define a default implementation of the factory method that returns a default ConcreteProduct object.
+* may call the factory method to create a Product object.
 ###ConcreteCreator (Report, Resume)
-overrides the factory method to return an instance of a ConcreteProduct.
+* overrides the factory method to return an instance of a ConcreteProduct.