diff --git a/doc/source/admin/production.md b/doc/source/admin/production.md
index afa14d22584..3ba2f84e712 100644
--- a/doc/source/admin/production.md
+++ b/doc/source/admin/production.md
@@ -41,10 +41,9 @@ The steps to install Galaxy mostly follow those of the [regular instructions](ht
 
 ### Disable the developer settings
 
-Two options are set in the sample `config/galaxy.yml` which should not be enabled on a production server. You should set both to `false`:
+Debugging options are set in the sample `config/galaxy.yml` which should not be enabled on a production server.  Check the following items:
 
 * `debug: false` - Disable middleware that loads the entire response in memory for displaying debugging information in the page.  If left enabled, the proxy server may timeout waiting for a response or your Galaxy process may run out of memory if it's serving large files.
-* `use_interactive: false` - Disables displaying and live debugging of tracebacks via the web.  Leaving it enabled will expose your configuration (database password, id_secret, etc.).
 * Disable `filter-with: gzip`.  Leaving the gzip filter enabled will cause UI failures because of the way templates are streamed once `debug` is set to `False`.  You will still be able (and are encouraged) to enable gzip in the proxy server.
 
 During deployment, you may run into problems with failed jobs.  By default, Galaxy removes files related to job execution. You can instruct Galaxy to keep files of failed jobs with: `cleanup_job: onsuccess`