From 5b8740a8722f170238c704754dda0a0987b26cbc Mon Sep 17 00:00:00 2001 From: Kevin Fowlks Date: Wed, 22 Mar 2017 10:54:48 -0400 Subject: [PATCH] Update component_loading.markdown (#2314) Changed the word "build-in" to "built-in" were applicable. --- source/developers/component_loading.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/component_loading.markdown b/source/developers/component_loading.markdown index f57148ec8b5..342aa60b7ed 100644 --- a/source/developers/component_loading.markdown +++ b/source/developers/component_loading.markdown @@ -17,7 +17,7 @@ A component will be loaded on start if a section (ie. `light:`) for it exists in Once loaded, a component will only be setup if all dependencies can be loaded and are able to setup. Keep an eye on the logs to see if your component could be loaded and initialized.

-You can override a built-in component by having a component with the same name in your config/custom_components folder. If the build-in component is inside a subfolder, take care to place your customization in a folder with the same name in config/custom_components/*folder*. Note that overriding build-in components is not recommended and will probably break things! +You can override a built-in component by having a component with the same name in your config/custom_components folder. If the built-in component is inside a subfolder, take care to place your customization in a folder with the same name in config/custom_components/*folder*. Note that overriding built-in components is not recommended and will probably break things!