jacobpascual/openzfs-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add "the" to a phrase

Browse Source 
I noticed this while looking at #317.

Signed-off-by: Richard Laager <rlaager@wiktel.com>
This commit is contained in:
Richard Laager
2022-06-09 12:18:48 -05:00
parent 36c1f2f5cd
commit 9e7a1e8c54
6 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst
View File

@@ -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``.

4
docs/Getting Started/Debian/Debian Buster Root on ZFS.rst
View File

@@ -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``.

4
docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst
View File

@@ -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``.

4
docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst
View File

@@ -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``.

4
docs/Getting Started/openSUSE/openSUSE Leap Root on ZFS.rst
View File

@@ -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``.

4
docs/Getting Started/openSUSE/openSUSE Tumbleweed Root on ZFS.rst
View File

@@ -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``.