From bf0ca906f5c87826c5b2db27c25c82740c8e0ad2 Mon Sep 17 00:00:00 2001 From: Low Jeng Lam Date: Sun, 30 Oct 2016 16:03:06 +0800 Subject: [PATCH] Typo "note" --- engine/userguide/storagedriver/zfs-driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/userguide/storagedriver/zfs-driver.md b/engine/userguide/storagedriver/zfs-driver.md index d17a55dc58..398df6ebe5 100644 --- a/engine/userguide/storagedriver/zfs-driver.md +++ b/engine/userguide/storagedriver/zfs-driver.md @@ -95,7 +95,7 @@ This process of creating child layers and containers from *read-only* snapshots Container reads with the `zfs` storage driver are very simple. A newly launched container is based on a ZFS clone. This clone initially shares all of its data with the dataset it was created from. This means that read operations with the - `zfs` storage driver are fast – even if the data being read was note + `zfs` storage driver are fast – even if the data being read was not copied into the container yet. This sharing of data blocks is shown in the diagram below.