Fix misuse of the phrase zpool in ZFS chapter handbook

PR:             257405
Reviewed by:    grahamperrin@, pauamma@

1 files changed, 2 insertions, 2 deletions

diff --git a/documentation/content/en/books/handbook/zfs/_index.adoc b/documentation/content/en/books/handbook/zfs/_index.adoc
index 9720122a84..397f592208 100644
--- a/documentation/content/en/books/handbook/zfs/_index.adoc
+++ b/documentation/content/en/books/handbook/zfs/_index.adoc
@@ -489,7 +489,7 @@ The <<zfs-zfs,`zfs`>> utility allows creating, destroying, and managing datasets
 [[zfs-zpool-create]]
 === Creating and Destroying Storage Pools
 
-Creating a ZFS storage pool (_zpool_) requires permanent decisions, as the pool structure cannot change after creation.
+Creating a ZFS storage pool requires permanent decisions, as the pool structure cannot change after creation.
 The most important decision is which types of vdevs to group the physical disks into. 
 See the list of <<zfs-term-vdev,vdev types>> for details about the possible options.
 After creating the pool, most vdev types do not allow adding disks to the vdev.
@@ -581,7 +581,7 @@ This can cause undefined behavior in applications which had open files on those
 [[zfs-zpool-attach]]
 === Adding and Removing Devices
 
-Two ways exist for adding disks to a zpool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
+Two ways exist for adding disks to a pool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
 Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation.
 
 A pool created with a single disk lacks redundancy.