From cbe31f19c303879ee866ba348862bf71eb3ff90d Mon Sep 17 00:00:00 2001
From: Dave T <17680170+davet2001@users.noreply.github.com>
Date: Sat, 21 Nov 2020 13:28:09 +0000
Subject: [PATCH] Clarify description of 'after_dependencies' (#730)

---
 docs/creating_integration_manifest.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/creating_integration_manifest.md b/docs/creating_integration_manifest.md
index 206ba754..7b2694ce 100644
--- a/docs/creating_integration_manifest.md
+++ b/docs/creating_integration_manifest.md
@@ -55,7 +55,7 @@ Dependencies are other Home Assistant integrations that you want Home Assistant
 
 ## After dependencies
 
-This option is used to specify optional dependencies that might be used. When `after_dependencies` is present, set up of an integration will wait for the other dependency to be set up before being set up. It will also make sure that the requirements of `after_dependencies` are installed so methods from the integration can be safely imported.  
+This option is used to specify dependencies that might be used by the integration but aren't essential. When `after_dependencies` is present, set up of an integration will wait for the `after_dependencies` to be set up before being set up. It will also make sure that the requirements of `after_dependencies` are installed so methods from the integration can be safely imported.  For example, if the `camera` integration might use the `stream` integration in certain configurations, adding `stream` to `after_dependencies` of `camera`'s manifest, will ensure that `stream` is loaded before `camera` if it is configured.  If `stream` is not configured, `camera` will still load.
 
 ## Code Owners