-<P>You start the connection, from within a sysop enabled cluster login, by typing in the word <EM>connect</EM> followed by a script name like this ....
+
+<H2><A NAME="ss2.2">2.2</A> <A HREF="adminmanual.html#toc2.2">Filtering words from text fields in Announce, Talk and DX spots</A>
+</H2>
+
+<P>From version 1.48 onwards the interface to this has changed. You can now
+use the commands <EM>set/badword</EM> to add words that you are not prepared
+to see on the cluster, <EM>unset/badword</EM> to allow that word again and
+<EM>show/badword</EM> to list the words that you have set.</P>
+
+<P>If you have a previous <EM>/spider/data/badwords</EM>, the first time you start
+the node, it will read and convert this file to the new commands. The old style
+file will then be removed.</P>
+
+<H2><A NAME="ss2.3">2.3</A> <A HREF="adminmanual.html#toc2.3">Stopping (possibly bad) DX Spots from Nodes or Spotters</A>
+</H2>
+
+<P>
+There are a number of commands that control whether a spot progresses
+any further by regarding it as "bad" in some way.</P>
+
+<P>A DX Spot has a number of fields which can be checked to see whether they
+contain "bad" values, they are: the DX callsign itself, the Spotter and
+the Originating Node.</P>
+
+<P>There are a set of commands which allow the sysop to control whether a
+spot continues:-</P>