From: Nathan Cutler <ncutler@suse.com>
Date: Tue, 8 Sep 2020 06:30:48 +0000 (+0200)
Subject: doc: cephfs/fs-nfs-exports: use "NFS Ganesha" everywhere
X-Git-Tag: v15.2.8~5^2~1^2~39^2~3
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=0c0d3e137cd2726d8bbeb70a9af223608f972f68;p=ceph.git

doc: cephfs/fs-nfs-exports: use "NFS Ganesha" everywhere

The document seemed to be wanting to refer to the software as "NFS
Ganesha", but was failing to do so in some places.

Signed-off-by: Nathan Cutler <ncutler@suse.com>
(cherry picked from commit bc8b2c3823138c68fb4057a335d500f724b02b99)
---

diff --git a/doc/cephfs/fs-nfs-exports.rst b/doc/cephfs/fs-nfs-exports.rst
index cfb46bce0646..fe549e02a035 100644
--- a/doc/cephfs/fs-nfs-exports.rst
+++ b/doc/cephfs/fs-nfs-exports.rst
@@ -19,9 +19,9 @@ Create NFS Ganesha Cluster
 
     $ ceph nfs cluster create <type> <clusterid> [<placement>]
 
-This creates a common recovery pool for all Ganesha daemons, new user based on
-cluster_id, and a common ganesha config rados object. It can also bring up NFS
-Ganesha daemons using the enabled ceph-mgr orchestrator module (see
+This creates a common recovery pool for all NFS Ganesha daemons, new user based on
+cluster_id, and a common NFS Ganesha config rados object. It can also bring up
+NFS Ganesha daemons using the enabled ceph-mgr orchestrator module (see
 :doc:`/mgr/orchestrator`), e.g. cephadm.
 
 <type> signifies the export type, which corresponds to the NFS Ganesha file
@@ -85,8 +85,8 @@ Show NFS Ganesha Cluster Information
 
 This displays ip and port of deployed cluster.
 
-Set Customized Ganesha Configuration
-====================================
+Set Customized NFS Ganesha Configuration
+========================================
 
 .. code:: bash
 
@@ -95,8 +95,8 @@ Set Customized Ganesha Configuration
 With this the nfs cluster will use the specified config and it will have
 precedence over default config blocks.
 
-Reset Ganesha Configuration
-===========================
+Reset NFS Ganesha Configuration
+===============================
 
 .. code:: bash
 
@@ -152,7 +152,7 @@ Get CephFS Export
 
 It displays export block for a cluster based on pseudo root name (binding).
 
-Configuring NFS-Ganesha to export CephFS with vstart
+Configuring NFS Ganesha to export CephFS with vstart
 ====================================================
 
 1) Using cephadm
@@ -161,7 +161,7 @@ Configuring NFS-Ganesha to export CephFS with vstart
 
         $ MDS=1 MON=1 OSD=3 NFS=1 ../src/vstart.sh -n -d --cephadm
 
-    It can deploy only single ganesha daemon with vstart on default ganesha port.
+    It can deploy only single NFS Ganesha daemon with vstart on default NFS Ganesha port.
 
 2) Using test orchestrator
 
@@ -169,15 +169,15 @@ Configuring NFS-Ganesha to export CephFS with vstart
 
        $ MDS=1 MON=1 OSD=3 NFS=1 ../src/vstart.sh -n -d
 
-    It can deploy multiple ganesha daemons on random port. But this requires
-    ganesha packages to be installed.
+    It can deploy multiple NFS Ganesha daemons on random port. But this requires
+    NFS Ganesha packages to be installed.
 
-NFS: It is the number of NFS-Ganesha clusters to be created.
+NFS: It is the number of NFS Ganesha clusters to be created.
 
 Mount
 =====
 
-After the exports are successfully created and Ganesha daemons are no longer in
+After the exports are successfully created and NFS Ganesha daemons are no longer in
 grace period. The exports can be mounted by
 
 .. code:: bash