From b303417f653d149852e163bf3e2e3edf5c6b71a0 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Mon, 27 May 2024 21:09:40 +1000 Subject: [PATCH] doc/cephfs: s/subvolumegroups/subvolume groups Use the term "subvolume groups" instead of "subvolumegroups" where the term appears in plain English. The string "subvolumegroups" is correct in commands, and remains unchanged. Also add formatting to command output, to make clearer that the output is indeed output. Fixes: https://github.com/ceph/ceph/pull/57574#discussion_r1606988766 Signed-off-by: Zac Dover --- doc/cephfs/fs-volumes.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/cephfs/fs-volumes.rst b/doc/cephfs/fs-volumes.rst index afb21f2c4018f..381e02190ebc8 100644 --- a/doc/cephfs/fs-volumes.rst +++ b/doc/cephfs/fs-volumes.rst @@ -228,8 +228,8 @@ following form: The ``exist`` command outputs: -* "subvolumegroup exists": if any subvolumegroup is present -* "no subvolumegroup exists": if no subvolumegroup is present +* ``subvolumegroup exists``: if any subvolumegroup is present +* ``no subvolumegroup exists``: if no subvolumegroup is present .. note:: This command checks for the presence of custom groups and not presence of the default one. A subvolumegroup-existence check alone is not @@ -902,7 +902,7 @@ to policies. This can distribute load across MDS ranks in predictable and stable ways. Review :ref:`cephfs-pinning` and :ref:`cephfs-ephemeral-pinning` for details on how pinning works. -Run a command of the following form to configure pinning for subvolumegroups: +Run a command of the following form to configure pinning for subvolume groups: .. prompt:: bash # -- 2.39.5