home-assistant · fabaff · Oct 16, 2019 · Oct 16, 2019 · Oct 16, 2019 · Oct 16, 2019
diff --git a/source/_integrations/automation.markdown b/source/_integrations/automation.markdown
@@ -31,3 +31,12 @@ automation:
       - platform: state
   ...
 ```
+
+## Configuration
+
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
+
+```yaml
+# Example configuration.yaml entry
+automation:
+```
diff --git a/source/_integrations/cloud.markdown b/source/_integrations/cloud.markdown
@@ -10,6 +10,10 @@ ha_iot_class: Cloud Push
 
 The Home Assistant Cloud allows you to quickly integrate your local Home Assistant with various cloud services like Amazon Alexa and Google Assistant. [Learn more.](/cloud)
 
+## Configuration
+
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
+
 ```yaml
 # Example configuration.yaml entry to enable the cloud component
 cloud:

@@ -10,7 +10,7 @@ ha_qa_scale: internal
 
 The `config` integration is designed to display panels in the frontend to configure and manage parts of Home Assistant.
 
-To enable the configuration panel, add the following to your `configuration.yaml` file:
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Example configuration.yaml entry

@@ -8,7 +8,7 @@ ha_qa_scale: internal
 ha_release: 0.7
 ---
 
-This offers the official frontend to control Home Assistant.
+This offers the official frontend to control Home Assistant. This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Example configuration.yaml entry

@@ -14,8 +14,7 @@ component for storing the data and uses the same database setting.
 If any entities are excluded from being recorded,
 no history will be available for these entities.
 
-To enable the history option in your installation,
-add the following to your `configuration.yaml` file:
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Basic configuration.yaml entry

diff --git a/source/_integrations/light.mqtt.markdown b/source/_integrations/light.mqtt.markdown
@@ -8,7 +8,7 @@ ha_iot_class: Configurable
 ha_release: 0.8
 ---
 
-The `mqtt` light platform with lets you control your MQTT enabled lights through one of the supported message schemas.
+The `mqtt` light platform lets you control your MQTT enabled lights through one of the supported message schemas.
 
 ## Comparison of light MQTT schemas
 

@@ -17,8 +17,7 @@ the `recorder` integration for storing the data. This means that if the
 PostgreSQL as data store, the `logbook` integration does not use the default
 SQLite database to store data.
 
-To enable the logbook in your installation,
-add the following to your `configuration.yaml` file:
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Example configuration.yaml entry

diff --git a/source/_integrations/map.markdown b/source/_integrations/map.markdown
@@ -8,7 +8,7 @@ ha_qa_scale: internal
 ha_release: 0.56
 ---
 
-This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/integrations/device_tracker/) documentation.
+This offers a map on the frontend to display the location of tracked devices. To set up tracked devices, look at the [device tracker](/integrations/device_tracker/) documentation. This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Example configuration.yaml entry

@@ -16,8 +16,7 @@ If you are a mobile app developer, see the [developer documentation](https://dev
 
 ## Configuration
 
-This integration is by default enabled, unless you've disabled or removed the `default_config:` line from your configuration.
-If that is the case, the following example shows you how to enable this integration manually:
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Example configuration.yaml entry

diff --git a/source/_integrations/person.markdown b/source/_integrations/person.markdown
@@ -32,7 +32,7 @@ You can manage persons via the UI from the person page inside the configuration
 
 ## Configuring the `person` integration via the Home Assistant configuration panel
 
-If you prefer to use the configuration panel to configure the `person` integration simply add one line to your `configuration.yaml` file and restart Home Assistant.
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 person:

diff --git a/source/_integrations/ssdp.markdown b/source/_integrations/ssdp.markdown
@@ -12,7 +12,7 @@ Integrations can opt-in to be found by adding [an SSDP section](https://develope
 
 ## Configuration
 
-To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Example configuration.yaml entry

@@ -17,6 +17,8 @@ below the horizon. The sun can be used within automation as
 
 ## Configuration
 
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
+
 ```yaml
 # Example configuration.yaml entry
 sun:

diff --git a/source/_integrations/system_health.markdown b/source/_integrations/system_health.markdown
@@ -10,9 +10,10 @@ ha_release: 0.87
 
 The System Health integration provides an API to offer information on the system and its components. It also allows to run diagnostic tools to diagnose problems.
 
-System health is included as part of the [default config](https://www.home-assistant.io/integrations/default_config/) starting with Home Assistant 0.88. If you do not wish to use the default config, you can add the following to your configuration.yaml file.
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
+# Example configuration.yaml entry
 system_health:
 ```
 

diff --git a/source/_integrations/updater.markdown b/source/_integrations/updater.markdown
@@ -20,7 +20,7 @@ The `updater` binary sensor will wait one hour after startup until it performs t
 
 ## Configuration
 
-To integrate this into Home Assistant, add the following section to your `configuration.yaml` file:
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
 
 ```yaml
 updater:

@@ -13,7 +13,7 @@ Integrations can opt-in to be found by adding either [a Zeroconf section](https:
 
 ## Configuration
 
-To have Home Assistant scan for integrations using zeroconf and HomeKit, add the following section to your `configuration.yaml` file:
+This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, and you wish to have Home Assistant scan for integrations using zeroconf and HomeKit, the following example shows you how to enable this integration manually:
 
 ```yaml
 # Example configuration.yaml entry
-Original file line number
+Diff line change
@@ Expand Up @@
     ## Configuring the `person` integration via the Home Assistant configuration panel
-    If you prefer to use the configuration panel to configure the `person` integration simply add one line to your `configuration.yaml` file and restart Home Assistant.
+    This integration is by default enabled, unless you've disabled or removed the [`default_config:`](https://www.home-assistant.io/integrations/default_config/) line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
     ```yaml
     person:
@@ Expand Down @@