diff --git a/rfcs/0052-extensible-udt/0052-extensible-udt.md b/rfcs/0052-extensible-udt/0052-extensible-udt.md
index 1cf2bfee..a54e460e 100644
--- a/rfcs/0052-extensible-udt/0052-extensible-udt.md
+++ b/rfcs/0052-extensible-udt/0052-extensible-udt.md
@@ -103,7 +103,7 @@ actual `raw_extension_data` (`ScriptVec`) structure data will be included in a
 witness field `input_type` or `output_type` contained in the current
 transaction. We will explain this part below. Choosing `input_type` or
 `output_type` depends on whether the type script is running on input or output
-cells. Under a lot of scenarios, it is `input_type`. But in the example “Owner
+cells. Under a lot of scenarios, it is `input_type`. But in the following example “Owner
 Mode Without Consuming Cell”, we can see it’s possible on `output_type`.
 
 ### xUDT Witness