diff --git a/doc/src/sgml/ref/create_external_table.sgml b/doc/src/sgml/ref/create_external_table.sgml
index d18a8734358..798b9a077cd 100755
--- a/doc/src/sgml/ref/create_external_table.sgml
+++ b/doc/src/sgml/ref/create_external_table.sgml
@@ -145,7 +145,7 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
You may specify multiple external data sources or URIs (uniform resource identifiers)
- with the LOCATION clause � up to the number of primary segment instances
+ with the LOCATION clause up to the number of primary segment instances
in your Apache Cloudberry array. Each URI points to an external data file or other data
source. These URIs do not need to exist prior to defining an external table (CREATE EXTERNAL TABLE
does not validate the URIs specified). However you will get an error if they cannot be found
@@ -159,7 +159,7 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
- gpfdist � If using the gpfdist:// protocol, you must have the
+ gpfdist If using the gpfdist:// protocol, you must have the
Cloudberry file distribution program (gpfdist) running on the host where the external
data files reside. This program points to a given directory on the file host and
serves external data files to all Apache Cloudberry segments in parallel.
@@ -169,7 +169,7 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
- file � If using the file:// protocol the external data file(s)
+ file If using the file:// protocol the external data file(s)
must reside on a segment host in a location accessible by the Cloudberry super user
(gpadmin). The number of URIs specified corresponds to the number of segment
instances that will work in parallel to access the external table. So for
@@ -184,7 +184,7 @@ CREATE WRITABLE EXTERNAL WEB [TEMPORARY | TEMP] TABLE table_name
- http � If using the http:// protocol the external data file(s)
+ http If using the http:// protocol the external data file(s)
must reside on a web server that is accessible by the Cloudberry segment hosts.
The number of URIs specified corresponds to the number of segment instances
that will work in parallel to access the external table. So for example,