From b9a9789294592a3b5ed974d74e40700778cfd810 Mon Sep 17 00:00:00 2001 From: michaelspets Date: Wed, 19 Apr 2017 00:13:58 +0300 Subject: [PATCH] Fix broken link (#2870) Signed-off-by: Michael Spetsiotis --- engine/tutorials/dockervolumes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/engine/tutorials/dockervolumes.md b/engine/tutorials/dockervolumes.md index bf1ce6978e..fb3c0ed489 100644 --- a/engine/tutorials/dockervolumes.md +++ b/engine/tutorials/dockervolumes.md @@ -20,7 +20,7 @@ Docker Engine. ## Data volumes A *data volume* is a specially-designated directory within one or more -containers that bypasses the [*Union File System*](/engine/reference/glossary.md#union-file-system). +containers that bypasses the [*Union File System*](/glossary/?term=Union file system). Data volumes provide several useful features for persistent or shared data: - Volumes are initialized when a container is created. If the container's @@ -32,7 +32,7 @@ Data volumes provide several useful features for persistent or shared data: - Changes to a data volume will not be included when you update an image. - Data volumes persist even if the container itself is deleted. -Data volumes are designed to persist data, independent of the container's lifecycle. +Data volumes are designed to persist data, independent of the container's lifecycle. Docker therefore *never* automatically deletes volumes when you remove a container, nor will it "garbage collect" volumes that are no longer referenced by a container.