manual fixes

sometimes the AI got it wrong.
also some other fixes.

Author: ThomasWaldmann

README.rst

@@ -90,7 +90,7 @@ Main features
     * FreeBSD
     * OpenBSD and NetBSD (no xattrs/ACLs support or binaries yet)
     * Cygwin (experimental, no binaries yet)
-    * Windows Subsystem for Linux (WSL) on Windows 10 (experimental)
+    * Windows Subsystem for Linux (WSL) on Windows 10/11 (experimental)
 
 **Free and Open Source Software**
   * security and functionality can be audited independently

docs/deployment/automated-local.rst

@@ -104,7 +104,7 @@ modify it to suit your needs (e.g. more backup sets, dumping databases etc.).
     # Create backups
     #
 
-    # Options for Borg create
+    # Options for borg create
     BORG_OPTS="--stats --one-file-system --compression lz4 --checkpoint-interval 86400"
 
     # Set BORG_PASSPHRASE or BORG_PASSCOMMAND somewhere around here, using export,

docs/deployment/pull-backup.rst

@@ -54,7 +54,7 @@ completely in every aspect from such a backup.
 
 .. warning::
 
-    The chroot method was chosen to get the right user and group name-ID
+    The chroot method was chosen to get the right user and group name-id
     mappings, assuming they only come from files (/etc/passwd and group).
     This assumption might be wrong, e.g. if users/groups also come from
     ldap or other providers.

docs/quickstart.rst

@@ -49,7 +49,7 @@ by deleting/pruning archives. This mechanism is not bullet-proof in some
 circumstances [1]_.
 
 If you *really* run out of disk space, it can be hard or impossible to free space,
-because Borg needs free space to operate—even to delete backup
+because Borg needs free space to operate — even to delete backup
 archives.
 
 You can use some monitoring process or just include the free space information

docs/usage/notes.rst

@@ -320,7 +320,7 @@ repository. Make sure that backup client machines only get to access the reposit
 ``borg serve``.
 
 Ensure that no remote access is possible if the repository is temporarily set to normal mode
-for example, regular pruning.
+(for example, for regular pruning).
 
 Further protections can be implemented, but are outside of Borg's scope. For example,
 file system snapshots or wrapping ``borg serve`` to set special permissions or ACLs on

scripts/borg.exe.spec

@@ -51,7 +51,7 @@ exe = EXE(pyz,
           console=True)
 
 # Build a directory-based binary in addition to a packed
-# single-file. This allows one to easily look at all included
+# single file. This allows one to easily look at all included
 # files (e.g., without having to strace or halt the built binary
 # and introspect /tmp). Also avoids unpacking all libraries when
 # running the app, which is better for app signing on various operating systems.

src/borg/archiver.py

@@ -4507,13 +4507,13 @@ def define_borg_mount(parser):
         reduce problems with manual input. The ``--qr-html`` option creates a printable
         HTML template with a QR code and a copy of the ``--paper``-formatted key.
 
-        For repositories using key file encryption the key is saved locally
+        For repositories using keyfile encryption the key is saved locally
         on the system that is capable of doing backups. To guard against loss
         of this key, the key needs to be backed up independently of the main
         data backup.
 
         For repositories using repokey encryption, the key is saved in the
-        repository's config file. A backup is thus not strictly needed,
+        repository in the config file. A backup is thus not strictly needed,
         but it guards against the repository becoming inaccessible if the file
         is damaged for some reason.
 
@@ -4551,7 +4551,7 @@ def define_borg_mount(parser):
         process in which each line is checked for plausibility before
         proceeding to the next line. For this format, PATH must not be provided.
 
-        For repositories using key file encryption, the key file which ``borg key
+        For repositories using keyfile encryption, the key file which ``borg key
         import`` writes to depends on several factors. If the ``BORG_KEY_FILE``
         environment variable is set and non-empty, ``borg key import`` creates
         or overwrites the file named by ``$BORG_KEY_FILE``. Otherwise, ``borg
@@ -5073,7 +5073,7 @@ def define_borg_mount(parser):
         the first backup after the conversion takes longer than expected
         due to the cache re-sync.
 
-        The upgrade should be able to resume if interrupted, although it
+        Upgrade should be able to resume if interrupted, although it
         will still iterate over all segments. If you want to start
         from scratch, use ``borg delete`` over the copied repository to
         make sure the cache files are also removed::

src/borg/chunker.pyx

@@ -58,7 +58,7 @@ def dread(offset, size, fd=None, fh=-1):
         data = os.read(fh, size)
         if hasattr(os, 'posix_fadvise'):
             # UNIX-only and, in case of block sizes that are not a multiple of the
-            # system's page size, it is better used with a bug-fixed Linux kernel >= 4.6.0,
+            # system's page size, it is better used with a bug-fixed Linux kernel > 4.6.0,
             # see comment/workaround in _chunker.c and borgbackup issue #907.
             os.posix_fadvise(fh, offset, len(data), os.POSIX_FADV_DONTNEED)
         return data

src/borg/crypto/file_integrity.py

@@ -153,7 +153,7 @@ def hash_filename(self, filename=None):
         # Hash the name of the file, but only the basename, i.e. not the path.
         # In Borg the name itself encodes the context (e.g., index.N, cache, files),
         # while the path doesn't matter, and moving e.g. a repository or cache directory is supported.
-        # Changing the name, however, implies a change of context that is not permissible.
+        # Changing the name, however, imbues a change of context that is not permissible.
         # While Borg does not use anything except ASCII in these file names, it's important to use
         # the same encoding everywhere for portability. Using os.fsencode() would be wrong.
         filename = os.path.basename(filename or self.path)

src/borg/crypto/key.py

@@ -47,7 +47,7 @@ class PasscommandFailure(Error):
 
 
 class PassphraseWrong(Error):
-    """Passphrase supplied via BORG_PASSPHRASE, by BORG_PASSCOMMAND, or via BORG_PASSPHRASE_FD is incorrect."""
+    """Passphrase supplied in BORG_PASSPHRASE, by BORG_PASSCOMMAND, or via BORG_PASSPHRASE_FD is incorrect."""
     exit_mcode = 52