Browse code

Fix typo in btrfs userguide doc

Signed-off-by: Samuel Dion-Girardeau <samuel.diongirardeau@gmail.com>

Samuel Dion-Girardeau authored on 2015/12/24 05:10:01
Showing 1 changed files
... ...
@@ -12,7 +12,7 @@ parent = "mn_storage_docker"
12 12
 
13 13
 Btrfs is a next generation copy-on-write filesystem that supports many advanced
14 14
 storage technologies that make it a good fit for Docker. Btrfs is included in
15
-the mainline Linux kernel and it's on-disk-format is now considered stable.
15
+the mainline Linux kernel and its on-disk-format is now considered stable.
16 16
 However, many of its features are still under heavy development and users should
17 17
 consider it a fast-moving target.
18 18
 
... ...
@@ -47,7 +47,7 @@ Snapshots are a point-in-time read-write copy of an entire subvolume. They exist
47 47
 
48 48
 Btfs allocates space to subvolumes and snapshots on demand from an underlying pool of storage. The unit of allocation is referred to as a *chunk* and *chunks* are normally ~1GB in size.
49 49
 
50
-Snapshots are first-class citizens in a Btrfs filesystem. This means that they look, feel, and operate just like regular subvolumes. The technology required to create them is built directly into the Btrfs filesystem thanks to its native copy-on-write design. This means that Btrfs snapshots are space efficient with little or no performance overhead. The diagram below shows a subvolume and it's snapshot sharing the same data.
50
+Snapshots are first-class citizens in a Btrfs filesystem. This means that they look, feel, and operate just like regular subvolumes. The technology required to create them is built directly into the Btrfs filesystem thanks to its native copy-on-write design. This means that Btrfs snapshots are space efficient with little or no performance overhead. The diagram below shows a subvolume and its snapshot sharing the same data.
51 51
 
52 52
 ![](images/btfs_pool.jpg)
53 53
 
... ...
@@ -91,7 +91,7 @@ ubuntu              latest              0a17decee413        2 weeks ago
91 91
 <none>              <none>              f9a9f253f610        2 weeks ago         188.1 MB
92 92
 ```
93 93
 
94
-Each image layer exists as a Btrfs subvolume or snapshot with the same name as it's image ID as illustrated by the `btrfs subvolume list` command shown below:
94
+Each image layer exists as a Btrfs subvolume or snapshot with the same name as its image ID as illustrated by the `btrfs subvolume list` command shown below:
95 95
 
96 96
 ```bash
97 97
 $ sudo btrfs subvolume list /var/lib/docker