From 25833b830e49b2810b017352290fe8e7a2227356 Mon Sep 17 00:00:00 2001
From: OneHandedPirate <100222116+OneHandedPirate@users.noreply.github.com>
Date: Mon, 17 Feb 2025 06:14:06 +1000
Subject: [PATCH] Update scene.rst (#1640)

* Update scene.rst

* Create 1640.bugfix.rst
---
 CHANGES/1640.bugfix.rst                        | 1 +
 docs/dispatcher/finite_state_machine/scene.rst | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)
 create mode 100644 CHANGES/1640.bugfix.rst

diff --git a/CHANGES/1640.bugfix.rst b/CHANGES/1640.bugfix.rst
new file mode 100644
index 00000000..ef51e546
--- /dev/null
+++ b/CHANGES/1640.bugfix.rst
@@ -0,0 +1 @@
+Fix typo in docs
diff --git a/docs/dispatcher/finite_state_machine/scene.rst b/docs/dispatcher/finite_state_machine/scene.rst
index 0c385e78..40e9fe8c 100644
--- a/docs/dispatcher/finite_state_machine/scene.rst
+++ b/docs/dispatcher/finite_state_machine/scene.rst
@@ -30,7 +30,7 @@ They allow you to control and manage the flow of the conversation in a more orga
 Scene Lifecycle
 ---------------
 
-Each Scene can be "entered", "left" of "exited", allowing for clear transitions between different
+Each Scene can be "entered", "left" or "exited", allowing for clear transitions between different
 stages of the conversation.
 For instance, in a multi-step form filling interaction, each step could be a Scene -
 the bot guides the user from one Scene to the next as they provide the required information.