Fix missing refs, remove nonexistent pages

source/User-Manual/Benchmarking.rst

@@ -41,7 +41,7 @@ Workstation
 ############
 
 | **Computer:** Windows 10, 32-core Intel Core i9, 128 GB RAM, 3 NVMe SSDs
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`lfpviewer`
 | **Buffer duration:** 40 ms
 | **Simulated source:** Neuropixels 1.0
 
@@ -58,7 +58,7 @@ Workstation
 |
 
 | **Computer:** Windows 10, 32-core Intel Core i9, 128 GB RAM, 3 NVMe SSDs
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`lfpviewer`
 | **Buffer duration:** 40 ms
 | **Simulated source:** Neuropixels 2.0
 
@@ -76,7 +76,7 @@ Workstation
 |
 
 | **Computer:** Windows 10, 32-core Intel Core i9, 128 GB RAM, 3 NVMe SSDs
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`lfpviewer`
 | **Buffer duration:** 40 ms
 | **Simulated source:** Single stream (e.g. Open Ephys Acquisition Board)
 
@@ -94,7 +94,7 @@ Workstation
 |
 
 | **Computer:** Windows 10, 32-core Intel Core i9, 128 GB RAM, 3 NVMe SSDs
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`BandpassFilter` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`BandpassFilter` > :ref:`lfpviewer`
 | **Buffer duration:** 40 ms
 | **Simulated source:** Single stream (e.g. Open Ephys Acquisition Board)
 
@@ -112,7 +112,7 @@ Workstation
 |
 
 | **Computer:** Windows 10, 32-core Intel Core i9, 128 GB RAM, 3 NVMe SSDs
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`BandpassFilter` > :ref:`LFP Viewer` > :ref:`spikedetector` > :ref:`spikeviewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`BandpassFilter` > :ref:`lfpviewer` > :ref:`spikedetector` > :ref:`spikeviewer`
 | **Buffer duration:** 40 ms
 | **Simulated source:** Single stream (e.g. Open Ephys Acquisition Board)
 
@@ -131,7 +131,7 @@ Laptop
 ############
 
 | **Computer:** Windows 10, 16-core Intel Core i7, 32 GB RAM, SKHynix 512 GB SSD
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`lfpviewer`
 | **Buffer duration:** 21 ms
 | **Simulated source:** Neuropixels 1.0
 
@@ -145,7 +145,7 @@ Laptop
 |
 
 | **Computer:** Windows 10, 16-core Intel Core i7, 32 GB RAM, SKHynix 512 GB SSD
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`lfpviewer`
 | **Buffer duration:** 21 ms
 | **Simulated source:** Neuropixels 2.0
 
@@ -159,7 +159,7 @@ Laptop
 |
 
 | **Computer:** Windows 10, 16-core Intel Core i7, 32 GB RAM, SKHynix 512 GB SSD
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`lfpviewer`
 | **Buffer duration:** 21 ms
 | **Simulated source:** Single stream (e.g. Open Ephys Acquisition Board)
 
@@ -176,7 +176,7 @@ Laptop
 |
 
 | **Computer:** Windows 10, 16-core Intel Core i7, 32 GB RAM, SKHynix 512 GB SSD
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`BandpassFilter` > :ref:`LFP Viewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`BandpassFilter` > :ref:`lfpviewer`
 | **Buffer duration:** 21 ms
 | **Simulated source:** Single stream (e.g. Open Ephys Acquisition Board)
 
@@ -193,7 +193,7 @@ Laptop
 |
 
 | **Computer:** Windows 10, 16-core Intel Core i7, 32 GB RAM, SKHynix 512 GB SSD
-| **Signal chain:** :ref:`sourcesim` > :ref:`Record Node` > :ref:`BandpassFilter` > :ref:`LFP Viewer` > :ref:`spikedetector` > :ref:`spikeviewer`
+| **Signal chain:** :ref:`sourcesim` > :ref:`recordnode` > :ref:`BandpassFilter` > :ref:`lfpviewer` > :ref:`spikedetector` > :ref:`spikeviewer`
 | **Buffer duration:** 21 ms
 | **Simulated source:** Single stream (e.g. Open Ephys Acquisition Board)
 

source/User-Manual/Plugins/Record-Node.rst

@@ -82,7 +82,7 @@ To set the data format for a given Record Node, send the **index** of the record
 
 
 Selecting channels to record
-####################
+#############################
 
 To change the recorded channels for a given stream, send the following message to :code:`/api/processors/<id>/config`:
 

source/User-Manual/Plugins/TTL-Panels.rst

@@ -27,11 +27,12 @@ The TTL Panels plugin is not included by default in the Open Ephys GUI. To insta
 
 The Plugin Installer also allows you to upgrade to the latest version of this plugin, if it's already installed.
 
-.. _undertanding-ttl-events:
+.. _understanding-ttl-events:
+
 Understanding TTL events
 ###########################
 
-TTL (transistor–transitor logic) events are the primary way that data sampled at irregular intervals is transmitted between plugins. Each TTL event has a *state* (on or off), a *line* (1-256), and a *stream* associated with it. Each plugin that generates events will have a unique TTL channel (in order to help trace the origin of these events), but channels on the same data stream will share the same set of TTL lines. This makes it possible for a plugin to respond to an event on Line 1 in the same way whether this event was triggered by an external piece of hardware and added by a Source plugin or, or generated by a Filter plugin further down the signal chain. In addition, the states of the first 64 lines can be combined to form a *TTL word*, with each line representing a different bit in an unsigned 64-bit integer.
+TTL (transistor-transistor logic) events are the primary way that data sampled at irregular intervals is transmitted between plugins. Each TTL event has a *state* (on or off), a *line* (1-256), and a *stream* associated with it. Each plugin that generates events will have a unique TTL channel (in order to help trace the origin of these events), but channels on the same data stream will share the same set of TTL lines. This makes it possible for a plugin to respond to an event on Line 1 in the same way whether this event was triggered by an external piece of hardware and added by a Source plugin or, or generated by a Filter plugin further down the signal chain. In addition, the states of the first 64 lines can be combined to form a *TTL word*, with each line representing a different bit in an unsigned 64-bit integer.
 
 It's important to keep this nomenclature in mind, because in previous versions of the GUI, the terms "channel," "line," and "bit" were often used interchangeably. Now, they have distinct meanings that will hopefully make TTL events easier to work with.
 

source/User-Manual/Plugins/index.rst

@@ -26,7 +26,7 @@ Officially supported Filter plugins: :ref:`bandpassfilter`, :ref:`channelmap`, :
 
 **Sinks** send data to an external source, such as a display, stimulator, etc., without altering the underlying data streams. Data should pass through Sinks unchanged.
 
-Officially supported Sink plugins: :ref:`arduinooutput`, :ref:`datasnapshot`, :ref:`eventbroadcaster`, :ref:`falconoutput`, :ref:`latencyhistogram`, :ref:`lfpviewer`, :ref:`multibandintegrator`, :ref:`onlinepsth`, :ref:`probeviewer`, :ref:`pulsepal`, :ref:`riveroutput`, :ref:`spectrumviewer`, :ref:`spikeviewer`, :ref:`zmqinterface`
+Officially supported Sink plugins: :ref:`arduinooutput`, :ref:`datasnapshot`, :ref:`eventbroadcaster`, :ref:`falconoutput`, :ref:`latencyhistogram`, :ref:`lfpviewer`, :ref:`multibandintegrator`, :ref:`onlinepsth`, :ref:`probeviewer`, :ref:`pulsepal`, :ref:`spectrumviewer`, :ref:`spikeviewer`, :ref:`zmqinterface`
 
 **Utilities** perform miscellaneous functions related to the signal chain. 
 
@@ -164,7 +164,6 @@ To remove a plugin, simply click the "Uninstall" button. This will delete the pl
     Record-Node
     RHD-Rec-Controller
     Ripple-Detector
-    River-Output
     Scale-Converter
     Source-Sim
     Spectrum-Viewer

source/User-Manual/Whats-new-in-v100.rst

@@ -126,8 +126,6 @@ All versions of the Open Ephys acquisition board are now supported by one plugin
 Deprecated plugins
 --------------------
 
-The :ref:`riveroutput` plugin has been removed from the plugin installer, as this was rarely used.
-
-
+The River Output plugin has been removed from the plugin installer, as this was rarely used.
 
 |