Browse code

fixed two readme typos

Dan Stine authored on 2014/04/04 21:12:17
Showing 1 changed files
... ...
@@ -3,7 +3,7 @@
3 3
 #### background
4 4
 
5 5
 libcontainer specifies configuration options for what a container is.  It provides a native Go implementation 
6
-for using linux namespaces with no external dependencies.  libcontainer provides many convience functions for working with namespaces, networking, and management.  
6
+for using linux namespaces with no external dependencies.  libcontainer provides many convenience functions for working with namespaces, networking, and management.  
7 7
 
8 8
 
9 9
 #### container
... ...
@@ -91,7 +91,7 @@ Sample `container.json` file:
91 91
 ```
92 92
 
93 93
 Using this configuration and the current directory holding the rootfs for a process, one can use libcontainer to exec the container. Running the life of the namespace, a `pid` file 
94
-is written to the current directory with the pid of the namespaced process to the external world.  A client can use this pid to wait, kill, or perform other operation with the container.  If a user tries to run an new process inside an existing container with a live namespace the namespace will be joined by the new process.
94
+is written to the current directory with the pid of the namespaced process to the external world.  A client can use this pid to wait, kill, or perform other operation with the container.  If a user tries to run a new process inside an existing container with a live namespace the namespace will be joined by the new process.
95 95
 
96 96
 
97 97
 You may also specify an alternate root place where the `container.json` file is read and where the `pid` file will be saved.