From b96b2b542a6dc76f1c1a0c9948fe9a88cadeef5c Mon Sep 17 00:00:00 2001
From: Han Lu <11597940+ErbB4@users.noreply.github.com>
Date: Thu, 1 Aug 2024 10:45:33 +0200
Subject: [PATCH] fixed typo and grammar (#2360)

<!-- Please make sure your PR follows our [contribution
guidelines](https://github.com/arbor-sim/arbor/tree/master/doc/contrib)
and agree to the terms outlined in the [PR
procedure](https://github.com/arbor-sim/arbor/tree/master/doc/contrib/pr.rst).
-->
---
 doc/cpp/probe_sample.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/cpp/probe_sample.rst b/doc/cpp/probe_sample.rst
index 6e7a21b9..912ab99b 100644
--- a/doc/cpp/probe_sample.rst
+++ b/doc/cpp/probe_sample.rst
@@ -52,7 +52,7 @@ disabled.
 
 Cable cell probes that contingently do not correspond to a valid measurable
 quantity are ignored: samplers attached to them will receive no values.
-Mechanism state queries however will throw a ``cable_cell_error`` exception at
+Mechanism state queries, however will throw a ``cable_cell_error`` exception at
 simulation initialization if the requested state variable does not exist on the
 mechanism.
 
@@ -82,7 +82,7 @@ Queries cell membrane potential at each site in ``locations``.
 
     struct cable_probe_membrane_voltage_cell {};
 
-Queries cell membrane potential across whole cell.
+Queries cell membrane potential across the whole cell.
 
 *  Sample value: ``cable_sample_range``. Each value is the
    average membrane potential in millivolts across an unbranched
@@ -173,7 +173,7 @@ Membrane current _excluding_ capacitive currents and stimuli across components o
 
     struct cable_probe_total_current_cell {};
 
-Total membrance current excluding current stimuli across components of the cell.
+Total membrane current excluding current stimuli across components of the cell.
 
 *  Sample value: ``cable_sample_range``. Each value is the current in
    nanoamperes across an unbranched component of the cell, as determined
@@ -609,7 +609,7 @@ the same sequence of time points, that is, it must exhibit repeatable
 and deterministic behaviour.
 
 The ``schedule`` object itself uses type-erasure to wrap any schedule
-implementation class, which can be any copy--constructable class that
+implementation class, which can be any copy--constructible class that
 provides the methods ``reset()`` and ``events(t0, t1)`` above. Three
 schedule implementations are provided by the engine:
 
-- 
GitLab