1 files changed, 8 insertions, 7 deletions
diff --git a/SUPPORT b/SUPPORT
index 5d852074..f1705aaa 100644
--- a/SUPPORT
+++ b/SUPPORT
@@ -25,7 +25,8 @@ directly.
 In brief, always provide the version of the software that you are
 using, and when requesting features or reporting bugs, first check to
-see that the issue has not already been addressed in the CVS tree.
+see that the issue has not already been addressed in the current Git
+code.
 GETTING HELP
@@ -47,8 +48,8 @@ REPORTING BUGS AND SUBMITTING PATCHES
 Bug reports, investigations of possible bugs, feature requests, and
 patch submissions should be submitted to the development list at
-mailto:nagiosplug-devel@lists.sourceforge.net. Please raise a tracker first 
+mailto:nagiosplug-devel@lists.sourceforge.net. Please raise an issue first 
-in Sourceforge, otherwise your email is likely to be missed over time.
+in GitHub, otherwise your email is likely to be missed over time.
 You should identify the version, preferably in the subject line. 
 However, to best use developer resources, it is suggested that you 
@@ -56,10 +57,10 @@ reference your report to one of the following sources:
  1) The most recent release, including beta's
-  2) The twice-daily snapshots (there's a link provided on
+  2) The current snapshots (there's a link provided on
-     http://nagiosplug.sourceforge.net)
+     https://www.nagios-plugins.org/download.html)
-  3) The current CVS tree from sourceforge
+  3) The current Git code from GitHub
 (This does not mean you should run any of these sources in a
 production environment - the latter two you clearly should
@@ -69,7 +70,7 @@ which are most recent.)
 From experience, I know that most bugs can be fixed with only a few
 more moments work than it takes to determine if the bug is still
-present in the CVS tree. If you can save a developer the expense of
+present in the Git tree. If you can save a developer the expense of
 that time, you ensure that bugs are fixed more rapidly, and thus you
 ensure your problem resolution is reflected in a stable release more
 quickly.

diff --git a/SUPPORT b/SUPPORT index 5d852074..f1705aaa 100644 --- a/SUPPORT +++ b/SUPPORT
@@ -25,7 +25,8 @@ directly.
25		25
26	In brief, always provide the version of the software that you are	26	In brief, always provide the version of the software that you are
27	using, and when requesting features or reporting bugs, first check to	27	using, and when requesting features or reporting bugs, first check to
28	see that the issue has not already been addressed in the CVS tree.	28	see that the issue has not already been addressed in the current Git
		29	code.
29		30
30	GETTING HELP	31	GETTING HELP
31		32
@@ -47,8 +48,8 @@ REPORTING BUGS AND SUBMITTING PATCHES
47		48
48	Bug reports, investigations of possible bugs, feature requests, and	49	Bug reports, investigations of possible bugs, feature requests, and
49	patch submissions should be submitted to the development list at	50	patch submissions should be submitted to the development list at
50	mailto:nagiosplug-devel@lists.sourceforge.net. Please raise a tracker first	51	mailto:nagiosplug-devel@lists.sourceforge.net. Please raise an issue first
51	in Sourceforge, otherwise your email is likely to be missed over time.	52	in GitHub, otherwise your email is likely to be missed over time.
52		53
53	You should identify the version, preferably in the subject line.	54	You should identify the version, preferably in the subject line.
54	However, to best use developer resources, it is suggested that you	55	However, to best use developer resources, it is suggested that you
@@ -56,10 +57,10 @@ reference your report to one of the following sources:
56		57
57	1) The most recent release, including beta's	58	1) The most recent release, including beta's
58		59
59	2) The twice-daily snapshots (there's a link provided on	60	2) The current snapshots (there's a link provided on
60	http://nagiosplug.sourceforge.net)	61	https://www.nagios-plugins.org/download.html)
61		62
62	3) The current CVS tree from sourceforge	63	3) The current Git code from GitHub
63		64
64	(This does not mean you should run any of these sources in a	65	(This does not mean you should run any of these sources in a
65	production environment - the latter two you clearly should	66	production environment - the latter two you clearly should
@@ -69,7 +70,7 @@ which are most recent.)
69		70
70	From experience, I know that most bugs can be fixed with only a few	71	From experience, I know that most bugs can be fixed with only a few
71	more moments work than it takes to determine if the bug is still	72	more moments work than it takes to determine if the bug is still
72	present in the CVS tree. If you can save a developer the expense of	73	present in the Git tree. If you can save a developer the expense of
73	that time, you ensure that bugs are fixed more rapidly, and thus you	74	that time, you ensure that bugs are fixed more rapidly, and thus you
74	ensure your problem resolution is reflected in a stable release more	75	ensure your problem resolution is reflected in a stable release more
75	quickly.	76	quickly.