From 223848a08f58fc20ee4afc008fabbec2d448be68 Mon Sep 17 00:00:00 2001
From: =?utf8?q?=E5=8F=B6=E6=B5=B7=E4=B8=B0?= <769358362@qq.com>
Date: Fri, 15 Dec 2023 17:05:38 +0800
Subject: [PATCH] doc/cephfs/client-auth.rst: correct ``fs authorize cephfs1
 /dir1 client.x rw``

---
 doc/cephfs/client-auth.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/cephfs/client-auth.rst b/doc/cephfs/client-auth.rst
index 5a642e4f8ae..946211bf682 100644
--- a/doc/cephfs/client-auth.rst
+++ b/doc/cephfs/client-auth.rst
@@ -316,8 +316,8 @@ Changing rw permissions in caps
 It's not possible to modify caps by running ``fs authorize`` except for the
 case when read/write permissions have to be changed. This so because the
 ``fs authorize`` becomes ambiguous. For example, user runs ``fs authorize
-cephfs1 /dir1 client.x rw`` to create a client and then runs ``fs authorize
-cephfs1 /dir2 client.x rw`` (notice ``/dir1`` is changed to ``/dir2``).
+cephfs1 client.x /dir1 rw`` to create a client and then runs ``fs authorize
+cephfs1 client.x /dir2 rw`` (notice ``/dir1`` is changed to ``/dir2``).
 Running second command can be interpreted as changing ``/dir1`` to ``/dir2``
 in current cap or can also be interpreted as authorizing the client with a
 new cap for path ``/dir2``. As seen in previous sections, second
-- 
2.47.3