[SCM] The rsync repository. - branch master updated

[Rsync CVS commit messages]

The branch, master has been updated
       via  86f41650 A couple spelling tweaks; tweak order.
      from  9a06b2ed Preparing for release of 3.3.0pre1 [buildall]

https://git.samba.org/?p=rsync.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit 86f41650fb048fa5857a137f70074d77ebe06e36
Author: Wayne Davison <wayne at opencoder.net>
Date:   Sun Apr 30 17:28:50 2023 -0700

    A couple spelling tweaks; tweak order.

-----------------------------------------------------------------------

Summary of changes:
 NEWS.md    | 8 ++++----
 rsync.1.md | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)


Changeset truncated at 500 lines:

diff --git a/NEWS.md b/NEWS.md
index 1d3a158b..67869ccc 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -10,12 +10,12 @@
 - Fixed an buffer overflow in the checksum2 code if SHA1 is being used for
   the checksum2 algorithm.
 
-- Fixed a string-comparison issue in the internal file-list code that affected
-  tr_TR.utf-8.
-
 - Add a backtick to the list of characters that the filename quoting needs to
   escape using backslashes.
 
+- Fixed a string-comparison issue in the internal file-list code that affected
+  tr_TR.utf-8.
+
 - Make sure that a local transfer marks the sender side as trusted.
 
 - Change the argv handling to work with a newer popt library -- one that likes
@@ -100,7 +100,7 @@
 
 - The `--fuzzy` option was optimized a bit to try to cut down on the amount of
   computations when considering a big pool of files. The simple heuristic from
-  Kenneth Finnegan resuled in about a 2x speedup.
+  Kenneth Finnegan resulted in about a 2x speedup.
 
 - If rsync is forced to use protocol 29 or before (perhaps due to talking to an
   rsync before 3.0.0), the modify time of a file is limited to 4-bytes.  Rsync
diff --git a/rsync.1.md b/rsync.1.md
index 16dbf20c..894b3663 100644
--- a/rsync.1.md
+++ b/rsync.1.md
@@ -245,7 +245,7 @@ to be copied to different destination directories using more than one copy.
 
 While a copy of a case-ignoring filesystem to a case-ignoring filesystem can
 work out fairly well, if no `--delete-during` or `--delete-before` option is
-active, rsync can potentially update an existing file on the receiveing side
+active, rsync can potentially update an existing file on the receiving side
 without noticing that the upper-/lower-case of the filename should be changed
 to match the sender.
 


-- 
The rsync repository.