doc: fix LRC documentation

Recovery from a failure in jerasure need only k reads and
not k+m-1.

Signed-off-by: Danny Al-Gaaf <danny.al-gaaf@bisect.de>

diff --git a/doc/rados/operations/erasure-code-lrc.rst b/doc/rados/operations/erasure-code-lrc.rst
index eeb07a385758f8d294b019e497cc65dca229aa27..348fc164d003a1d432bf026e0776befcffdbd8be 100644 (file)
--- a/doc/rados/operations/erasure-code-lrc.rst
+++ b/doc/rados/operations/erasure-code-lrc.rst
@@ -5,14 +5,14 @@ Locally repairable erasure code plugin
 With the *jerasure* plugin, when an erasure coded object is stored on
 multiple OSDs, recovering from the loss of one OSD requires reading
 from all the others. For instance if *jerasure* is configured with
-*k=8* and *m=4*, losing one OSD requires reading from the eleven
+*k=8* and *m=4*, losing one OSD requires reading from the eight
 others to repair.
 
 The *lrc* erasure code plugin creates local parity chunks to be able
 to recover using less OSDs. For instance if *lrc* is configured with
 *k=8*, *m=4* and *l=4*, it will create an additional parity chunk for
 every four OSDs. When a single OSD is lost, it can be recovered with
-only four OSDs instead of eleven.
+only four OSDs instead of eight.
 
 Erasure code profile examples
 =============================