documentation updates

COPYRIGHT

@@ -42,7 +42,7 @@ individuals.  This list is not exhaustive.  Consult the individual
 files for more detailed copyright statements.
 
 
-Copyright (C) 1999-2015 The FreeRADIUS Server Project
+Copyright (C) 1999-2018 The FreeRADIUS Server Project
 
 Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Alan DeKok
 <aland@deployingradius.com>
@@ -52,6 +52,8 @@ Software Foundation, Inc.
 
 Copyright (C) 2011-2015 Arran Cudbard-Bell <a.cudbardb@freeradius.org>
 
+Copyright (C) 2012-2018 Matthew Newton <matthew-git@newtoncomputing.co.uk>
+
 Copyright (C) 2003, 2004, 2005 Kostas Kalevras <kkalev@noc.ntua.gr>
 
 Copyright (C) 2004  Cladju Consulting, Inc.

README.md

@@ -80,23 +80,25 @@ problems can be solved by carefully reading the debugging output,
 which includes WARNINGs about common issues, and suggestions for how
 they may be fixed.
 
-Read the FAQ.  Many questions are answered there.  See the Wiki
+Many questions are answered on the Wiki:
 
 https://wiki.freeradius.org
 
-Read the configuration files.  Many parts of the server have NO
-documentation, other than comments in the configuration file.
+Read the configuration files.  Many parts of the server are
+documented only with extensive comments in the configuration files.
 
-Consult the users mailing lists. 
+Search the mailing lists. For example, using Google, searching
+"site:lists.freeradius.org <search term>" will return results from
+the FreeRADIUS mailing lists.
 
-https://www.freeradius.org/list/users.html
+https://freeradius.org/support/
 
 
 ## Feedback, Defects, and Community Support
 
 If you have any comments, or are having difficulty getting FreeRADIUS
 to do what you want, please post to the 'freeradius-users' list
-(see the URL above). The FreeRADIUS mailing list is operated and
+(see the URL above). The FreeRADIUS mailing list is operated, and
 contributed to, by the FreeRADIUS community. Users of the list will be
 more than happy to answer your questions, with the caveat that you've
 read documentation relevant to your issue first.
@@ -105,6 +107,9 @@ If you suspect a defect in the server, would like to request a feature,
 or submit a code patch, please use the GitHub issue tracker for the
 freeradius-server
 [repository](https://github.com/FreeRADIUS/freeradius-server).
+However, it is nearly always best to raise the issue on the
+mailing lists first to determine whether it really is a defect or
+missing feature.
 
 Instructions for gathering data for defect reports can be found in
 ``doc/bugs.md`` or on the [wiki](https://wiki.freeradius.org/project/bug-reports).

doc/README.md

@@ -31,7 +31,7 @@ When asking for help on the users list, be sure the include a
 detailed and clear description of the problem, together with
 full debug output from FreeRADIUS, obtained by running
 
-    $ radiusd -X
+    # radiusd -X
 
 Developers only discussion is to be had on the developers list:
 
@@ -87,7 +87,7 @@ If you have ANY problems, concerns, or surprises when running
 the server, then run it in debugging mode, as root, from the
 command line:
 
-    $ radiusd -X
+    # radiusd -X
 
 It will produce a large number of messages.  The answers to many
 questions, and the solution to many problems, can usually be found in
@@ -97,4 +97,4 @@ For further details, see:
 
 https://www.freeradius.org/faq/
 
-and the `bugs.md`  file, in this directory.
+and the `bugs.md` file, in this directory.