Updated FAQ (markdown)

FAQ.md

@@ -5,7 +5,7 @@ Here are some of the most common questions compiled from the hamlib mailing list
 
 Hamlib is fundamentally a C language linkable subroutine library, developed primarily using GNU tools on Linux systems. The library aims to provide a "rig-independent" application programming interface (API) that allows programmers to write applications that control transceivers, rotators, and other devices used in Amateur Radio and similar services. (These devices, except for rotators, are called "rigs".)
 
-Hamlib provides bindings for languages other than C, such as C++, Python, Perl, and TCL. (some limitations may exist) There is an application program, rigctl, which may be used to control a rig from the command line or fron a script. A network daemon version rigctld is also in development and in use by various applications. 
+Hamlib provides bindings for languages other than C, such as C++, Lua, Python (2 and 3), Perl, and TCL. (some limitations may exist) There is an application program, rigctl, which may be used to control a rig from the command line or fron a script. A network daemon version rigctld is also in development and in use by various applications. 
 
 ## Who is the target user of Hamlib?
 
@@ -13,9 +13,7 @@ Hamlib is written to support programmers who are writing rig control, logging, a
 
 ## I downloaded or purchased a program that uses Hamlib; where do I get support?
 
-Support is the responsibility of the provider of your application program -- or its associated Internet discussion group. The Hamlib project is not set up to provide support to non-programmer users.
-
-That said, we do wish to encourage those users interested in helping to test their rigs as we develop support in the associated backend(s). Please post to the Hamlib-developer mailing list to announce your intention to help. 
+First, contact the application developer as they will be able to determine the source of the issue.  If it turns out to be a problem with Hamlib, you're invited to post your to the Hamlib developer mailing list.  Often this leads to a fix or enhancement for your particular device.  We do wish to encourage those users interested in testing their rigs to post to the list as we develop support in the associated backend(s).
 
 ## What platforms are supported?
 
@@ -23,11 +21,11 @@ The base platform is x86 Linux, but the source has been compiled in many archite
 
 ## Does Hamlib work under Windows?
 
-Hamlib works under Windows, as made available from download section. It works also under the [Unix-like cygwin](http://www.cygwin.com/) environment. 
+Hamlib works under Windows, both 32 and 64 bit versions, as made available from the download section. It also works under the [Unix-like cygwin](http://www.cygwin.com/) environment for Windows. 
 
 ## Is my rig supported?
 
-Check out the [supported radios] page. You could also type `rigctl --list` after having compiled and/or installed Hamlib. It will display a neat list sorted by Hamlib RigId and including Manufacturer, Model number and backend Version number and status. Here is an example: 
+Check out the [supported radios] page. You could also type `rigctl --list` after having compiled and/or installed Hamlib. It will display a neat list sorted by Hamlib RigId including Manufacturer, Model number and backend Version number and status. Here is an example: 
 
 ~~~~
  Rig #  Mfg                    Model                   Version         Status
@@ -46,7 +44,7 @@ Check out the [supported radios] page. You could also type `rigctl --list` after
 
 ## How do I know if my rig really works with hamlib?
 
-There is a fairly good description in the [README.betatester](http://hamlib.git.sourceforge.net/git/gitweb.cgi?p=hamlib/hamlib;a=blob_plain;f=README.betatester;hb=refs/heads/master) file, included with the Hamlib source code. The first tool to use would be `rigctl`, which is very powerful in testing basic rig commands. Suppose I own a Kenwood TS-850, which is hooked up to the first serial port in the Linux OS.
+There is a fairly good description in the [README.betatester](https://github.com/Hamlib/Hamlib/blob/master/README.betatester) file, included with the Hamlib source code. The first tool to use would be `rigctl`, which is very powerful in testing basic rig commands. Suppose I own a Kenwood TS-850, which is hooked up to the first serial port in the Linux OS.
 
     $ rigctl -r /dev/ttyS0 -m 209
 
@@ -83,7 +81,7 @@ No, you can't. The serial port can only be accessed by one program at the same t
 
     $ rigctld -m 210 -r /dev/ttyS1 &
 
-Next, you can start you favourite software and select NET rigctl or model 2 to access the information, or simply control it with the following:
+Next, you can start your favorite software and select NET rigctl or model 2 to access the information, or simply control it with the following:
 
     $ rigctl -m 2 -r localhost
 
@@ -129,7 +127,7 @@ This process can be integrated into your autoconf/automake build system with pkg
 
     PKG_CHECK_MODULES(HAMLIB, hamlib, HAVE_HAMLIB=true, HAVE_HAMLIB=false)
 
-to your `configure.ac`. In addition to `HAVE_HAMLIB`, the variables `HAMLIB_LIBS` and `HAMLIB_CFLAGS` will be created. To substitute on them you'll have to `AC_SUBST` both of them separately. 
+to your `configure.ac`. In addition to `HAVE_HAMLIB`, the variables `HAMLIB_LIBS` and `HAMLIB_CFLAGS` will be created. To use them you'll have to `AC_SUBST` both of them separately. 
 
 ## `make install` is okay, but rigctl complains it cannot find a library. What's wrong?