doc/rados/operations/crush-map: s/die/dice/

Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>

diff --git a/doc/rados/operations/crush-map.rst b/doc/rados/operations/crush-map.rst
index 20e492180c48164137d8bc58482387a3e088b2f0..a3403e30e6facbc1e08df66aec23723367b55ae4 100644 (file)
--- a/doc/rados/operations/crush-map.rst
+++ b/doc/rados/operations/crush-map.rst
@@ -216,7 +216,7 @@ device in the CRUSH map are set based on the device size and indicate
 how much data we *should* be storing where.  However, because CRUSH is
 based on a pseudorandom placement process, there is always some
 variation from this ideal distribution, the same way that rolling a
-die sixty times will not result in rolling exactly 10 ones and 10
+dice sixty times will not result in rolling exactly 10 ones and 10
 sixes.  Weight sets allow the cluster to do a numerical optimization
 based on the specifics of your cluster (hierarchy, pools, etc.) to achieve
 a balanced distribution.