From 5ec42512c55e7a1c998be7be5090c2a41708ae27 Mon Sep 17 00:00:00 2001
From: Vikram Vaswani <2571660+vvaswani@users.noreply.github.com>
Date: Sun, 8 Feb 2026 01:14:08 +0530
Subject: [PATCH] fix: typo

Signed-off-by: Vikram Vaswani <2571660+vvaswani@users.noreply.github.com>
---
 rsync.1.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/rsync.1.md b/rsync.1.md
index 2b4b75087..8f78d1246 100644
--- a/rsync.1.md
+++ b/rsync.1.md
@@ -2820,12 +2820,12 @@ expand it.
 
 0.  `--compress-threads=NUM`, `--zt=NUM`
 
-    Set the number of threads to spawn when compressing data. Setting this 
-    option to 1 or more will instruct the compression library to spawn 1 or 
-    more threads for compression. Ideally, increasing the number of threads 
+    Set the number of threads to spawn when compressing data. Setting this
+    option to 1 or more will instruct the compression library to spawn 1 or
+    more threads for compression. Ideally, increasing the number of threads
     will increase transfer speed if the transfer is CPU bound on the sender.
-    
-    This option does not affect decompression. 
+
+    This option does not affect decompression.
 
     Compression algorithms that allow threading:
 
@@ -3945,7 +3945,7 @@ different ways.
 We will first cover the basics of how include & exclude rules affect what files
 are transferred, ignoring any deletion side-effects.  Filter rules mainly
 affect the contents of directories that rsync is "recursing" into, but they can
-also affect a top-level item in the transfer that was specified as a argument.
+also affect a top-level item in the transfer that was specified as an argument.
 
 The default for any unmatched file/dir is for it to be included in the
 transfer, which puts the file/dir into the sender's file list.  The use of an