From a8334f3e56cb772e891dc68e395c3e37a75119ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Laurent=20Inderm=C3=BChle?= <laurent.indermuehle@pm.me>
Date: Thu, 5 Oct 2023 10:28:18 +0200
Subject: [PATCH] typo

Co-authored-by: Andrew Klychkov <aaklychkov@mail.ru>
---
 changelogs/569_fix_column_uppercasing.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/changelogs/569_fix_column_uppercasing.yml b/changelogs/569_fix_column_uppercasing.yml
index 7645683..40863c5 100644
--- a/changelogs/569_fix_column_uppercasing.yml
+++ b/changelogs/569_fix_column_uppercasing.yml
@@ -9,7 +9,7 @@ major_changes:
     from being uppercased
     (https://github.com/ansible-collections/community.mysql/pull/569).
   - mysql_user - the ``column_case_sensitive`` argument's default value will be
-    changed to ``true`` in community.mysql 4.0.0. If your playbook expectd the
+    changed to ``true`` in community.mysql 4.0.0. If your playbook expected the
     column to be automatically uppercased for your users privileges, you should
     set this to false explicitly
     (https://github.com/ansible-collections/community.mysql/issues/577).