From c81a2ebf318cd62efaaf8117f972fd6cdbc902aa Mon Sep 17 00:00:00 2001 From: Simone Chemelli Date: Wed, 26 Jan 2022 18:58:55 +0100 Subject: [PATCH] Improve strings.sensor.json key wording (#1195) --- docs/internationalization/core.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/internationalization/core.md b/docs/internationalization/core.md index 39384d90..9429e004 100644 --- a/docs/internationalization/core.md +++ b/docs/internationalization/core.md @@ -80,9 +80,9 @@ The translation strings for the configuration flow handler are defined under the ### `strings.sensor.json` -Integrations can provide translations for states of its entities under other integrations like sensor. To do this, the entity will need a custom device class that starts with `__`. You can then provide translations that will only be applied for your entity. Note that you cannot customize your translation when you use an official device class. Those are standardized. +Integrations can provide translations for states of its entities under other integrations like sensor. To do this, the entity will need a custom device class that starts with `__` (note double underscore). You can then provide translations that will only be applied for your entity. Note that you cannot customize your translation when you use an official device class. Those are standardized. -To differentiate entities and their translations, provide different device classes. The following example `strings.sensor.json` is for a Moon sensor entity with the `moon__phase` device class: +To differentiate entities and their translations, provide different device classes. The following example `strings.sensor.json` is for a Moon domain sensor entity with the `moon__phase` device class: ```json {