From 3197ada1d9868b28d25ca75b84bd727f535f32ae Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Fri, 13 Sep 2024 16:20:22 +0200
Subject: [PATCH] Z-Wave association group: clarify wording (#34718)

---
 source/_integrations/zwave_js.markdown | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index 95351f3896d..387676c3c75 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -980,9 +980,9 @@ In Home Assistant, it is currently not possible to set the Z-Wave controller int
 
 A Z-Wave controller that manages an empty network can also join a different network and act as a secondary controller there. However, with Home Assistant, this is not possible. Home Assistant does not allow the Z-Wave controller to join another network, because Home Assistant acts as the central hub.
 
-## Z-Wave association groups used
+## Z-Wave association groups
 
-In Home Assistant, a single [association group](#association-group) is supported:
+In Home Assistant, a single [association group](#association-group) is implemented:
 
 - **Group 1**: This is an association group that includes only one device. It is used after a [factory reset](#controller), to send a **Device Reset Locally Notification**.