summaryrefslogtreecommitdiff
path: root/rsync.1.md
diff options
context:
space:
mode:
authorSamuel Henrique <samueloph@debian.org>2022-08-18 05:50:43 +0100
committerGitHub <noreply@github.com>2022-08-17 21:50:43 -0700
commitb94bba40361acf1b7b9da41b02aa3d6b6e47943d (patch)
treeeb21d07b8ab13410fa712623b47679b49eee4706 /rsync.1.md
parenta182507bef2d0cd92052b3c5ebaf1d98278e0dad (diff)
downloadrsync-b94bba40361acf1b7b9da41b02aa3d6b6e47943d.tar.gz
Fix typos on manpage (#358)
Diffstat (limited to 'rsync.1.md')
-rw-r--r--rsync.1.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/rsync.1.md b/rsync.1.md
index f29495f2..1a3e8607 100644
--- a/rsync.1.md
+++ b/rsync.1.md
@@ -1904,13 +1904,13 @@ expand it.
By default, an exclude or include has both a server-side effect (to "hide"
and "show" files when building the server's file list) and a receiver-side
- effect (to "protect" and "risk" files when deletions are occuring). Any
+ effect (to "protect" and "risk" files when deletions are occurring). Any
rule that has no modifier to specify what sides it is executed on will be
instead treated as if it were a server-side rule only, avoiding any
"protect" effects of the rules.
A rule can still apply to both sides even with this option specified if the
- rule is given both the sender & receiver modifer letters (e.g., `-f'-sr
+ rule is given both the sender & receiver modifier letters (e.g., `-f'-sr
foo'`). Receiver-side protect/risk rules can also be explicitly specified
to limit the deletions. This saves you from having to edit a bunch of
`-f'- foo'` rules into `-f'-s foo'` (aka `-f'H foo'`) rules (not to mention