From 30fdbaeb1313b1daa57e89bdb1f86f2ebf0ed20e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?R=C3=A9mi=20Delaporte-Mathurin?=
 <40028739+RemDelaporteMathurin@users.noreply.github.com>
Date: Wed, 16 Feb 2022 12:42:43 -0500
Subject: [PATCH] Tiny typo

---
 docs/source/usersguide/troubleshoot.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/source/usersguide/troubleshoot.rst b/docs/source/usersguide/troubleshoot.rst
index dd1c86a13..06e5c5704 100644
--- a/docs/source/usersguide/troubleshoot.rst
+++ b/docs/source/usersguide/troubleshoot.rst
@@ -80,7 +80,7 @@ high enough to produce any pixels in the overlapping area.
 To reliably validate a geometry input, it is best to run the problem in
 geometry debugging mode with the ``-g``, ``-geometry-debug``, or
 ``--geometry-debug`` command-line options.  This will enable checks for
-overlapping cells at every move of esch simulated particle.  Depending on the
+overlapping cells at every move of each simulated particle.  Depending on the
 complexity of the geometry input file, this could add considerable overhead to
 the run (these runs can still be done in parallel).  As a result, for this run
 mode the user will probably want to run fewer particles than a normal