diff --git a/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst b/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst index 2f2b139..3aca727 100644 --- a/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst +++ b/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst @@ -268,7 +268,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - The pool name is arbitrary. If changed, the new name must be used consistently. The ``bpool`` convention originated in this HOWTO. @@ -407,7 +407,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - When using LUKS with mirror or raidz topologies, use ``/dev/mapper/luks1``, ``/dev/mapper/luks2``, etc., which you will have to create using ``cryptsetup``. diff --git a/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst b/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst index a6afd90..b26c87a 100644 --- a/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst +++ b/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst @@ -283,7 +283,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - The pool name is arbitrary. If changed, the new name must be used consistently. The ``bpool`` convention originated in this HOWTO. @@ -418,7 +418,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - When using LUKS with mirror or raidz topologies, use ``/dev/mapper/luks1``, ``/dev/mapper/luks2``, etc., which you will have to create using ``cryptsetup``. diff --git a/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst b/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst index 5d0cf3c..2a6787b 100644 --- a/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst +++ b/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst @@ -437,7 +437,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - The boot pool name is no longer arbitrary. It _must_ be ``bpool``. If you really want to rename it, edit ``/etc/grub.d/10_linux_zfs`` later, after GRUB is installed (and run ``update-grub``). @@ -579,7 +579,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - When using LUKS with mirror or raidz topologies, use ``/dev/mapper/luks1``, ``/dev/mapper/luks2``, etc., which you will have to create using ``cryptsetup``. diff --git a/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst b/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst index 9aa8716..2d81075 100644 --- a/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst +++ b/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst @@ -311,7 +311,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - The boot pool name is no longer arbitrary. It _must_ be ``bpool``. If you really want to rename it, edit ``/etc/grub.d/10_linux_zfs`` later, after GRUB is installed (and run ``update-grub``). @@ -451,7 +451,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - When using LUKS with mirror or raidz topologies, use ``/dev/mapper/luks1``, ``/dev/mapper/luks2``, etc., which you will have to create using ``cryptsetup``. diff --git a/docs/Getting Started/openSUSE/openSUSE Leap Root on ZFS.rst b/docs/Getting Started/openSUSE/openSUSE Leap Root on ZFS.rst index 4008792..cefcf62 100644 --- a/docs/Getting Started/openSUSE/openSUSE Leap Root on ZFS.rst +++ b/docs/Getting Started/openSUSE/openSUSE Leap Root on ZFS.rst @@ -262,7 +262,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - The pool name is arbitrary. If changed, the new name must be used consistently. The ``bpool`` convention originated in this HOWTO. @@ -399,7 +399,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - When using LUKS with mirror or raidz topologies, use ``/dev/mapper/luks1``, ``/dev/mapper/luks2``, etc., which you will have to create using ``cryptsetup``. diff --git a/docs/Getting Started/openSUSE/openSUSE Tumbleweed Root on ZFS.rst b/docs/Getting Started/openSUSE/openSUSE Tumbleweed Root on ZFS.rst index 3e7dd18..8a005dd 100644 --- a/docs/Getting Started/openSUSE/openSUSE Tumbleweed Root on ZFS.rst +++ b/docs/Getting Started/openSUSE/openSUSE Tumbleweed Root on ZFS.rst @@ -254,7 +254,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - The pool name is arbitrary. If changed, the new name must be used consistently. The ``bpool`` convention originated in this HOWTO. @@ -391,7 +391,7 @@ Step 2: Disk Formatting - For raidz topologies, replace ``mirror`` in the above command with ``raidz``, ``raidz2``, or ``raidz3`` and list the partitions from - additional disks. + the additional disks. - When using LUKS with mirror or raidz topologies, use ``/dev/mapper/luks1``, ``/dev/mapper/luks2``, etc., which you will have to create using ``cryptsetup``.