Documentation updates

Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>

www/building.xml

@@ -31,7 +31,8 @@ And <em>optionally</em> also:
   <li><b><tt><a href="http://code.google.com/p/libproxy/">libproxy</a></tt></b></li>
   <li><b><tt><a href="http://trousers.sourceforge.net/">trousers</a></tt></b> <i>(for TPM support if using GnuTLS)</i></li>
   <li><b><tt><a href="http://stoken.sourceforge.net/">libstoken</a></tt></b> <i>(for SecurID software token support)</i></li>
-  <li><b><tt><a href="http://www.nongnu.org/oath-toolkit/">liboath</a></tt></b> <i>(for RFC6238 TOTP support)</i></li>
+  <li><b><tt><a href="http://www.nongnu.org/oath-toolkit/">liboath</a></tt></b> <i>(for software HOTP/TOTP support)</i></li>
+  <li><b><tt><a href="https://pcsclite.alioth.debian.org/pcsclite.html">libpcsclite</a></tt></b> <i>(for Yubikey hardware HOTP/HOTP support)</i></li>
 </ul>
 <p>OpenConnect supports the use of HTTP and SOCKS proxies to connect to the
 AnyConnect service, even without using libproxy. You may wish to use libproxy

www/charset.xml

@@ -19,7 +19,7 @@ all of the time"</i>. This was the case up to and including the OpenConnect
 <p>Since its inception, however, OpenConnect has been ported to
 various less progressive POSIX-based systems and also to Windows,
 which has its own particular style of charset insanity. It was
-therefore necessary to implement some explcit handling for character
+therefore necessary to implement some explicit handling for character
 set conversion.</p>
 
 <p>The design of this character set handling is that the internal

www/features.xml

@@ -16,7 +16,8 @@
   <li>Authentication via HTTP forms.</li>
   <li>Authentication using SSL certificates &#8212; from local file, <a href="http://en.wikipedia.org/wiki/Trusted_Platform_Module">Trusted Platform Module</a> and <i>(when built with GnuTLS)</i> PKCS#11 smartcards.</li>
   <li>Authentication using SecurID software tokens <i>(when built with libstoken)</i></li>
-  <li>Authentication using RFC6238 TOTP software tokens <i>(when built with liboath)</i></li>
+  <li>Authentication using OATH TOTP or HOTP software tokens <i>(when built with liboath)</i></li>
+  <li>Authentication using Yubikey OATH tokens <i>(when built with libpcsclite)</i></li>
   <li><i>UserGroup</i> support for selecting between multiple configurations on a single VPN server.</li>
   <li>Data transport over TCP <i>(HTTPS)</i> or UDP <i>(DTLS)</i>.</li>
   <li>Keepalive and Dead Peer Detection on both HTTPS and DTLS.</li>