"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
Go azure-blobazure-blob-storageazure-filesbackblaze-b2cloud-storagedropboxencryptionftpfuse-filesystemgogolanggoogle-cloud-storagegoogle-driveonedriveopenstack-swiftrclones3sftpsyncwebdav
docs: fix broken --check-filename self-link in bisync docs
shauryac3ba184611c3
diff --git a/docs/content/bisync.md b/docs/content/bisync.mdindex 4e18c2c2d..0e6430321 100644--- a/docs/content/bisync.md+++ b/docs/content/bisync.md@@ -323,7 +323,7 @@ Time stamps and file contents for `RCLONE_TEST` files are not important, justthe names and locations. If you have symbolic links in your sync tree it isrecommended to place `RCLONE_TEST` files in the linked-to directory tree toprotect against bisync assuming a bunch of deleted files if the linked-to tree-should not be accessible. See also the [--check-filename](--check-filename) flag.+should not be accessible. See also the [--check-filename](#check-filename) flag.### --check-filename