summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Brady <mikebrady@eircom.net>2017-12-07 17:51:32 +0000
committerGitHub <noreply@github.com>2017-12-07 17:51:32 +0000
commitd17c9b05d9150f3083955ef787fae5e059380a55 (patch)
treeba6295fcc5ef01aa4853b5f2782e9325d3cfd5f6
parenta676dd27be229203a62a8e4715678d474d5da1a9 (diff)
Update CONTRIBUTING.md
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5480906..170f885 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -10,7 +10,7 @@ Changes and additions in the development branch make their way eventually to the
Issues Reports
----
-Issue reports are welcome, but before you report an issue, please have a look though the issues, open and closed, and check for hints in the [TROUBLESHOOTING](TROUBLESHOOTING.md) page. It would be great to give some details of the device and version of Linux or FreeBSD in use along with the version of Shairport Sync you are using (use `$ shairport-sync -V` to get this). Then, if possible, some diagnostic information from the log or logfile wold be useful.
+Issue reports are welcome, but before you report an issue, please have a look though the issues, open and closed, and check for hints in the [TROUBLESHOOTING](TROUBLESHOOTING.md) page. It would be great to give some details of the device and version of Linux or FreeBSD in use along with the version of Shairport Sync you are using (use `$ shairport-sync -V` to get this). Then, if possible, some diagnostic information from the log or logfile would be useful.
In general, a log verbosity of 2 is plenty (`-vv`, or the relevant entry in the configuration file), and it's usally helpful if statistics have been enabled (`--statistics` on the command line, or the relevant entry in the configuration file).