doc: cleanup erasure coded pool doc on cephfs use

Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>

diff --git a/doc/rados/operations/erasure-code.rst b/doc/rados/operations/erasure-code.rst
index a85f5678b3821604ba6e0cf5506d9fa455b4229b..de0ba3647499068fb5039c2a98b075dd1feaf13c 100644 (file)
--- a/doc/rados/operations/erasure-code.rst
+++ b/doc/rados/operations/erasure-code.rst
@@ -121,7 +121,7 @@ By default, erasure coded pools only work with uses like RGW that
 perform full object writes and appends.
 
 Since Luminous, partial writes for an erasure coded pool may be
-enabled with a per-pool setting. This lets RBD and Cephfs store their
+enabled with a per-pool setting. This lets RBD and CephFS store their
 data in an erasure coded pool::
 
     ceph osd pool set ec_pool allow_ec_overwrites true
@@ -132,14 +132,14 @@ during deep-scrub. In addition to being unsafe, using filestore with
 ec overwrites yields low performance compared to bluestore.
 
 Erasure coded pools do not support omap, so to use them with RBD and
-Cephfs you must instruct them to store their data in an ec pool, and
+CephFS you must instruct them to store their data in an ec pool, and
 their metadata in a replicated pool. For RBD, this means using the
 erasure coded pool as the ``--data-pool`` during image creation::
 
     rbd create --size 1G --data-pool ec_pool replicated_pool/image_name
 
-For Cephfs, using an erasure coded pool means setting that pool in
-a `file layout <../../../cephfs/file-layouts>`_.
+For CephFS, an erasure coded pool can be set as the default data pool during
+file system creation or via `file layouts <../../../cephfs/file-layouts>`_.
 
 
 Erasure coded pool and cache tiering