doc: drop manual remote snapshotting

Drop the word 'manually' from the doc, as this could also happen
via snap-schedule.

Signed-off-by: Jos Collin <jcollin@redhat.com>

diff --git a/doc/cephfs/cephfs-mirroring.rst b/doc/cephfs/cephfs-mirroring.rst
index 147100c9e31df1508c681b6cddcc29668963b5be..04656bd4b969e4bdb903fcdca23a28b95687938f 100644 (file)
--- a/doc/cephfs/cephfs-mirroring.rst
+++ b/doc/cephfs/cephfs-mirroring.rst
@@ -439,7 +439,7 @@ This allows a user to add a non-existent directory for synchronization. The mirr
 will mark such a directory as failed and retry (less frequently). When the directory is
 created, the mirror daemon will clear the failed state upon successful synchronization.
 
-Adding a new snapshot or a new directory manually in the ``.snap`` directory of the
+Adding a new snapshot or a new directory in the ``.snap`` directory of the
 remote filesystem will result in failed status of the corresponding configured directory.
 In the remote filesystem::
 
@@ -473,6 +473,9 @@ In the remote filesystem::
 When the snapshot or the directory is removed from the remote filesystem, the mirror daemon will
 clear the failed state upon successful synchronization of the pending snapshots, if any.
 
+.. note:: Setting snap-schedule on the remote flle system for directories that are being mirrored will
+          cause the mirror daemon to report errors like ``invalid metadata``.
+
 .. note:: Treat the remote filesystem as read-only. Nothing is inherently enforced by CephFS.
           But with the right MDS caps, users would not be able to snapshot directories in the
           remote file system.