From bb1a22d1e6464eb801c64c20fc26fa6d1a04169c Mon Sep 17 00:00:00 2001 From: Martin Michlmayr Date: Mon, 30 Apr 2018 18:32:10 +0200 Subject: [PATCH] Fix typos in section on rclone --- doc/030_preparing_a_new_repo.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/030_preparing_a_new_repo.rst b/doc/030_preparing_a_new_repo.rst index 2133ec7c2..9192fac03 100644 --- a/doc/030_preparing_a_new_repo.rst +++ b/doc/030_preparing_a_new_repo.rst @@ -439,7 +439,7 @@ listing similar to the following: 448 bar/baz/keys/4bf9c78049de689d73a56ed0546f83b8416795295cda12ec7fb9465af3900b44 Rclone can be `configured with environment variables`_, so for instance -configuring a bandwidth limit for rclone cat be achieve by setting the +configuring a bandwidth limit for rclone can be achieved by setting the ``RCLONE_BWLIMIT`` environment variable: .. code-block:: console @@ -453,7 +453,7 @@ The rclone backend has two additional options: * ``-o rclone.program`` specifies the path to rclone, the default value is just ``rclone`` * ``-o rclone.args`` allows setting the arguments passed to rclone, by default this is ``serve restic --stdio --b2-hard-delete --drive-use-trash=false`` -The reason why the two last parameters (``--b2-hard-delete`` and +The reason for the two last parameters (``--b2-hard-delete`` and ``--drive-use-trash=false``) can be found in the corresponding GitHub `issue #1657`_. In order to start rclone, restic will build a list of arguments by joining the