From 718811be9c450b73d1a693b1ef1b80d2af77ec30 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Celil=20Bu=C4=9Fra=20Karacan?=
 <49951195+cbugk@users.noreply.github.com>
Date: Fri, 19 Apr 2024 16:40:34 +0300
Subject: [PATCH] Update stateDiagram.md

Add explanation for naming a composite state
---
 packages/mermaid/src/docs/syntax/stateDiagram.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/mermaid/src/docs/syntax/stateDiagram.md b/packages/mermaid/src/docs/syntax/stateDiagram.md
index a5eff29bf..a78cb16d1 100644
--- a/packages/mermaid/src/docs/syntax/stateDiagram.md
+++ b/packages/mermaid/src/docs/syntax/stateDiagram.md
@@ -98,7 +98,7 @@ In a real world use of state diagrams you often end up with diagrams that are mu
 have several internal states. These are called composite states in this terminology.
 
 In order to define a composite state you need to use the state keyword followed by an id and the body of the composite
-state between \{\}. See the example below:
+state between \{\}. You can name a composite state on a seperate line just like a simple state. See the example below:
 
 ```mermaid-example
 stateDiagram-v2