Browse code

Copy edits for typos

Signed-off-by: Ed Costello <epc@epcostello.com>

Ed Costello authored on 2015/08/25 12:02:44
Showing 5 changed files
... ...
@@ -11,7 +11,7 @@ weight = 7
11 11
 
12 12
 # Using certificates for repository client verification
13 13
 
14
-The orginal content was deprecated. For information about configuring
15
-cerficates, see  [deploying a registry
14
+The original content was deprecated. For information about configuring
15
+certificates, see  [deploying a registry
16 16
 server](http://docs.docker.com/registry/deploying/). To reach an older version
17 17
 of this content, refer to an older version of the documentation. 
... ...
@@ -11,7 +11,7 @@ weight = 8
11 11
 
12 12
 # Run a local registry mirror
13 13
 
14
-The orginal content was deprecated. [An archived
14
+The original content was deprecated. [An archived
15 15
 version](https://docs.docker.com/v1.6/articles/registry_mirror) is available in
16 16
 the 1.7 documentation. For information about configuring mirrors with the latest
17 17
 Docker Registry version, please file a support request with [the Distribution
... ...
@@ -41,7 +41,7 @@ Your machine must be running Windows 7, 8/8.1 or newer to run Docker. Windows 10
41 41
     upgrading your operating system in order to try out Docker.
42 42
 
43 43
 2. Make sure your CPU supports [virtualization technology](https://en.wikipedia.org/wiki/X86_virtualization) 
44
-and virtualzation support is enabled in BIOS and recognized by Windows.
44
+and virtualization support is enabled in BIOS and recognized by Windows.
45 45
 
46 46
     #### For Windows 8 or 8.1
47 47
 
... ...
@@ -668,8 +668,8 @@ limit and "K" the kernel limit. There are three possible ways to set limits:
668 668
       <td class="no-wrap"><strong>U != 0, K &lt; U</strong></td>
669 669
       <td>
670 670
         Kernel memory is a subset of the user memory. This setup is useful in
671
-        deployments where the total amount of memory per-cgroup is overcommited.
672
-        Overcommiting kernel memory limits is definitely not recommended, since the
671
+        deployments where the total amount of memory per-cgroup is overcommitted.
672
+        Overcommitting kernel memory limits is definitely not recommended, since the
673 673
         box can still run out of non-reclaimable memory.
674 674
         In this case, the you can configure K so that the sum of all groups is
675 675
         never greater than the total memory. Then, freely set U at the expense of
... ...
@@ -679,7 +679,7 @@ limit and "K" the kernel limit. There are three possible ways to set limits:
679 679
     <tr>
680 680
       <td class="no-wrap"><strong>U != 0, K &gt; U</strong></td>
681 681
       <td>
682
-        Since kernel memory charges are also fed to the user counter and reclaimation
682
+        Since kernel memory charges are also fed to the user counter and reclamation
683 683
         is triggered for the container for both kinds of memory. This configuration
684 684
         gives the admin a unified view of memory. It is also useful for people
685 685
         who just want to track kernel memory usage.
... ...
@@ -89,7 +89,7 @@ So, you'll need an entry for both the servers in your local `/etc/hosts` file.
89 89
 3. Create a `notarytest` directory then change into that.
90 90
 
91 91
         $ mkdir notarytest
92
-        $ cd nostarytest
92
+        $ cd notarytest
93 93
 
94 94
 4. Create a filed called `Dockerfile` with your favorite editor.
95 95
 
... ...
@@ -191,7 +191,7 @@ root@0710762bb59a:/#
191 191
 ```
192 192
 
193 193
 Mounting the `docker.sock` gives the `notarysandbox` access to the `docker`
194
-deamon on your host, while storing all the keys and files inside the sandbox
194
+daemon on your host, while storing all the keys and files inside the sandbox
195 195
 container.  When you destroy the container, you destroy the "play" keys.
196 196
 
197 197
 ### Test some trust operations