diff --git a/documentation/content/en/books/handbook/zfs/_index.adoc b/documentation/content/en/books/handbook/zfs/_index.adoc
--- a/documentation/content/en/books/handbook/zfs/_index.adoc
+++ b/documentation/content/en/books/handbook/zfs/_index.adoc
@@ -4,7 +4,7 @@
 prev: books/handbook/geom
 next: books/handbook/filesystems
 description: ZFS is an advanced file system designed to solve major problems found in previous storage subsystem software
-tags: ["ZFS", "filesystem", "administration", "zpool", "features", "terminology", "RAID-Z"]
+tags: ["ZFS", "filesystem", "administration", "pool", "zpool", "features", "terminology", "RAID-Z"]
 showBookMenu: true
 weight: 25
 path: "/books/handbook/"
@@ -253,7 +253,7 @@
 Refer to man:zpool[8] for more details.
 ====
 
-The previous example created the `storage` zpool.
+The previous example created the `storage` pool.
 This example makes a new file system called `home` in that pool:
 
 [source,shell]
@@ -480,21 +480,27 @@
 Refer to man:zfs[8] and man:zpool[8] for other ZFS options.
 
 [[zfs-zpool]]
-== `zpool` Administration
+== Pool Administration
 
 ZFS administration uses two main utilities.
 The `zpool` utility controls the operation of the pool and allows adding, removing, replacing, and managing disks.
 The <<zfs-zfs,`zfs`>> utility allows creating, destroying, and managing datasets, both <<zfs-term-filesystem,file systems>> and <<zfs-term-volume,volumes>>.
 
 [[zfs-zpool-create]]
-=== Creating and Destroying Storage Pools
+=== Creating and Destroying Pools
+
+Creating a pool requires forethought.
 
-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.
-The exceptions are mirrors, which allow adding new disks to the vdev, and stripes, which upgrade to mirrors by attaching a new disk to the vdev.
-Although adding new vdevs expands a pool, the pool layout cannot change after pool creation.
+See the list of <<zfs-term-vdev,vdev types>> for details.
+
+After creating a pool, most types of vdev do not allow addition of a disk.
+Exceptions are: 
+
+* mirrors, which do allow addition of a disk to the vdev
+* stripes, which upgrade to mirrors by attaching a new disk to the vdev.
+
+Although adding a new vdev expands a pool, the pool layout cannot change.
 Instead, back up the data, destroy the pool, and recreate it.
 
 Create a simple mirror pool:
@@ -787,7 +793,7 @@
 The pool never enters a <<zfs-term-degraded,degraded>> state, reducing the risk of data loss.
 Running `zpool replace` copies the data from the old disk to the new one.
 After the operation completes, ZFS disconnects the old disk from the vdev.
-If the new disk is larger than the old disk, it may be possible to grow the zpool, using the new space.
+If the new disk is larger than the old disk, it may be possible to grow the pool, using the new space.
 See <<zfs-zpool-online,Growing a Pool>>.
 
 Replace a functioning device in the pool:
@@ -1211,7 +1217,7 @@
 ....
 
 [[zfs-zpool-upgrade]]
-=== Upgrading a Storage Pool
+=== Upgrading a Pool
 
 After upgrading FreeBSD, or if importing a pool from a system using an older version, manually upgrade the pool to the latest ZFS version to support newer features.
 Consider whether the pool may ever need importing on an older system before upgrading.
@@ -1453,7 +1459,7 @@
 This helps confirm that the operation will do what the user intends.
 
 [[zfs-zfs]]
-== `zfs` Administration
+== Dataset Administration
 
 The `zfs` utility can create, destroy, and manage all existing ZFS datasets within a pool.
 To manage the pool itself, use <<zfs-zpool,`zpool`>>.