From b61823cb3a9f3419aae22683589a6033ccb50266 Mon Sep 17 00:00:00 2001 From: cecille Date: Tue, 16 Jan 2024 10:40:19 -0500 Subject: [PATCH] One more --- docs/getting_started/SDKBasics.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/getting_started/SDKBasics.md b/docs/getting_started/SDKBasics.md index cedc6c02a0bb2e..fee03ae7cd484d 100644 --- a/docs/getting_started/SDKBasics.md +++ b/docs/getting_started/SDKBasics.md @@ -44,10 +44,10 @@ makes your device your device. Most are generated statically using zap. The cluster implementations are the logic that back the cluster. The cluster implementation code receives messages from the ember layer to request data model -operations on the cluster (reads / writes / commands). They are also responsible -for event generation and attribute change reporting. Simple cluster logic can be -written in the ember callback functions, but more complex cluster logic is -handled in the run-time installed interface layers. +operations on the cluster (reads / writes / command invokes). They are also +responsible for event generation and attribute change reporting. Simple cluster +logic can be written in the ember callback functions, but more complex cluster +logic is handled in the run-time installed interface layers. ## SDK Organization (some key bits)