Fix broken anchors warnings in the docs

Author: tuhaihe

docs/cbdb-linux-compile.md

@@ -18,7 +18,7 @@ Take the following steps to compile and install Apache Cloudberry:
 1. [Clone GitHub repo](#step-1-clone-github-repo).
 2. [Install dependencies](#step-2-install-dependencies).
 3. [Perform prerequisite platform tasks](#step-3-perform-prerequisite-platform-tasks).
-4. [Build Apache Cloudberry](#step-4-build-apache-database).
+4. [Build Apache Cloudberry](#step-4-build-apache-cloudberry).
 5. [Verify the cluster](#step-5-verify-the-cluster).
 
 ## Step 1. Clone GitHub repo

docs/cbdb-op-deploy-guide.md

@@ -13,7 +13,7 @@ The example in this document uses CentOS 7.6 and deploys Apache Cloudberry v1.0.
 1. [Prepare node servers](#step-1-prepare-server-nodes).
 2. [Install the RPM package](#step-2-install-the-rpm-package).
 3. [Configure mutual trust between nodes](#step-3-configure-mutual-trust-between-nodes).
-4. [Initialize the database](#step-4-initialize-cloudberry-database).
+4. [Initialize the database](#step-4-initialize-apache-cloudberry).
 5. [Log into the database](#step-5-log-into-apache-cloudberry).
 
 ## Step 1: Prepare server nodes

docs/functions/index.md

@@ -42,7 +42,7 @@ Apache Cloudberry does not support functions that return a table reference (`ran
 
 ## Built-in functions and operators
 
-The following table lists the categories of built-in functions and operators supported by PostgreSQL. All functions and operators are supported in Apache Cloudberry as in PostgreSQL with the exception of `STABLE` and `VOLATILE` functions, which are subject to the restrictions noted in [Apache Cloudberry Function Types](#topic27). See the [Functions and Operators](https://www.postgresql.org/docs/14/functions.html) section of the PostgreSQL documentation for more information about these built-in functions and operators.
+The following table lists the categories of built-in functions and operators supported by PostgreSQL. All functions and operators are supported in Apache Cloudberry as in PostgreSQL with the exception of `STABLE` and `VOLATILE` functions, which are subject to the restrictions noted in [Apache Cloudberry Function Types](#built-in-functions-and-operators). See the [Functions and Operators](https://www.postgresql.org/docs/14/functions.html) section of the PostgreSQL documentation for more information about these built-in functions and operators.
 
 |Operator/Function Category|VOLATILE Functions|STABLE Functions|Restrictions|
 |--------------------------|------------------|----------------|------------|

docs/functions/json-functions-and-operators.md

@@ -16,7 +16,7 @@ Apache Cloudberry includes built-in functions and operators that create and mani
 - [JSON operators](#json-operators)
 - [JSON creation functions](#json-creation-functions)
 - [JSON aggregate functions](#json-aggregate-functions)
-- [JSON processing functions](#json-processing-functions)
+- [JSON processing functions](#sqljson-path-language)
 
 ### JSON operators
 

docs/sql-stmts/copy.md

@@ -204,7 +204,7 @@ Specifies the newline used in your data files — `LF` (Line feed, 0x0A), `CR` (
 
 **`CSV`**
 
-Selects Comma Separated Value (CSV) mode. See [CSV Format](#section9).
+Selects Comma Separated Value (CSV) mode. See [CSV Format](#file-formats).
 
 **`FILL MISSING FIELDS`**
 

docs/sql-stmts/select.md

@@ -371,11 +371,11 @@ If an existing_window_name is specified, it must refer to an earlier entry in th
 
 **`PARTITION BY`**
 
-The `PARTITION BY` clause organizes the result set into logical groups based on the unique values of the specified expression. The elements of the `PARTITION BY` clause are interpreted in much the same fashion as elements of a [GROUP BY Clause](#groupbyclause), except that they are always simple expressions and never the name or number of an output column. Another difference is that these expressions can contain aggregate function calls, which are not allowed in a regular `GROUP BY` clause. They are allowed here because windowing occurs after grouping and aggregation. When used with window functions, the functions are applied to each partition independently. For example, if you follow `PARTITION BY` with a column name, the result set is partitioned by the distinct values of that column. If omitted, the entire result set is considered one partition.
+The `PARTITION BY` clause organizes the result set into logical groups based on the unique values of the specified expression. The elements of the `PARTITION BY` clause are interpreted in much the same fashion as elements of a [GROUP BY Clause](#the-group-by-clause), except that they are always simple expressions and never the name or number of an output column. Another difference is that these expressions can contain aggregate function calls, which are not allowed in a regular `GROUP BY` clause. They are allowed here because windowing occurs after grouping and aggregation. When used with window functions, the functions are applied to each partition independently. For example, if you follow `PARTITION BY` with a column name, the result set is partitioned by the distinct values of that column. If omitted, the entire result set is considered one partition.
 
 **`ORDER BY`**
 
-Similarly, the elements of the `ORDER BY` list are interpreted in much the same fashion as elements of an [ORDER BY Clause](#orderbyclause), except that the expressions are always taken as simple expressions and never the name or number of an output column.
+Similarly, the elements of the `ORDER BY` list are interpreted in much the same fashion as elements of an [ORDER BY Clause](#the-order-by-clause), except that the expressions are always taken as simple expressions and never the name or number of an output column.
 
 > **Note** The elements of the `ORDER BY` clause define how to sort the rows in each partition of the result set. If omitted, rows are returned in whatever order is most efficient and may vary.
 
@@ -869,7 +869,7 @@ Apache Cloudberry recognizes functional dependency (allowing columns to be omitt
 
 **LIMIT and OFFSET**
 
-The clauses `LIMIT` and `OFFSET` are Apache Cloudberry-specific syntax, also used by MySQL. The SQL:2008 standard has introduced the clauses `OFFSET .. FETCH {FIRST|NEXT} ...` for the same functionality, as shown above in [LIMIT Clause](#limitclause). This syntax is also used by IBM DB2. (Applications for Oracle frequently use a workaround involving the automatically generated `rownum` column, which is not available in Apache Cloudberry, to implement the effects of these clauses.)
+The clauses `LIMIT` and `OFFSET` are Apache Cloudberry-specific syntax, also used by MySQL. The SQL:2008 standard has introduced the clauses `OFFSET .. FETCH {FIRST|NEXT} ...` for the same functionality, as shown above in [LIMIT Clause](#the-limit-clause). This syntax is also used by IBM DB2. (Applications for Oracle frequently use a workaround involving the automatically generated `rownum` column, which is not available in Apache Cloudberry, to implement the effects of these clauses.)
 
 **FOR NO KEY UPDATE, FOR UPDATE, FOR SHARE, and FOR KEY SHARE**
 

docs/sys-utilities/gpaddmirrors.md

@@ -106,7 +106,7 @@ A configuration file containing one line for each mirror segment you want to cre
 <contentID>|<address>|<port>|<data_dir>
 ```
 
-Where `<contentID>` is the segment instance content ID, `<address>` is the hostname or IP address of the segment host, `<port>` is the communication port, and `<data_dir>` is the segment instance data directory. For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specifying-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#using-host-systems-with-multiple-nics).
+Where `<contentID>` is the segment instance content ID, `<address>` is the hostname or IP address of the segment host, `<port>` is the communication port, and `<data_dir>` is the segment instance data directory. For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specify-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#use-host-systems-with-multiple-nics).
 
 **`-l logfile_directory`**
 

docs/sys-utilities/gpexpand.md

@@ -100,7 +100,7 @@ This file can contain hostnames with or without network interfaces specified. Th
 
 > **Note** The Apache Cloudberry segment host naming convention is `sdwN` where `sdw` is a prefix and `N` is an integer. For example, `sdw1`, `sdw2` and so on. For hosts with multiple interfaces, the convention is to append a dash (`-`) and number to the host name. For example, `sdw1-1` and `sdw1-2` are the two interface names for host `sdw1`.
 
-For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specify-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#using-host-systems-with-multiple-nics).
+For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specify-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#use-host-systems-with-multiple-nics).
 
 **`-i | --input input_file`**
 

docs/sys-utilities/gpload.md

@@ -200,7 +200,7 @@ Required. Begins the load specification section. A `GPLOAD` specification must h
 
 Required. Defines the location and the format of the input data to be loaded. `gpload` will start one or more instances of the [gpfdist](/docs/sys-utilities/gpfdist.md) file distribution program on the current host and create the required external table definition(s) in Apache Cloudberry that point to the source data. Note that the host from which you run `gpload` must be accessible over the network by all Apache Cloudberry hosts (coordinator and segments).
 
-SOURCE**
+**`SOURCE`**
 
 Required. The `SOURCE` block of an `INPUT` specification defines the location of a source file. An `INPUT` section can have more than one `SOURCE` block defined. Each `SOURCE` block defined corresponds to one instance of the [gpfdist](/docs/sys-utilities/gpfdist.md) file distribution program that will be started on the local machine. Each `SOURCE` block defined must have a `FILE` specification.
 

docs/sys-utilities/psql.md

@@ -442,7 +442,7 @@ The new query buffer is then re-parsed according to the normal rules of `psql`,
 
 If a line number is specified, `psql` will position the cursor on the specified line of the file or query buffer. Note that if a single all-digits argument is given, `psql` assumes it is a line number, not a file name.
 
-See [Environment](#section17) for information about configuring and customizing your editor.
+See [Environment](#environment) for information about configuring and customizing your editor.
 
 **`\echo text [ ... ]`**