From 77c969d079eefeb092a948973377eb315b6f99a4 Mon Sep 17 00:00:00 2001
From: Alessandra Trapani <55453048+alessandratrapani@users.noreply.github.com>
Date: Wed, 27 Sep 2023 16:25:41 +0200
Subject: [PATCH] Update docs/best_practices/time_series.rst

Co-authored-by: Cody Baker <51133164+CodyCBakerPhD@users.noreply.github.com>
---
 docs/best_practices/time_series.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/best_practices/time_series.rst b/docs/best_practices/time_series.rst
index 54c60ea94..e40355145 100644
--- a/docs/best_practices/time_series.rst
+++ b/docs/best_practices/time_series.rst
@@ -165,7 +165,6 @@ Check function: :py::meth:`~nwbinspector.checks.time_series.check_resolution`
 Zero Rate
 ~~~~~~~~~
 
-If ``data`` field of :ref:`nwb-schema:sec-TimeSeries` has more than one frame, thus first dimension that represent time is
-greater than one, ``rate`` should not be 0.0.
+If the ``data`` field of :ref:`nwb-schema:sec-TimeSeries` has more than one frame, and according to :ref:`best_practice_data_orientation` this axis ought to be time, then the ``rate`` field should not be ``0.0``.
 
 Check function: :py::meth:`~nwbinspector.checks.time_series.check_rate_is_not_zero`