Fix spelling mistakes

Author: rhatdan

README.md

@@ -3,15 +3,15 @@ Default Containerized Application Labels/Annotations/Ids used to document the ap
 
 With the introduction of the [Atomic command](http://developerblog.redhat.com/2015/04/21/introducing-the-atomic-command/), we are accessing container image meta data to describe the purpose of the image or the application defined by the image.
 
-We would like to get concensus on default names.  Proposals have been made to namespace the label names defined
+We would like to get consensus on default names.  Proposals have been made to namespace the label names defined
 in Docker.  
 
 But we believe their should be some generic toplevel names defined that are not vendor specific, or
 distribution specific.  
 
-If you would like to see additional names and desciptions added please open issues and send pull requests to update this readme.
+If you would like to see additional names and descriptions added please open issues and send pull requests to update this readme.
 
-The follwing types of data are being considered:
+The following types of data are being considered:
 
 1. Labels used to describe how to use the application/image
 
@@ -35,9 +35,9 @@ The follwing types of data are being considered:
  | Vendor      | Owner of the image| 
  | URL         | Url with more information on the image|
  | Summary     | Short Description of the image|
- | Description | Detailed discription of the image|
+ | Description | Detailed description of the image|
 
-3. Annotations with container configuration that is externally accesible, to clarify the extent to which a container image is a "black box". Rather than explicit fields, this is a pattern for the key (in likeness to an Object Identifiers (OID) or the Java package naming convention).
+3. Annotations with container configuration that is externally accessible, to clarify the extent to which a container image is a "black box". Rather than explicit fields, this is a pattern for the key (in likeness to an Object Identifiers (OID) or the Java package naming convention).
 
  | `com.example.webserver.memory.max` | Maximum memory setting for "example.com" organization's webserver |
  | `com.example.webserver.memory.min` | Minimum memory setting for "example.com" organization's webserver |