diff --git a/source/_integrations/device_tracker.markdown b/source/_integrations/device_tracker.markdown
index a1a532794d7..d9de481051f 100644
--- a/source/_integrations/device_tracker.markdown
+++ b/source/_integrations/device_tracker.markdown
@@ -104,8 +104,8 @@ The `device_tracker.see` service can be used to manually update the state of a d
 
 | Service data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
-| `dev_id`               |       no | The second half of the `entity_id`, for example `tardis` for `device_tracker.tardis` |
-| `location_name`        |       no | The location, `home`, `not_home`, or the name of the zone |
+| `dev_id`               |       no | The `object_id`, for example `tardis` for `device_tracker.tardis` |
+| `location_name`        |      yes | The location, `home`, `not_home`, or the name of the zone |
 | `host_name`            |      yes | The hostname of the device tracker |
 | `mac`                  |      yes | The MAC address of the entity (only specify if you're updating a network based tracker) |
 | `gps`                  |      yes | If you're providing a location, for example `[51.513845, -0.100539]` |
diff --git a/source/_integrations/statistics.markdown b/source/_integrations/statistics.markdown
index da09bb48712..a8598d00448 100644
--- a/source/_integrations/statistics.markdown
+++ b/source/_integrations/statistics.markdown
@@ -14,7 +14,7 @@ ha_platforms:
   - sensor
 ---
 
-The `statistics` sensor platform consumes the state from other sensors. It exports the `mean` value as state and the following values as attributes: `count`, `mean`, `median`, `quantiles`, `stdev`, `variance`, `total`, `min_value`, `max_value`, `min_age`, `max_age`, `change`, `average_change` and `change_rate`. If the source is a binary sensor then only state changes are counted.
+The `statistics` sensor platform consumes the state from other sensors. It exports the `mean` value as state and the following values as attributes: `count`, `mean`, `median`, `quantiles`, `standard_deviation`, `variance`, `total`, `min_value`, `max_value`, `min_age`, `max_age`, `change`, `average_change` and `change_rate`. If the source is a binary sensor then only state changes are counted.
 
 Assuming the [`recorder`](/integrations/recorder/) integration is running (either configured explicitly or as part of a meta-integration/dependency, e.g., [`default_config`](/integrations/default_config/), [`history`](/integrations/history/), etc.), historical sensor data is read from the database on startup and is available immediately after a restart of the platform. If the [`recorder`](/integrations/recorder/) integration is *not* running, it can take time for the sensor to start reporting data because some attribute calculations require more than one value.