Update acq board plugin page for v3

source/User-Manual/Plugins/Acquisition-Board.rst

@@ -35,7 +35,9 @@ Plugin configuration
 Headstages
 ############
 
-On the left-hand side of the module, there are slots for each of 8 possible headstages (A1, A2, B1, B2, etc.). Each row corresponds to one 12-channel Omnetics connector on the input board (from left to right, there are A, B, C, and D), and each column corresponds to one headstage on that input. Up to two headstages can be connected to each input using a dual headstage adapter. The module will automatically detect headstages that are connected, as well as whether they contain a 64- or 32-channel Intan chip. However, if you add or remove headstages after the module has been loaded, you need to press the "RESCAN" button. 
+On the left-hand side of the module, there are four rows with 2 slots each. Each row represents a headstage port on the acquisition board (denoted as A, B, C, & D left-to-right on the hardware). Each port can accommodate either two headstages *without* an IMU or one headstage *with* an IMU. This corresponds to the following plugin behavior: when a headstage without an IMU is detected, it will occupy one slot in a row. When a headstage with an IMU is detected, it will occupy both slots in a row. When this processor is added to the signal chain, it automatically detects  connected headstages, as well as whether they contain a 64- or 32-channel Intan chip. If you add or remove headstages after the module has been loaded, you must press the "RESCAN" button. 
+
+..  note:: Plugging two headstage into one port requires a `dual headstage adapter <https://open-ephys.github.io/acq-board-docs/Hardware-Guide/Cables.html#dual-headstage-adapter>`__
 
 Using 16-channel headstages
 ----------------------------
@@ -112,6 +114,21 @@ To open the impedance measurement interface, click the "window" or "tab" buttons
 .. image:: ../../_static/images/plugins/acquisitionboard/acquisitionboard-02.png
   :alt: Annotated impedance measurement interface
 
+Memory Monitor
+###############
+
+..  attention:: This only pertains to hardware Gen2/Gen3 with firmware 1.5.1+
+
+.. image:: ../../_static/images/plugins/acquisitionboard/acquisitionboard-04.png
+  :alt: Updated editor with a memory usage monitor on the left
+
+While data is waiting to be transferred from the acquisition board to the computer, it sits in the
+acquisition board's buffer. The memory monitor on the left provides a visualization of how much data
+has accumulated in this buffer as a percentage of its total capacity. The memory monitor should stay
+at or near zero. Accumulated data in the hardware's buffer indicates an error that is causing data
+to be read from the hardware too slowly. This might eventually halt the program if the buffer fills
+to its capacity.
+
 |
 
 Closed-loop feedback

source/User-Manual/Plugins/Network-Events.rst

@@ -46,16 +46,16 @@ The primary purpose of the Network Events module is to add TTL events to one or
 
 :code:`TTL [Line=1-256] [State=0/1]` – Sends an **ON** (1) or **OFF** (0) TTL event on the specified TTL line. 
 
-:code:`TTL [Word=unsigned_int64_value]` – Sends TTL event with the states of the first 64 lines combined to form the TTL word. Each line represents a different bit in the given unsigned 64-bit integer. For more information on how TTL words work, refer to :ref:`undertanding-ttl-events`.
+:code:`TTL [Word=unsigned_int64_value]` – Sends TTL event with the states of the first 64 lines combined to form the TTL word. Each line represents a different bit in the given unsigned 64-bit integer. For more information on how TTL words work, refer to :ref:`understanding-ttl-events`.
 
 Other commands
 ---------------
 
 The Network Events module can also respond to commands related to starting/stopping acquisition and recording. However, these commands are also available via the Open Ephys HTTP Server (added in GUI version 0.6.0). It's recommended to use the HTTP Server commands whenever possible, as these do not rely on a specific plugin.
 
-:code:`StartAcquisition` – Starts data aquisition
+:code:`StartAcquisition` – Starts data acquisition
 
-:code:`StopAcquisition` – Stops data aquisition
+:code:`StopAcquisition` – Stops data acquisition
 
 :code:`StartRecord [RecordNode=record_node_id] [CreateNewDir=1] [RecDir=recording_directory_path] [PrependText=some_text] [AppendText=some_text]` – Starts recording of data