Update Docusaurus to latest version(3.9.2)

Author: heywalter

docs/appendix/enhanced-js.md

@@ -2,7 +2,7 @@
 
 Enhanced JS nodes allow you to utilize all built-in functions for external calls, such as networking and database operations. If your requirement is solely to process and operate on data records, it is recommended to use [standard JS nodes](standard-js.md).
 
-For detailed instructions on how to use enhanced JS nodes and explore various scenarios, please refer to the documentation and resources available for [JS processing node](../data-transformation/process-node.md#js-process).
+For detailed instructions on how to use enhanced JS nodes and explore various scenarios, please refer to the documentation and resources available for [JS processing node](../data-transformation/process-node.md#js-processing).
 
 :::tip
 

docs/appendix/standard-js.md

@@ -3,7 +3,7 @@
 
 Standard JS nodes can only process and operate on data records. If you require the usage of system built-in functions for external calls, such as networking or database operations, you can utilize [enhanced JS nodes](enhanced-js.md).
 
-For information on how to use and scenarios, see [JS processing node](../data-transformation/process-node.md#js-process).
+For information on how to use and scenarios, see [JS processing node](../data-transformation/process-node.md#js-processing).
 
 ## DateUtil
 

docs/case-practices/best-practice/alert-via-qqmail.md

@@ -62,7 +62,7 @@ The email authorization code is a special password used by QQ Mail to log into t
    ![SMTP Service Settings](../../images/qqmail_smtp_settings.png)
 
    * **SMTP Service Account**: Enter your QQ email address.
-   * **SMTP Service Password**: Enter the authorization code you obtained in [Step One](#mail-code).
+   * **SMTP Service Password**: Enter the authorization code you obtained in [Step One](#step-one-obtain-email-authorization-code).
    * **Encryption Method**: Select **SSL** to ensure security.
    * **SMTP Service Host**: Enter **smtp.qq.com**, the SMTP server for sending emails from QQ Mail.
    * **SMTP Service Port**: Enter **465** or **587**.

docs/case-practices/best-practice/raw-logs-solution.md

@@ -11,7 +11,7 @@ To enhance the efficiency of capturing data changes, TapData supports not only u
 * **Operating System**: Linux 64 or Windows 64 platforms.
 * **Storage**: Supported file systems include ext4, btrfs, zfs, xfs, sshfs; supported database block sizes are 2k, 4k, 8k, 16k, 32k.
 * **Port Requirements**: Some server ports must be open for service communication, including: default data transfer port: **8203**, web management default port: **8303**, raw log service port: **8190**.
-* **Permission**: The operating system user running the raw log plugin must have read access to redo log files; in addition to the permissions required for the source database as per the [Oracle Preparation Work](../../connectors/on-prem-databases/oracle.md#source) and enabling archive logs, additional permissions must be granted to simulate Oracle's data information structure and processes to cache part of Oracle Schema information to support the parsing of redo logs.
+* **Permission**: The operating system user running the raw log plugin must have read access to redo log files; in addition to the permissions required for the source database as per the [Oracle Preparation Work](../../connectors/on-prem-databases/oracle.md#as-a-source-database) and enabling archive logs, additional permissions must be granted to simulate Oracle's data information structure and processes to cache part of Oracle Schema information to support the parsing of redo logs.
 
 ```sql
 -- Replace <DSTUSER> with the actual username

docs/case-practices/pipeline-tutorial/mysql-to-bigquery.md

@@ -85,7 +85,7 @@ For more information, See [Management Tasks](../../data-transformation/manage-ta
 
 
 
-## <span id="faq"> FAQ</span>
+## FAQ
 
 * Q: Why does Agent's machine require access to Google Cloud Services?
 

docs/connectors/on-prem-databases/tidb.md

@@ -165,6 +165,6 @@ GRANT SELECT, INSERT, UPDATE, DELETE, ALTER, CREATE, DROP ON *.* TO 'username';
 
   1. Extract the downloaded file, then navigate to the extracted directory and run the `make` command to compile.
 
-  2. Locate the generated **cdc** binary file and place it in the **{tapData-dir}/run-resource/ti-db/tool** directory on the TapData engine machine (replace if necessary).
+  2. Locate the generated **cdc** binary file and place it in the **\{tapData-dir\}/run-resource/ti-db/tool** directory on the TapData engine machine (replace if necessary).
 
   3. Use the `chmod` command to grant read, write, and execute permissions to the files in this directory.

docs/connectors/others/dummy.md

@@ -4,7 +4,8 @@
 
 Dummy is a data source that generates test data. This article describes how to add Dummy data sources to TapData Cloud.
 
-<details><summary>Supported Generated Field Types</summary>
+<details>
+<summary>Supported Generated Field Types</summary>
 
 | Type                      | Description            | Parameters                                                    |
 | ------------------------- | ---------------------- | ------------------------------------------------------------ |
@@ -58,4 +59,3 @@ Dummy is a data source that generates test data. This article describes how to a
    If the connection test fails, follow the prompts on the page to fix it.
 
    :::
-

docs/connectors/pre-check.md

@@ -16,22 +16,22 @@ After the data replication/development task configuration is completed, execute
 | -------------------------- | ------------------------------------------------------------ |
 | Task Sync Type Check       | 【ERROR】【2023-01-01 00:00:00】【Task Sync Type Check】【Node-Source】The sync type (Full) of this node does not match the task sync type (Full + Incremental), the task cannot start normally, please check the relevant configuration. |
 | Default Timezone Check     | 【WARN】【2023-01-01 00:00:00】【Default Timezone Check】The default timezone connected by the source node (Node-Source) is inconsistent with the default timezone connected by the target node (Node-Target), which may cause inconsistency in synchronized data. |
-| Task Model Inference Check | 【ERROR】【2023-01-01 00:00:00】【Task Model Inference Check】Task configuration model inference failed, the task cannot start normally, please check the relevant issues. <br /> { <br />Node Name 1: Table Name 1: Field Name 1; <br />Node Name 2: Table Name 2: Field Name 2 <br />} |
+| Task Model Inference Check | 【ERROR】【2023-01-01 00:00:00】【Task Model Inference Check】Task configuration model inference failed, the task cannot start normally, please check the relevant issues. <br /> &#123; <br />Node Name 1: Table Name 1: Field Name 1; <br />Node Name 2: Table Name 2: Field Name 2 <br />&#125; |
 
 ## Source Node Check
 
 | Check Item                     | Log Example                                                  |
 | ------------------------------ | ------------------------------------------------------------ |
-| Source Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Source Connection Status Check】【Node-Source】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. { Data source login permission check failed: Wrong username or password } |
-| Source Model Load Check        | 【ERROR】【2023-01-01 00:00:00】【Source Model Load Check】【Node-Source】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. <br />{ Table Name 1; <br />Table Name 2 <br />} |
+| Source Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Source Connection Status Check】【Node-Source】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. &#123; Data source login permission check failed: Wrong username or password &#125; |
+| Source Model Load Check        | 【ERROR】【2023-01-01 00:00:00】【Source Model Load Check】【Node-Source】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. <br />&#123; Table Name 1; <br />Table Name 2 <br />&#125; |
 | Source Type Mapping Check      | 【WARN】【2023-01-01 00:00:00】【Source Type Mapping Check】【Node-Source】【Personinfo】【id】The data type of this field is temporarily unsupported, and will be ignored during data reading. |
 
 ## Target Node Check
 
 | Check Item                     | Log Example                                                  |
 | ------------------------------ | ------------------------------------------------------------ |
-| Target Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Target Connection Status Check】【Node-Target】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. { Data source login permission check failed: Wrong username or password } |
-| Target Model Load Check        | 【ERROR】【2023-01-01 00:00:00】【Target Model Load Check】【Node-Target】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. { Table Name 1; Table Name 2 } |
+| Target Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Target Connection Status Check】【Node-Target】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. &#123; Data source login permission check failed: Wrong username or password &#125; |
+| Target Model Load Check        | 【ERROR】【2023-01-01 00:00:00】【Target Model Load Check】【Node-Target】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. &#123; Table Name 1; Table Name 2 &#125; |
 | Target Type Mapping Failure    | 【WARN】【2023-01-01 00:00:00】【Target Type Mapping Check】【Node-Target】【Personinfo】【id】The data type of this field is temporarily unsupported, and will be ignored during data writing. |
 | Target Type Mapping Warning    | 【WARN】【2023-01-01 00:00:00】【Source Type Mapping Check】【Node-Target】【Personinfo】【pic】The target data type mapped by this field is a system-guessed result, which may be biased. Please check and confirm whether it meets the expectations, and adjust accordingly. |
 
@@ -41,4 +41,4 @@ After the data replication/development task configuration is completed, execute
 | ----------- | -------------------------------- | ------------------------------------------------------------ |
 | Source Node | MariaDB Timezone Check           | 【WARN】【2023-01-01 00:00:00】【MariaDB Timezone Check】【Node-MariaDB】The timezone setting in the MariaDB connection configuration only takes effect in the Full phase and is invalid in the Incremental phase. |
 | Target Node | Oracle NOT NULL Constraint Check | 【WARN】【2023-01-01 00:00:00】【Oracle NOT NULL Constraint Check】【Node-Oracle】【Personinfo】【id】When writing NOT NULL fields with Oracle data source as the target, "" cannot be processed. |
-| Target Node | CK Primary Key Type Check        | 【WARN】【2023-01-01 00:00:00】【CK Primary Key Type Check】【Node-CK】【Personinfo】When using ClickHouse data source as the target and the primary key data type is floating-point, this data table does not support the processing of update delete events. |
+| Target Node | CK Primary Key Type Check        | 【WARN】【2023-01-01 00:00:00】【CK Primary Key Type Check】【Node-CK】【Personinfo】When using ClickHouse data source as the target and the primary key data type is floating-point, this data table does not support the processing of update delete events. |

docs/data-transformation/create-views/overview.md

@@ -23,7 +23,8 @@ import TapDataAnimation from '@site/src/components/Animation/TapDataAnimation';
 <TapDataAnimation />
 
 
-<details><summary>Ways to Add Related Fields</summary>
+<details>
+<summary>Ways to Add Related Fields</summary>
 
 When designing your Incremental Materialized View, you can choose how data from related tables is included in your main record. TapData lets you customize this structure to match your analysis needs and downstream use cases:
 

docs/data-transformation/create-views/using-tapflow.md

@@ -71,7 +71,8 @@ You can build the real-time, incremental materialized view directly in **TapShel
    )
    ```
 
-   <details><summary>Understanding type and path in .lookup()</summary>
+   <details>
+   <summary>Understanding type and path in .lookup()</summary>
    These parameters control **how** related data is merged:
 
    - **type="object"** – embeds the joined record as a nested document at `path`. Ideal for one-to-one enrichments like adding user profiles inside orders.
@@ -247,4 +248,3 @@ This structure is analysis-ready, API-friendly, and tailored for real-time use.
 - **Publish the view as an API** so other teams or systems can consume fresh, structured order data via REST or GraphQL.
 
 
-