diff --git a/compose/compose-file.md b/compose/compose-file.md
index c247b7dd09..0173b900db 100644
--- a/compose/compose-file.md
+++ b/compose/compose-file.md
@@ -503,7 +503,7 @@ Logging configuration for the service.
 
 The `driver`  name specifies a logging driver for the service's
 containers, as with the ``--log-driver`` option for docker run
-([documented here](/engine/reference/logging/overview.md)).
+([documented here](/engine/admin/logging/overview.md)).
 
 The default value is json-file.
 
@@ -787,7 +787,7 @@ use the specified driver.
 > Note: No path expansion will be done if you have also specified a
 > `volume_driver`.
 
-See [Docker Volumes](/engine/userguide/dockervolumes.md) and
+See [Docker Volumes](/engine/tutorials/dockervolumes.md) and
 [Volume Plugins](/engine/extend/plugins_volume.md) for more
 
 ### volumes_from
diff --git a/compose/install.md b/compose/install.md
index 0d30ec9341..9f9d4d6add 100644
--- a/compose/install.md
+++ b/compose/install.md
@@ -14,7 +14,7 @@ To install Compose, do the following:
 
      * <a href="/engine/installation/windows/" target="_blank">Windows installation</a>
 
-     * <a href="/engine/installation/ubuntulinux/" target="_blank">Ubuntu installation</a>
+     * <a href="/engine/installation/linux/ubuntulinux/" target="_blank">Ubuntu installation</a>
 
      * <a href="/engine/installation/" target="_blank">other system installations</a>
 
diff --git a/engine/userguide/storagedriver/device-mapper-driver.md b/engine/userguide/storagedriver/device-mapper-driver.md
index 9cce0e7165..5e01f231bc 100644
--- a/engine/userguide/storagedriver/device-mapper-driver.md
+++ b/engine/userguide/storagedriver/device-mapper-driver.md
@@ -373,8 +373,8 @@ If you run into repeated problems with thin pool, you can use the
 `dm.min_free_space` option to tune the Engine behavior. This value ensures that
 operations fail with a warning when the free space is at or near the minimum.
 For information, see <a
-href="/../../reference/commandline/dockerd/#storage-driver-options"
-target="_blank">the storage driver options in the Engine daemon reference</a>.<!-- fix_-->
+href="/engine/reference/commandline/dockerd/#storage-driver-options"
+target="_blank">the storage driver options in the Engine daemon reference</a>.
 
 
 ### Examine devicemapper structures on the host
diff --git a/opensource/ways/test.md b/opensource/ways/test.md
index d6a24b4eb5..80ec316d62 100644
--- a/opensource/ways/test.md
+++ b/opensource/ways/test.md
@@ -29,7 +29,7 @@ Testing documentation is relatively easy:
 ## Step 1.  Find a page in <a href="/" target="_blank">Docker's documentation</a> that contains a procedure or example you want to test.
 
 You should choose something that _should work_ on your machine. For example,
-<a href="/articles/baseimages/" target="_blank">creating
+<a href="/engine/userguide/eng-image/baseimages/" target="_blank">creating
 a base image</a> is something anyone with Docker can do. While <a
 href="https://kitematic.com/docs/managing-volumes/" target="_blank">changing
 volume directories in Kitematic</a> requires a Mac and Docker's Kitematic
diff --git a/swarm/overview.md b/swarm/overview.md
index f52523ff8f..0d2930588d 100644
--- a/swarm/overview.md
+++ b/swarm/overview.md
@@ -75,4 +75,4 @@ like-minded individuals, we have a number of open channels for communication.
 
 * To contribute code or documentation changes: please submit a [pull request on Github](https://github.com/docker/swarm/pulls).
 
-For more information and resources, please visit the [Getting Help project page](/project/get-help/).
+For more information and resources, please visit the [Getting Help project page](/opensource/get-help/).