diff --git a/.github/issue_template.md b/.github/issue_template.md
index 386b0639..94bdb323 100644
--- a/.github/issue_template.md
+++ b/.github/issue_template.md
@@ -1,17 +1,23 @@
-<!--- Provide a general summary of the issue in the Title above -->
+<!---
+Provide a general summary of the issue in the Title above
 
-<!-- stop! If your ticket is about a device not being detected correctly, -->
-<!-- see SNMP::Info: https://github.com/netdisco/snmp-info/issues/new -->
+STOP! If your ticket is about a device not being detected correctly,
+see SNMP::Info: https://github.com/netdisco/snmp-info/issues/new
 
-<!-- stop! If you have new MIBs to submit, -->
-<!-- see netdisco-mibs: https://github.com/netdisco/netdisco-mibs/issues/new -->
+STOP! If you have new MIBs to submit,
+see netdisco-mibs: https://github.com/netdisco/netdisco-mibs/issues/new
 
-<!-- everything else about Netdisco's behaviour is good, here :-D -->
+STOP! If you are running a netdisco docker setup,
+see netdisco-docker: https://github.com/netdisco/netdisco-docker/issues/new
+
+everything else about Netdisco's behaviour is good, here :-D
+
+when including netdisco config snippets, whitespace matters since it's a yaml file
+for github issues it really helps if you include the relevant config parts in a codeblock (code fencing)
+see the "code" subject on https://guides.github.com/features/mastering-markdown/ for that)
+this should preserve spaces in the issue tracker and make troubleshooting quicker
+-->
 
-<!--- when including netdisco config snippets, whitespace matters since it's a yaml file -->
-<!--- for github issues it really helps if you include the relevant config parts in a codeblock (code fencing) -->
-<!--- see the "code" subject on https://guides.github.com/features/mastering-markdown/ for that) -->
-<!--- this should preserve spaces in the issue tracker and make troubleshooting quicker -->
 
 ## Expected Behavior
 <!--- If you're describing a bug, tell us what should happen -->