Carry of PR #13520

Removinig files

Signed-off-by: Mary Anthony <mary@docker.com>

docs/README.md

@@ -288,3 +288,4 @@ project.
 
 
 
+

docs/sources/articles/security.md

@@ -262,7 +262,7 @@ Docker containers are, by default, quite secure; especially if you take
 care of running your processes inside the containers as non-privileged
 users (i.e., non-`root`).
 
-You can add an extra layer of safety by enabling Apparmor, SELinux,
+You can add an extra layer of safety by enabling AppArmor, SELinux,
 GRSEC, or your favorite hardening solution.
 
 Last but not least, if you see interesting security features in other

docs/sources/docker-hub-enterprise/release-notes.md

@@ -22,8 +22,8 @@ page_keywords: docker, documentation, about, technology, understanding, enterpri
 ### CS Docker Engine 1.6.2-cs5
 (21 May 2015)
 
-For customers running Docker Engine on [supported versions of RedHat Enterprise
-Linux](https://www.docker.com/enterprise/support/) with [SELinux
+For customers running Docker Engine on [supported versions of Red Hat Enterprise
+Linux (RHEL)](https://www.docker.com/enterprise/support/) with [SELinux
 enabled](https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/
 6/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux
 -Enabling_and_Disabling_SELinux.html), the `docker build` and `docker run`

docs/sources/docker-hub/builds.md

@@ -225,7 +225,7 @@ Follow the steps below to configure the GitHub Service hooks for your Automated
     <tr>
       <td>1.</td>
       <td><img src="/docker-hub/hub-images/gh_settings.png"></td>
-      <td>Log in to Github.com, and go to your Repository page. Click on "Settings" on
+      <td>Log in to GitHub.com, and go to your Repository page. Click on "Settings" on
       the right side of the page. You must have admin privileges to the repository in order to do this.</td>
     </tr>
     <tr>

docs/sources/installation/binaries.md

@@ -87,7 +87,7 @@ To set the file's execute bit on Linux and OS X:
 
     $ chmod +x docker
 
-To get the list of stable release version numbers from Github, view the
+To get the list of stable release version numbers from GitHub, view the
 `docker/docker` [releases page](https://github.com/docker/docker/releases). 
 
 > **Note**

docs/sources/installation/mac.md

@@ -346,7 +346,7 @@ Use `boot2docker help` to list the full command line reference. For more
 information about using SSH or SCP to access the Boot2Docker VM, see the README
 at  [Boot2Docker repository](https://github.com/boot2docker/boot2docker).
 
-Thanks to Chris Jones whose [blog](http://goo.gl/Be6cCk)  inspired me to redo
-this page.
+Thanks to Chris Jones whose [blog](http://viget.com/extend/how-to-use-docker-on-os-x-the-missing-guide)  
+inspired me to redo this page.
 
 Continue with the [Docker User Guide](/userguide/).

docs/sources/installation/softlayer.md

@@ -1,5 +1,5 @@
 page_title: Installation on IBM SoftLayer 
-page_description: Installation instructions for Docker on IBM Softlayer.
+page_description: Installation instructions for Docker on IBM SoftLayer.
 page_keywords: IBM SoftLayer, virtualization, cloud, docker, documentation, installation
 
 # IBM SoftLayer

docs/sources/installation/windows.md

@@ -130,7 +130,7 @@ to you using:
 
     boot2docker ip
 
-Typically, it is 192.168.59.103, but it could get changed by Virtualbox's DHCP
+Typically, it is 192.168.59.103, but it could get changed by VirtualBox's DHCP
 implementation.
 
 For further information or to report issues, please see the [Boot2Docker site](http://boot2docker.io)

docs/sources/project/advanced-contributing.md

@@ -147,6 +147,6 @@ Making a pull request with a design proposal simplifies this process:
 * you can leave comments on specific design proposal line
 * replies around line are easy to track
 * as a proposal changes and is updated, pages reset as line items resolve
-* Github maintains the entire history
+* GitHub maintains the entire history
 
 While proposals in pull requests do not end up merged into a master repository, they provide a convenient tool for managing the design process.

docs/sources/project/doc-style.md

@@ -207,7 +207,7 @@ Text taken from a GUI (e.g., menu text or button text) should appear in "double
 quotes". The text should take the exact same capitalisation, etc. as appears in
 the GUI. E.g., Click "Continue" to save the settings.
 
-Text that refers to a keyboard command or hotkey is  capitalized (e.g., Ctrl-D).
+Text that refers to a keyboard command or hotkey is capitalized (e.g., Ctrl-D).
 
 When writing CLI examples, give the user hints by making the examples resemble
 exactly what they see in their shell: 

docs/sources/project/set-up-git.md

@@ -225,7 +225,7 @@ the branch to your fork on GitHub:
          * [new branch]      dry-run-test -> dry-run-test
         Branch dry-run-test set up to track remote branch dry-run-test from origin.
 
-9. Open your browser to Github.
+9. Open your browser to GitHub.
 
 10. Navigate to your Docker fork.
 

docs/sources/project/software-req-win.md

@@ -191,8 +191,8 @@ In this section, you install the Go language. Then, you build the source so that
 
 ## Get the Docker repository
 
-In this step, you start a Git `bash` terminal and get the Docker source code from
-Github. 
+In this step, you start a Git `bash` terminal and get the Docker source code 
+from GitHub. 
 
 1. Locate the **Git Bash** program and start it.
 

docs/sources/reference/api/docker_remote_api_v1.6.md

@@ -178,7 +178,7 @@ Status Codes:
              "Warnings":[]
         }
 
-    **Second, start (using the ID returned above) the image we jus
+    **Second, start (using the ID returned above) the image we just
     created, mapping the ssh port 22 to something on the host**:
 
         POST /containers/e90e34656806/start HTTP/1.1
@@ -190,7 +190,7 @@ Status Codes:
 
 **Example response**:
 
-        HTTP/1.1 204 No Conten
+        HTTP/1.1 204 No Content
         Content-Type: text/plain; charset=utf-8
         Content-Length: 0
 

docs/sources/reference/commandline/cli.md

@@ -698,13 +698,13 @@ to any of the files in the context. For example, your build can use an
 [*ADD*](/reference/builder/#add) instruction to reference a file in the
 context.
 
-The `URL` parameter can specify the location of a Git repository; the
-repository acts as the build context. The system recursively clones the
-repository and its submodules using a `git clone --depth 1 --recursive`
-command. This command runs in a temporary directory on your local host. After
-the command succeeds, the directory is sent to the Docker daemon as the
-context. Local clones give you the ability to access private repositories using
-local user credentials, VPN's, and so forth.
+The `URL` parameter can specify the location of a Git repository; the repository
+acts as the build context. The system recursively clones the repository and its
+submodules using a `git clone --depth 1 --recursive` command. This command runs
+in a temporary directory on your local host. After the command succeeds, the
+directory is sent to the Docker daemon as the context. Local clones give you the
+ability to access private repositories using local user credentials, VPNs, and
+so forth.
 
 Git URLs accept context configuration in their fragment section, separated by a
 colon `:`.  The first part represents the reference that Git will check out,

docs/sources/reference/glossary.md

@@ -90,7 +90,7 @@ Docker and its components. It provides the following services:
 - Docker image hosting
 - User authentication
 - Automated image builds and work-flow tools such as build triggers and web hooks
-- Integration with GitHub and BitBucket
+- Integration with GitHub and Bitbucket
 
 
 ## Dockerfile

docs/sources/release-notes.md

@@ -40,7 +40,7 @@ repository](https://github.com/docker/docker/issues/).
 An idiosyncrasy in AUFS prevented permissions from propagating predictably
 between upper and lower layers. This caused issues with accessing private
 keys, database instances, etc.  This issue was closed in this release:
-[Github Issue 783](https://github.com/docker/docker/issues/783).
+[GitHub Issue 783](https://github.com/docker/docker/issues/783).
 
 
 * *Docker Hub incompatible with Safari 8*

docs/sources/userguide/dockerhub.md

@@ -16,7 +16,7 @@ most out of Docker. To do this, it provides services such as:
 * User authentication.
 * Automated image builds and work-flow tools such as build triggers and web
   hooks.
-* Integration with GitHub and BitBucket.
+* Integration with GitHub and Bitbucket.
 
 In order to use Docker Hub, you will first need to register and create an account. Don't
 worry, creating an account is simple and free.

docs/sources/userguide/dockerrepos.md

@@ -118,16 +118,16 @@ manage private repositories. You can learn how to create and manage an organizat
 ### Automated Builds
 
 Automated Builds automate the building and updating of images from
-[GitHub](https://www.github.com) or [BitBucket](http://bitbucket.com), directly on Docker
-Hub. It works by adding a commit hook to your selected GitHub or BitBucket repository,
+[GitHub](https://www.github.com) or [Bitbucket](http://bitbucket.com), directly on Docker
+Hub. It works by adding a commit hook to your selected GitHub or Bitbucket repository,
 triggering a build and update when you push a commit.
 
 #### To setup an Automated Build
 
 1.  Create a [Docker Hub account](https://hub.docker.com/) and login.
-2.  Link your GitHub or BitBucket account through the ["Link Accounts"](https://registry.hub.docker.com/account/accounts/) menu.
+2.  Link your GitHub or Bitbucket account through the ["Link Accounts"](https://registry.hub.docker.com/account/accounts/) menu.
 3.  [Configure an Automated Build](https://registry.hub.docker.com/builds/add/).
-4.  Pick a GitHub or BitBucket project that has a `Dockerfile` that you want to build.
+4.  Pick a GitHub or Bitbucket project that has a `Dockerfile` that you want to build.
 5.  Pick the branch you want to build (the default is the `master` branch).
 6.  Give the Automated Build a name.
 7.  Assign an optional Docker tag to the Build.
@@ -135,7 +135,7 @@ triggering a build and update when you push a commit.
 
 Once the Automated Build is configured it will automatically trigger a
 build and, in a few minutes, you should see your new Automated Build on the [Docker Hub](https://hub.docker.com)
-Registry. It will stay in sync with your GitHub and BitBucket repository until you
+Registry. It will stay in sync with your GitHub and Bitbucket repository until you
 deactivate the Automated Build.
 
 If you want to see the status of your Automated Builds, you can go to your
@@ -144,7 +144,7 @@ and it will show you the status of your builds and their build history.
 
 Once you've created an Automated Build you can deactivate or delete it. You
 cannot, however, push to an Automated Build with the `docker push` command.
-You can only manage it by committing code to your GitHub or BitBucket
+You can only manage it by committing code to your GitHub or Bitbucket
 repository.
 
 You can create multiple Automated Builds per repository and configure them

docs/sources/userguide/dockervolumes.md

@@ -80,9 +80,9 @@ directory from your Docker daemon's host into a container.
 
 > **Note:**
 > If you are using Boot2Docker, your Docker daemon only has limited access to
-> your OSX/Windows filesystem. Boot2Docker tries to auto-share your `/Users`
-> (OSX) or `C:\Users` (Windows) directory - and so you can mount files or directories
-> using `docker run -v /Users/<path>:/<container path> ...` (OSX) or
+> your OS X/Windows filesystem. Boot2Docker tries to auto-share your `/Users`
+> (OS X) or `C:\Users` (Windows) directory - and so you can mount files or directories
+> using `docker run -v /Users/<path>:/<container path> ...` (OS X) or
 > `docker run -v /c/Users/<path>:/<container path ...` (Windows). All other paths
 > come from the Boot2Docker virtual machine's filesystem.
 

docs/sources/userguide/level2.md

@@ -74,7 +74,7 @@ RUN apt-get install -y <input id="gcc" class="l_fill" type="text"><br>
 <input id="run6" class="l_fill" type="text">cd redis-stable && make && make install<br>
 &#35; launch redis when starting the image
 <input id="entrypoint" class="l_fill" type="text"> ["redis-server"]<br>
-&#35; run as user dameon
+&#35; run as user daemon
 <input id="user" class="l_fill" type="text"> daemon<br>
 &#35; expose port 6379
 <input id="expose" class="l_fill" type="text"> 6379