Fix some typos

sbraz · gmelikov · commit 98c1be6b0ed7 · 2025-07-15T19:56:09.000+03:00
Signed-off-by: Louis Sautier &lt;sautier.louis@gmail.com&gt;
diff --git a/docs/Basic Concepts/RAIDZ.rst b/docs/Basic Concepts/RAIDZ.rst
@@ -36,7 +36,7 @@ Actual used space for a block in RAIDZ is based on several points:
   ``disks count`` minus ``parity number`` parts of data block
 
 - one block of data with size of ``recordsize`` is
-  splitted equally via ``sector size`` parts
+  split equally via ``sector size`` parts
   and written on each stripe on RAIDZ vdev
 - each stripe of data will have a part of block
 
diff --git a/docs/Getting Started/Alpine Linux/Root on ZFS.rst b/docs/Getting Started/Alpine Linux/Root on ZFS.rst
@@ -9,7 +9,7 @@ Alpine Linux Root on ZFS
 
     # For the CI/CD test run of this guide,
     # Enable verbose logging of bash shell and fail immediately when
-    # a commmand fails.
+    # a command fails.
     set -vxeuf
     distro=${1}
 
@@ -245,7 +245,7 @@ System Installation
        # devices as installation target.  However, the alias support for
        # loop device was just introduced in March 2023. See
        # https://github.com/systemd/systemd/pull/26693
-       # For now, we will create the aliases maunally as a workaround
+       # For now, we will create the aliases manually as a workaround
        looppart="1 2 3 4 5"
        for i in ${DISK}; do
          for j in ${looppart}; do
diff --git a/docs/Getting Started/Arch Linux/Root on ZFS.rst b/docs/Getting Started/Arch Linux/Root on ZFS.rst
@@ -6,7 +6,7 @@
 
   # For the CI/CD test run of this guide,
   # Enable verbose logging of bash shell and fail immediately when
-  # a commmand fails.
+  # a command fails.
   set -vxeuf
   distro=${1}
 
@@ -243,7 +243,7 @@ System Installation
        # devices as installation target.  However, the alias support for
        # loop device was just introduced in March 2023. See
        # https://github.com/systemd/systemd/pull/26693
-       # For now, we will create the aliases maunally as a workaround
+       # For now, we will create the aliases manually as a workaround
        looppart="1 2 3 4 5"
        for i in ${DISK}; do
          for j in ${looppart}; do
diff --git a/docs/Getting Started/Debian/Debian Bookworm Root on ZFS.rst b/docs/Getting Started/Debian/Debian Bookworm Root on ZFS.rst
@@ -569,7 +569,7 @@ Step 4: System Configuration
 
    If you're installing on a laptop or a device where wireless is the
    primary network option, the above may not be sufficient as you
-   could lack the appopriate firmware for the device and tools to
+   could lack the appropriate firmware for the device and tools to
    configure the radio. Install some additional packages to cover
    that need::
 
diff --git a/docs/Getting Started/Debian/Debian Trixie Root on ZFS.rst b/docs/Getting Started/Debian/Debian Trixie Root on ZFS.rst
@@ -569,7 +569,7 @@ Step 4: System Configuration
 
    If you're installing on a laptop or a device where wireless is the
    primary network option, the above may not be sufficient as you
-   could lack the appopriate firmware for the device and tools to
+   could lack the appropriate firmware for the device and tools to
    configure the radio. Install some additional packages to cover
    that need::
 
diff --git a/docs/Getting Started/Fedora/Root on ZFS.rst b/docs/Getting Started/Fedora/Root on ZFS.rst
@@ -6,7 +6,7 @@
 
   # For the CI/CD test run of this guide,
   # Enable verbose logging of bash shell and fail immediately when
-  # a commmand fails.
+  # a command fails.
   set -vxeuf
 
   distro=${1}
@@ -252,7 +252,7 @@ System Installation
        # devices as installation target.  However, the alias support for
        # loop device was just introduced in March 2023. See
        # https://github.com/systemd/systemd/pull/26693
-       # For now, we will create the aliases maunally as a workaround
+       # For now, we will create the aliases manually as a workaround
        looppart="1 2 3 4 5"
        for i in ${DISK}; do
          for j in ${looppart}; do
@@ -592,7 +592,7 @@ Bootloader
      # chroot ends here
      ZFS_ROOT_GUIDE_TEST
 
-Post installaion
+Post installation
 ---------------------------
 
 #. Install package groups
diff --git a/docs/Getting Started/NixOS/Root on ZFS.rst b/docs/Getting Started/NixOS/Root on ZFS.rst
@@ -4,7 +4,7 @@
 
   # For the CI/CD test run of this guide,
   # Enable verbose logging of bash shell and fail immediately when
-  # a commmand fails.
+  # a command fails.
   set -vxeuf
 
 .. In this document, there are three types of code-block markups:
@@ -154,7 +154,7 @@ System Installation
        # devices as installation target.  However, the alias support for
        # loop device was just introduced in March 2023. See
        # https://github.com/systemd/systemd/pull/26693
-       # For now, we will create the aliases maunally as a workaround
+       # For now, we will create the aliases manually as a workaround
        looppart="1 2 3 4 5"
        for i in ${DISK}; do
          for j in ${looppart}; do
diff --git a/docs/Getting Started/RHEL-based distro/Root on ZFS.rst b/docs/Getting Started/RHEL-based distro/Root on ZFS.rst
@@ -4,7 +4,7 @@
 
   # For the CI/CD test run of this guide,
   # Enable verbose logging of bash shell and fail immediately when
-  # a commmand fails.
+  # a command fails.
   set -vxeuf
   distro=${1}
 
@@ -242,7 +242,7 @@ System Installation
        # devices as installation target.  However, the alias support for
        # loop device was just introduced in March 2023. See
        # https://github.com/systemd/systemd/pull/26693
-       # For now, we will create the aliases maunally as a workaround
+       # For now, we will create the aliases manually as a workaround
        looppart="1 2 3 4 5"
        for i in ${DISK}; do
          for j in ${looppart}; do
@@ -513,7 +513,7 @@ Bootloader
      # chroot ends here
      ZFS_ROOT_GUIDE_TEST
 
-Post installaion
+Post installation
 ---------------------------
 
 #. Install package groups
diff --git a/docs/Getting Started/openSUSE/openSUSE Leap Root on ZFS.rst b/docs/Getting Started/openSUSE/openSUSE Leap Root on ZFS.rst
@@ -672,7 +672,7 @@ Step 5: System Configuration
    * en_US.utf8
    * POSIX
 
-   Find yout locale from `locale -a` commands output then set it with following command.
+   Find your locale from `locale -a` commands output then set it with following command.
 
    .. code-block:: text
 
@@ -853,7 +853,7 @@ Step 6: Kernel Installation
      mkinitrd
 
    **Note:** After some installations, LUKS partition cannot seen by dracut,
-   this will print “Failure occured during following action:
+   this will print “Failure occurred during following action:
    configuring encrypted DM device X VOLUME_CRYPTSETUP_FAILED“. For fix this
    issue you need to check cryptsetup installation. `See for more information <https://forums.opensuse.org/showthread.php/528938-installation-with-LUKS-cryptsetup-installer-gives-error-code-3034?p=2850404#post2850404>`__
    **Note:** Although we add the zfs config to the system module into `/etc/modules.d`, if it is not seen by dracut, we have to add it to dracut by force.
diff --git a/docs/Getting Started/openSUSE/openSUSE Tumbleweed Root on ZFS.rst b/docs/Getting Started/openSUSE/openSUSE Tumbleweed Root on ZFS.rst
@@ -655,7 +655,7 @@ Step 5: System Configuration
    * en_US.utf8
    * POSIX
 
-   Find yout locale from `locale -a` commands output then set it with following command.
+   Find your locale from `locale -a` commands output then set it with following command.
 
    .. code-block:: text
 
@@ -818,7 +818,7 @@ Step 6: Kernel Installation
      mkinitrd
 
    **Note:** After some installations, LUKS partition cannot seen by dracut,
-   this will print “Failure occured during following action:
+   this will print “Failure occurred during following action:
    configuring encrypted DM device X VOLUME_CRYPTSETUP_FAILED“. For fix this
    issue you need to check cryptsetup installation. `See for more information <https://forums.opensuse.org/showthread.php/528938-installation-with-LUKS-cryptsetup-installer-gives-error-code-3034?p=2850404#post2850404>`__
    **Note:** Although we add the zfs config to the system module into `/etc/modules.d`, if it is not seen by dracut, we have to add it to dracut by force.
diff --git a/docs/Performance and Tuning/Module Parameters.rst b/docs/Performance and Tuning/Module Parameters.rst
@@ -1262,7 +1262,7 @@ l2arc_meta_percent
 
 Percent of ARC size allowed for L2ARC-only headers.
 Since L2ARC buffers are not evicted on memory pressure, too large amount of
-headers on system with irrationaly large L2ARC can render it slow or unusable.
+headers on system with irrationally large L2ARC can render it slow or unusable.
 This parameter limits L2ARC writes and rebuild to achieve it.
 
 +-------------------+-------------------------------------------------+
@@ -1443,7 +1443,7 @@ storage devices.
 | Tags              | `ARC <#arc>`__, `L2ARC <#l2arc>`__              |
 +-------------------+-------------------------------------------------+
 | When to change    | Consider setting for cache devices which        |
-|                   | effeciently handle TRIM commands.               |
+|                   | efficiently handle TRIM commands.               |
 +-------------------+-------------------------------------------------+
 | Data Type         | ulong                                           |
 +-------------------+-------------------------------------------------+
@@ -4716,7 +4716,7 @@ zfs_nopwrite_enabled
 ~~~~~~~~~~~~~~~~~~~~
 
 The NOP-write feature is enabled by default when a
-crytographically-secure checksum algorithm is in use by the dataset.
+cryptographically-secure checksum algorithm is in use by the dataset.
 ``zfs_nopwrite_enabled`` allows the NOP-write feature to be completely
 disabled.
 
@@ -6860,7 +6860,7 @@ zfs_compressed_arc_enabled
 
 When compression is enabled for a dataset, later reads of the data can
 store the blocks in ARC in their on-disk, compressed state. This can
-increse the effective size of the ARC, as counted in blocks, and thus
+increase the effective size of the ARC, as counted in blocks, and thus
 improve the ARC hit ratio.
 
 +----------------------------+----------------------------------------+
diff --git a/docs/msg/ZFS-8000-K4/index.rst b/docs/msg/ZFS-8000-K4/index.rst
@@ -62,7 +62,7 @@ which pool is in error:
      pool: test
     state: FAULTED
    status: One or more of the intent logs could not be read.
-           Waiting for adminstrator intervention to fix the faulted pool.
+           Waiting for administrator intervention to fix the faulted pool.
    action: Either restore the affected device(s) and run 'zpool online',
            or ignore the intent log records by running 'zpool clear'.
     scrub: none requested
