@@ -193,5 +193,5 @@ reason, you may want to place heavy write workloads on data volumes.

 * [Understand images, containers, and storage drivers](imagesandcontainers.md)

 * [Select a storage driver](selectadriver.md)

-* [BTRFS storage driver in practice](btrfs-driver.md)

+* [Btrfs storage driver in practice](btrfs-driver.md)

 * [Device Mapper storage driver in practice](device-mapper-driver.md)

@@ -1,14 +1,14 @@

 <!--[metadata]>

 +++

-title = "BTRFS storage in practice"

-description = "Learn how to optimize your use of BTRFS driver."

-keywords = ["container, storage, driver, BTRFS "]

+title = "Btrfs storage in practice"

+description = "Learn how to optimize your use of Btrfs driver."

+keywords = ["container, storage, driver, Btrfs "]

 [menu.main]

 parent = "mn_storage_docker"

 +++

 <![end-metadata]-->

-# Docker and BTRFS in practice

+# Docker and Btrfs in practice

 Btrfs is a next generation copy-on-write filesystem that supports many advanced

 storage technologies that make it a good fit for Docker. Btrfs is included in

@@ -250,7 +250,7 @@ Now that you have a Btrfs filesystem mounted at `/var/lib/docker`, the daemon sh

 Your Docker host is now configured to use the `btrfs` storage driver.

-## BTRFS and Docker performance

+## Btrfs and Docker performance

 There are several factors that influence Docker's performance under the  `btrfs` storage driver.

@@ -307,4 +307,4 @@ One final point, data volumes provide the best and most predictable performance.

 * [Understand images, containers, and storage drivers](imagesandcontainers.md)

 * [Select a storage driver](selectadriver.md)

 * [AUFS storage driver in practice](aufs-driver.md)

-* [BTRFS storage driver in practice](btrfs-driver.md)

+* [Btrfs storage driver in practice](btrfs-driver.md)

@@ -251,5 +251,5 @@ For detailed information about data volumes [Managing data in containers](https:

 * [Select a storage driver](selectadriver.md)

 * [AUFS storage driver in practice](aufs-driver.md)

-* [BTRFS storage driver in practice](btrfs-driver.md)

+* [Btrfs storage driver in practice](btrfs-driver.md)

 * [Device Mapper storage driver in practice](device-mapper-driver.md)

@@ -18,10 +18,10 @@ Docker relies on driver technology to manage the storage and interactions associ

 * [Understand images, containers, and storage drivers](imagesandcontainers.md)

 * [Select a storage driver](selectadriver.md)

 * [AUFS storage driver in practice](aufs-driver.md)

-* [BTRFS storage driver in practice](btrfs-driver.md)

+* [Btrfs storage driver in practice](btrfs-driver.md)

 * [Device Mapper storage driver in practice](device-mapper-driver.md)

 * [OverlayFS in practice](overlayfs-driver.md)

-* [FS storage in practice](zfs-driver.md)

+* [ZFS storage in practice](zfs-driver.md)

 If you are new to Docker containers make sure you read ["Understand images, containers, and storage drivers"](imagesandcontainers.md) first. It explains key concepts and technologies that can help you when working with storage drivers.

@@ -26,7 +26,7 @@ Once you decide which driver is best, you set this driver on the Docker daemon a

 |--------------|---------------------|

 |OverlayFS     |`overlay`            |

 |AUFS          |`aufs`               |

-|BTRFS         |`btrfs`              |

+|Btrfs         |`btrfs`              |

 |Device Maper  |`devicemapper`       |

 |VFS*          |`vfs`                |

 |ZFS           |`zfs`                |

@@ -115,5 +115,5 @@ Whichever driver you choose, make sure it has strong community support and momen

 * [Understand images, containers, and storage drivers](imagesandcontainers.md)

 * [AUFS storage driver in practice](aufs-driver.md)

-* [BTRFS storage driver in practice](btrfs-driver.md)

+* [Btrfs storage driver in practice](btrfs-driver.md)

 * [Device Mapper storage driver in practice](device-mapper-driver.md)