summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormoxiegirl <mary@docker.com>2015-10-24 17:34:17 -0700
committermoxiegirl <mary@docker.com>2015-10-24 17:34:17 -0700
commitbca90f4985d8dc2e06059a5e137b515205e115e0 (patch)
tree45b72a8a59f57078a4e3cd71ef90a971481aa125
parent80439a4ce280777ded1b22842b7b6b3d4d6b574a (diff)
downloaddocker-moxiegirl-patch-README.tar.gz
Update README.mdmoxiegirl-patch-README
Update for fixes.
-rw-r--r--docs/README.md6
1 files changed, 2 insertions, 4 deletions
diff --git a/docs/README.md b/docs/README.md
index 96ded0c51a..d36457c3fc 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -26,9 +26,7 @@ contains the last release of documentation.
After a release, documentation updates are continually merged into `master` as
they occur. This work includes new documentation for forthcoming features, bug
-fixes, and other updates. Docker's CI system automatically builds and updates
-the `master` documentation after each merge and posts it to
-[http://docs.master.dockerproject.org](http://docs.master.dockerproject.org).
+fixes, and other updates.
Periodically, the Docker maintainers update `docs.docker.com` between official
releases of Docker. They do this by cherry-picking commits from `master`,
@@ -67,7 +65,7 @@ own.
The `docker/docker` repository contains a `Dockerfile` and a `Makefile`.
Together, these create a development environment in which you can build and
run a container running the Docker documentation website. To build the
- documentation site, enter `make docs` at the root of your `docker/docker`
+ documentation site, enter `make docs` in the `docs` directory of your `docker/docker`
fork:
$ make docs