Merge pull request juju#1267 from mbruzek/auto-retry-2

Adding link to models-config document.

Author: matthewhelmke

src/en/developer-debugging.md

@@ -148,16 +148,20 @@ terminating.
 
 Prior to version 2.0, hooks returning an error will block until the user
 takes an action to retry them manually, by issuing the command `juju resolved
---retry unit-name/#` for the affected unit. Juju version 2.0 and up will
-automatically retry hooks in error periodically. However, the `juju resolved
---retry` command may still be used to retry the hook immediately. After
-retrying, go back to the debug-hooks session to interact with he Juju
-environment.
+--retry unit-name/#` for the affected unit. After issuing the retry command,
+go back to the debug-hooks session to interact with the Juju environment.
 
 ```bash
 juju resolved --retry mysql/0
 ```
 
+Starting with Juju version 2.0 hooks returning errors will be automatically 
+retried periodically. However, the `juju resolved --retry` command may still be
+used to retry the hook immediately. See the 
+[General configuration options](./models-config#retrying-failed-hooks)
+for more information on the automatic retry feature and how to disable this 
+behaviour.
+
 ## Debugging Reactive
 
 Reactive charms can set states. It may be helpful to see these states for