doc/mgr/dashboard: NFS management instruction review

Signed-off-by: Lenz Grimmer <lgrimmer@suse.com>

diff --git a/doc/mgr/dashboard.rst b/doc/mgr/dashboard.rst
index 5a8f14d7dccfc9dca2bb82181ee080622f1ba3c7..2cf0b14c3f927d1c28795064c21df6272ee23d66 100644 (file)
--- a/doc/mgr/dashboard.rst
+++ b/doc/mgr/dashboard.rst
@@ -81,7 +81,7 @@ various aspects of your Ceph cluster:
   counters. Display and manage (add/edit/delete) object gateway users and their
   details (e.g. quotas) as well as the users' buckets and their details (e.g.
   owner, quotas).
-* **NFS-Ganesha**: Manage NFS-Ganesha exports that are stored as RADOS objects.
+* **NFS**: Manage NFS exports of CephFS filesystems and RGW S3 buckets via NFS Ganesha.```
 
 Enabling
 --------
@@ -620,16 +620,16 @@ A log entry may look like this::
 NFS-Ganesha Management
 ----------------------
 
-Ceph Dashboard can help with the management of NFS-Ganesha exports that use
+Ceph Dashboard can manage `NFS Ganesha <http://nfs-ganesha.github.io/>`_ exports that use
 CephFS or RadosGW as their backstore.
 
 To enable this feature in Ceph Dashboard there are some assumptions that need
 to be met regarding the way NFS-Ganesha services are configured.
 
-Ceph Dashboard reads NFS-Ganesha configuration from the Ceph cluster, therefore
+The dashboard manages NFS-Ganesha config files stored in RADOS objects on the Ceph Cluster.
 NFS-Ganesha must store part of their configuration in the Ceph cluster.
 
-The NFS-Ganesha configuration stored in the Ceph cluster must follow some
+These configuration files must follow some conventions.
 conventions.
 Each export block must be stored in its own RADOS object named
 ``export-<id>``, where ``<id>`` must match the ``Export_ID`` attribute of the
@@ -650,9 +650,9 @@ Configuring NFS-Ganesha in the dashboard
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 To enable the management of NFS-Ganesha exports in Ceph Dashboard, we only
-need to tell the Dashboard, in which RADOS pool and namespace are stored the
-configuration objects. Then, Ceph Dashboard knows how search for the objects
-following the naming convention described above.
+need to tell the Dashboard, in which RADOS pool and namespace the
+configuration objects are stored. Then, Ceph Dashboard can access the objects
+by following the naming convention described above.
 
 The Dashboard command to configure the NFS-Ganesha configuration objects
 location is::
@@ -666,13 +666,13 @@ configuration objects and we can start manage the exports through the Web UI.
 Support for multiple NFS-Ganesha clusters
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Ceph Dashboard also supports the management of NFS-Ganesha export belonging
+Ceph Dashboard also supports the management of NFS-Ganesha exports belonging
 to different NFS-Ganesha clusters. An NFS-Ganesha cluster is a group of
 NFS-Ganesha service daemons sharing the same exports. Different NFS-Ganesha
 clusters are independent and don't share the exports configuration between each
 other.
 
-Each NFS-Ganesha cluster should store their configuration objects in a
+Each NFS-Ganesha cluster should store its configuration objects in a
 different RADOS pool/namespace to isolate the configuration from each other.
 
 To specify the locations of the configuration of each NFS-Ganesha cluster we
@@ -683,6 +683,6 @@ can use the same command as above but with a different value pattern::
 The ``<cluster_id>`` is an arbitrary string that should uniquely identify the
 NFS-Ganesha cluster.
 
-When configuring the Ceph Dashboard with multiple NFS-Ganesha clusters the
+When configuring the Ceph Dashboard with multiple NFS-Ganesha clusters, the
 Web UI will automatically allow to choose to which cluster an export belongs.