From 0e8c1b63ff46226ba739b712804d2e1d7816863d Mon Sep 17 00:00:00 2001 From: Usha Mandya <47779042+usha-mandya@users.noreply.github.com> Date: Tue, 20 Oct 2020 11:18:18 +0100 Subject: [PATCH] Minor style updates --- storage/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/storage/index.md b/storage/index.md index c2898141e3..e2f0b902eb 100644 --- a/storage/index.md +++ b/storage/index.md @@ -135,14 +135,14 @@ Some use cases for volumes include: (such as `/var/lib/docker/volumes/`). - When your application requires high-performance I/O on Docker Desktop. Volumes - are stored in the Linux VM rather than the host, which means that reads and writes + are stored in the Linux VM rather than the host, which means that the reads and writes have much lower latency and higher throughput. -- When your application requires fully native filesystem behaviour on Docker - Desktop. For example a database engine requires precise control over disk +- When your application requires fully native file system behavior on Docker + Desktop. For example, a database engine requires precise control over disk flushing to guarantee transaction durability. Volumes are stored in the Linux VM and can make these guarantees, whereas bind mounts are remoted to macOS or - Windows where the filesystems behave slightly differently. + Windows, where the file systems behave slightly differently. ## Good use cases for bind mounts