diff --git a/background-processing/placing-processing-into-another-process.rst b/background-processing/placing-processing-into-another-process.rst
index 5d8dd1c..f2b0edf 100644
--- a/background-processing/placing-processing-into-another-process.rst
+++ b/background-processing/placing-processing-into-another-process.rst
@@ -8,7 +8,7 @@ Well scenarios
 
 * Your background processing consumes **too much CPU or other resources**, and this decreases main application's performance. So you want to use separate machine for processing background jobs.
 * You have long-running jobs that **are constantly aborted** (retrying, aborted, retried again and so on) due to regular shutdowns of the main application. So you want to use separate process with increased lifetime (and you can't use :doc:`always running mode <../deployment-to-production/making-aspnet-app-always-running>` for your web application).
-* *Do you have other suggestions? Please post them in the comment form below*.
+* *Do you have other suggestions? Please edit this page on GITHUB*.
 
 You can stop processing background jobs in your main application by simply removing the instantiation of the ``BackgroundJobServer`` class (if you create it manually) or removing an invocation of the ``UseHangfireServer`` method from your OWIN configuration class.