---
I proofread NEWS and here's what I found.
NEWS | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/NEWS b/NEWS
index d1f62be..2edb43f 100644
--- a/NEWS
+++ b/NEWS
@@ -116,11 +116,11 @@ Changes since 2.6.9:
options are set correctly for the current batch file: --iconv, --acls,
--xattrs, --inplace, --append, and --append-verify.
- - Using --only-write-batch to a daemon receiver now work properly (older
+ - Using --only-write-batch to a daemon receiver now works properly (older
versions would update some files while writing the batch).
- Avoid outputting a "file has vanished" message when the file is
a broken
- symlink and --copy-unsafe-links or --copy-dirlinks are used (the code
+ symlink and --copy-unsafe-links or --copy-dirlinks is used (the code
already handled this for --copy-links).
- Fixed the combination of --only-write-batch and --dry-run.
@@ -160,7 +160,7 @@ Changes since 2.6.9:
ACL-patched versions of rsync, apply the acls.diff file from the patches
dir.
- - Added the --xattrs (-X) option to preserver extended attributes. This is
+ - Added the --xattrs (-X) option to preserve extended attributes. This is
an improved version of the prior patch that was available, and it even
supports OS X xattrs (which includes their resource fork data). If you
need to have backward compatibility with old, xattr-patched versions of
@@ -315,7 +315,7 @@ Changes since 2.6.9:
directory named testtmp (which is created, if missing). This allows
someone to symlink the testtmp directory to another filesystem (which is
useful if the build dir's filesystem does not support ACLs and
xattrs,
- but another file system does).
+ but another filesystem does).
- Rsync now has a way of handling protocol-version changes during the
development of a new protocol version. This causes any out-of-sync
--
1.5.4.rc3.15.g4bbc
