Patchwork [2/7] dm: documentation fix

login
register
mail settings
Submitter amulhern@redhat.com
Date Nov. 27, 2017, 3:02 p.m.
Message ID <20171127150245.27959-2-amulhern@redhat.com>
Download mbox | patch
Permalink /patch/10076983/
State Accepted, archived
Delegated to: Mike Snitzer
Headers show

Comments

amulhern@redhat.com - Nov. 27, 2017, 3:02 p.m.
From: mulhern <amulhern@redhat.com>

Use possessive pronoun where appropriate

Instead of contraction.

Signed-off-by: mulhern <amulhern@redhat.com>
---
 Documentation/device-mapper/cache-policies.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Patch

diff --git a/Documentation/device-mapper/cache-policies.txt b/Documentation/device-mapper/cache-policies.txt
index d3ca8af..86786d8 100644
--- a/Documentation/device-mapper/cache-policies.txt
+++ b/Documentation/device-mapper/cache-policies.txt
@@ -60,7 +60,7 @@  Memory usage:
 The mq policy used a lot of memory; 88 bytes per cache block on a 64
 bit machine.
 
-smq uses 28bit indexes to implement it's data structures rather than
+smq uses 28bit indexes to implement its data structures rather than
 pointers.  It avoids storing an explicit hit count for each block.  It
 has a 'hotspot' queue, rather than a pre-cache, which uses a quarter of
 the entries (each hotspot block covers a larger area than a single
@@ -84,7 +84,7 @@  resulting in better promotion/demotion decisions.
 
 Adaptability:
 The mq policy maintained a hit count for each cache block.  For a
-different block to get promoted to the cache it's hit count has to
+different block to get promoted to the cache its hit count has to
 exceed the lowest currently in the cache.  This meant it could take a
 long time for the cache to adapt between varying IO patterns.