From 4686380f1e1ece36da4228063c6e70aebd5f769e Mon Sep 17 00:00:00 2001
From: Hugos68 <hugokorteapple@gmail.com>
Date: Mon, 10 Mar 2025 14:13:13 +0100
Subject: [PATCH 1/2] docs(composition): typo

---
 website/data/overview/composition.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/data/overview/composition.mdx b/website/data/overview/composition.mdx
index 7d79abb33e..e076d58b37 100644
--- a/website/data/overview/composition.mdx
+++ b/website/data/overview/composition.mdx
@@ -51,7 +51,7 @@ element part needs to have a unique id.
 Each time you initiate the machine with the `useMachine` hook, you'll need to
 ensure that you provide a unique id.
 
-In most cases, you can rely on the framework providing unique a unique id for each component.
+In most cases, you can rely on the framework providing a unique id for each component.
 
 ### React
 

From d1bd5869086b120963a7a46c87db7c6433029982 Mon Sep 17 00:00:00 2001
From: Hugos68 <hugokorteapple@gmail.com>
Date: Mon, 10 Mar 2025 14:19:51 +0100
Subject: [PATCH 2/2] feat(composition): id for machine instead of component

---
 website/data/overview/composition.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/data/overview/composition.mdx b/website/data/overview/composition.mdx
index e076d58b37..e1536f30c1 100644
--- a/website/data/overview/composition.mdx
+++ b/website/data/overview/composition.mdx
@@ -51,7 +51,7 @@ element part needs to have a unique id.
 Each time you initiate the machine with the `useMachine` hook, you'll need to
 ensure that you provide a unique id.
 
-In most cases, you can rely on the framework providing a unique id for each component.
+In most cases, you can rely on the framework providing a unique id for each machine.
 
 ### React