doc: Clarification of text in ec stretch cluster design

Information regarding min_size in the EC Cluster Design doc was unclear in regards to the intention of what we want to develop. This commit is to clarify this so it is clear to readers.

Signed-off-by: Jon Bailey <jonathan.bailey1@ibm.com>

diff --git a/doc/dev/osd_internals/erasure_coding/ec_stretch_cluster.rst b/doc/dev/osd_internals/erasure_coding/ec_stretch_cluster.rst
index 07bcc61856807e0d2e30474e896ba008de366a3d..01e829d7bf527eefcd30549e2df6f215f961d21e 100644 (file)
--- a/doc/dev/osd_internals/erasure_coding/ec_stretch_cluster.rst
+++ b/doc/dev/osd_internals/erasure_coding/ec_stretch_cluster.rst
@@ -247,8 +247,7 @@ These parameters are intended for advanced users and offer finer control over th
 
 **--min_size**
   - *Definition*: The minimum number of shards required to serve I/O within a zone.
-  - *Format*: Now always specified as a target range: ``1-<num replicas>`` for replica pools, 
-              or ``<num data shards>-<num data shards>+<num coding shards>`` for EC pools.
+  - *Note*: The value should be within allowed specified ranges. For replica pools this range is ``1-<num replicas>``, for EC pools this is ``<num data shards>-<num data shards>+<num coding shards>``.
 
 **--crush_rule**
   - *Definition*: Use this CRUSH rule, instead of an auto-generated rule.