From 894a26d71321704428e01400c6f5c1d106002fbf Mon Sep 17 00:00:00 2001 From: LHuisingh <31296055+LHuisingh@users.noreply.github.com> Date: Sun, 19 Jan 2025 23:08:17 -0800 Subject: [PATCH] Make wording consistent (#37006) Make the wording relating to attributes more consistent within this sentence. --- source/_docs/configuration/state_object.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/state_object.markdown b/source/_docs/configuration/state_object.markdown index 7f70fd8a92e..c792feb5e35 100644 --- a/source/_docs/configuration/state_object.markdown +++ b/source/_docs/configuration/state_object.markdown @@ -32,7 +32,7 @@ The `state` prefix indicates that this information is part of the state object ( ### About the state -The screenshot shows three lights in different states (the `state.state`): `on`, `off`, and `unavailable`. Each light comes with its own entity state attributes such as `supported_color_modes`, `supported_features`. These attributes have their own state: the state of `supported_color_modes` is `color_temp` and `hs`, the state of the `supported_features` attribute is `4`. +The screenshot shows three lights in different states (the `state.state`): `on`, `off`, and `unavailable`. Each light comes with its own entity state attributes such as `supported_color_modes`, `supported_features`. These attributes have their own state: the state of the `supported_color_modes` attribute is `color_temp` and `hs`, the state of the `supported_features` attribute is `4`.

Screenshot showing three lights with different states: `on`, `off`, or `unavailable`