From 98514aa47cfa7ca1f068d7ae3369a916e554f788 Mon Sep 17 00:00:00 2001
From: Tommaso Comparin <3862206+tcompa@users.noreply.github.com>
Date: Thu, 2 Nov 2023 11:26:13 +0100
Subject: [PATCH] Rephrase sentence about Z size of FOV/well ROIs

---
 docs/tables.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/docs/tables.md b/docs/tables.md
index 6b9f8ab73..b2e4d6f35 100644
--- a/docs/tables.md
+++ b/docs/tables.md
@@ -258,10 +258,10 @@ tasks) always include two specific ROI tables:
 * The table named `well_ROI_table`, which covers the NGFF image corresponding to the whole well[^1];
 * The table named `FOV_ROI_table`, which lists all original fields of view (FOVs).
 
-Each one of these two tables includes ROIs that are only defined in the XY
-plane, and span the whole image size along the Z axis. Note that this differs,
-e.g., from ROIs which are the bounding boxes of three-dimensional segmented
-objects, and which may cover only a part of the image Z size.
+Each one of these two tables includes ROIs that span the whole image size along
+the Z axis. Note that this differs, e.g., from ROIs which are the bounding
+boxes of three-dimensional segmented objects, and which may cover only a part
+of the image Z size.
 
 #### OME-Zarr import
 
@@ -277,6 +277,10 @@ ROI tables to the NGFF images:
   case the image is a tiled well[^1]), or it may simply be useful for applying
   downstream processing to smaller arrays and avoid large memory requirements.
 
+As for the case of `well_ROI_table` and `FOV_ROI_table` described
+[above](#ome-zarr-creation), also these two tables include ROIs spanning the
+whole image extension along the Z axis.
+
 #### OME-Zarr processing
 
 ROI tables are also used and updated during image processing, e.g as in: