diff --git a/docs/creating_integration_file_structure.md b/docs/creating_integration_file_structure.md index ffc4c3cc..8938d1eb 100644 --- a/docs/creating_integration_file_structure.md +++ b/docs/creating_integration_file_structure.md @@ -33,5 +33,5 @@ Home Assistant will look for an integration when it sees the domain referenced i - `/custom_components/` - `homeassistant/components/` (built-in integrations) -You can override a built-in integration by having an integration with the same domain in your `/custom_components` folder. [The `manifest.json` file requires a version tag when you override a core integration](creating_integration_manifest.md/#version). An overridden core integration can be identified by a specific icon in the upper right corner of the integration box in the overview [![Open your Home Assistant instance and show your integrations.](https://my.home-assistant.io/badges/integrations.svg)](https://my.home-assistant.io/redirect/integrations/) +You can override a built-in integration by having an integration with the same domain in your `/custom_components` folder. [The `manifest.json` file requires a version tag when you override a core integration](creating_integration_manifest/#version). An overridden core integration can be identified by a specific icon in the upper right corner of the integration box in the overview [![Open your Home Assistant instance and show your integrations.](https://my.home-assistant.io/badges/integrations.svg)](https://my.home-assistant.io/redirect/integrations/) Note that overriding built-in integrations is not recommended as you will no longer get updates. It is recommended to pick a unique name.