From 93d10e63b04ff3c1ada172997cb0ef519052f882 Mon Sep 17 00:00:00 2001
From: Shawn <506895667@qq.com>
Date: Thu, 8 Sep 2022 16:53:24 +0800
Subject: [PATCH] chore: update CHANGES-4.3.md for #8927

---
 CHANGES-4.3.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CHANGES-4.3.md b/CHANGES-4.3.md
index 9be7de63f..796efcfff 100644
--- a/CHANGES-4.3.md
+++ b/CHANGES-4.3.md
@@ -17,11 +17,11 @@ File format:
 - Fix rule-engine update behaviour which may initialize actions for disabled rules. [#8849](https://github.com/emqx/emqx/pull/8849)
 - Fix JWT plugin don't support non-integer timestamp claims. [#8862](https://github.com/emqx/emqx/pull/8862)
 - Fix dashboard binding IP address not working. [#8916](https://github.com/emqx/emqx/pull/8916)
-- Fix rule SQL topic matching to null values failed. [#?](https://github.com/emqx/emqx/pull/?)
+- Fix rule SQL topic matching to null values failed. [#8927](https://github.com/emqx/emqx/pull/8927)
   The following SQL should not fail (crash) but return `{"r": false}`:
   `SELECT topic =~ 't' as r FROM "$events/client_connected"`.
   The topic is a null value as there's no such field in event `$events/client_connected`, so it
-  should return false if mathch it to a topic.
+  should return false if match it to a topic.
 
 ## v4.3.19