Update docs

DOC/src/html/index.html

@@ -620,7 +620,7 @@ links.<br></p>
 Languages</h3>
 <p>There are several third party projects which provide wrappers
 for pigpio.<br></p>
-<p>Some I am aware of are:<br></p>
+<p>Some are listed here:<br></p>
 <ul>
 <li><a href="https://github.com/skvamme/pigpio">Erlang</a>
 (skvamme)</li>
@@ -635,7 +635,9 @@ diozero, a high level wrapper around pigpio, Pi4J, wiringPi etc
 "https://github.com/unosquare/pigpio-dotnet">.NET/mono</a>
 (unosquare)</li>
 <li><a href="https://github.com/fivdi/pigpio">Node.js</a>
-(fivdi)</li>
+A wrapper for the pigpio C library (fivdi)</li>
+<li><a href="https://github.com/guymcswain/pigpio-client">Node.js</a>
+A client for pigpio socket interface (guymcswain)</li>
 <li><a href="https://metacpan.org/pod/RPi::PIGPIO">Perl</a> (Gligan
 Calin Horea)</li>
 <li><a href=

pigpio.3

@@ -191,7 +191,11 @@ error PI_INITIALISED.
 
 .br
 If you intend to rely on signals sent to your application, you should
-turn off the internal signal handling as show in this example:
+turn off the internal signal handling as shown in this example:
+
+.br
+
+.br
 
 .EX
 int cfg = gpioCfgGetInternals();

pigpio.h

@@ -107,7 +107,8 @@ If the library is initialised the [*gpioCfg**] functions will return
 error PI_INITIALISED.
 
 If you intend to rely on signals sent to your application, you should
-turn off the internal signal handling as show in this example:
+turn off the internal signal handling as shown in this example:
+
 . .
 int cfg = gpioCfgGetInternals();
 cfg |= PI_CFG_NOSIGHANDLER;  // (1<<10)