From e48bff57b0dcc21c9cf72c56e308b0f2cded77ca Mon Sep 17 00:00:00 2001 From: Adeleke Akinade Date: Wed, 28 Feb 2024 13:47:54 +0000 Subject: [PATCH] Fix typos in the btrfs-driver page. --- content/storage/storagedriver/btrfs-driver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/storage/storagedriver/btrfs-driver.md b/content/storage/storagedriver/btrfs-driver.md index dd21cfefdf..ba012c1201 100644 --- a/content/storage/storagedriver/btrfs-driver.md +++ b/content/storage/storagedriver/btrfs-driver.md @@ -32,7 +32,7 @@ Btrfs Filesystem as Btrfs. - Changing the storage driver makes any containers you have already created inaccessible on the local system. Use `docker save` to save containers, and push existing images to Docker Hub or a private repository, so that you - not need to re-create them later. + do not need to re-create them later. - `btrfs` requires a dedicated block storage device such as a physical disk. This block device must be formatted for Btrfs and mounted into `/var/lib/docker/`. @@ -271,7 +271,7 @@ storage driver. Btrfs doesn't support page cache sharing. This means that each process accessing the same file copies the file into the Docker host's memory. As a -result, the `btrfs` driver may not be the best choice high-density use cases +result, the `btrfs` driver may not be the best choice for high-density use cases such as PaaS. ### Small writes