remove HTML comments

Signed-off-by: DanRoscigno <dan@roscigno.com>

Author: DanRoscigno

docs/en/administration/management/BE_configuration.md

@@ -32,19 +32,6 @@ This error occurs because the web services port of the BE is occupied. Try to mo
 
 This error occurs when you run programs in Java Runtime Environment (JRE). To solve this problem, replace JRE with Java Development Kit (JDK). We recommend that you use Oracle's JDK 1.8 or later.
 
-<!-- ## Why does the error "Failed to Distribute files to node" occur when I deploy StarRocks of Enterprise Edition and configure nodes?
-
-This error occurs when Setuptools versions installed on multiple frontends (FEs) are inconsistent. To solve this problem, you can execute the following command as a root user.
-
-```plaintext
-yum remove python-setuptools
-
-rm /usr/lib/python2.7/site-packages/setuptool* -rf
-
-wget https://bootstrap.pypa.io/ez_setup.py -O - | python
-```
--->
-
 ## Can FE and BE configuration items be modified and then take effect without restarting the cluster?
 
 Yes. Perform the following steps to modify the configurations of [FE and BE parameters](../administration/management/FE_configuration.md):
@@ -116,14 +103,6 @@ Check if OpenSSH Daemon (sshd) is enabled. If not, run the `/etc/init.d/sshd`` s
 
 Run the `netstat -anp |grep port` command to check whether the ports in the `be.conf` file are occupied. If so, replace the occupied port with a free port and then restart the BE.
 
-<!--
-
-## Why does the error "Failed to transport upgrade files to agent host. src:…" occur when I upgrade a cluster of the Enterprise Edition?
-
-This error occurs when the disk space specified in the deployment directory is insufficient. During the cluster upgrade, the StarRocks Manager distributes the binary file of the new version to each node. If the disk space specified in the deployment directory is insufficient, the file cannot be distributed to each node. To solve this problem, add data disks.
-
--->
-
 ## Why does the FE node log on the diagnostics page of StarRocks Manager display "Search log failed." for a newly deployed FE node that is running properly?
 
  By default, StarRocks Manager obtains the path configuration of the newly deployed FE within 30 seconds. This error occurs when the FE starts slowly or does not respond within 30 seconds due to other reasons. Check the log of Manager Web via the path:

docs/en/administration/management/FE_configuration.md

@@ -20,14 +20,10 @@ However, this authentication method still can be seen as a cluster-level safe ac
 
 Unlike instance profile-based authentication, the assumed role-based authentication method supports assuming an AWS IAM role to gain access to your AWS resources. For more information, see [Assuming a role](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-sharing-logs-assume-role.html).
 
-<!--Specifically, you can bind multiple catalogs each to a specific assumed role, so that these catalogs each can connect to specific AWS resources (for example, a specific S3 bucket). This means you can access a different data source by changing the catalog of the current SQL session. Further, if the cluster administrator grants privileges on different catalogs to different users, this will achieve an access control solution just like allowing different users within the same cluster to access different data sources.-->
-
 ### IAM user-based authentication
 
 The IAM user-based authentication method supports using IAM user credentials to gain access to your AWS resources. For more information, see [IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html).
 
-<!--You can bind multiple catalogs each to the credentials (Access Key and Secret Key) of a specific IAM user, so that different users within the same cluster can access different data sources.-->
-
 ## Preparations
 
 First, find the IAM role associated with the EC2 instance on which your StarRocks cluster runs (that role is referred to as the EC2 instance role hereinafter in this topic), and obtain the role's ARN. You will need the EC2 instance role for instance profile-based authentication and need the EC2 instance role and its ARN for assumed role-based authentication.

docs/en/faq/Deploy_faq.md

@@ -309,14 +309,6 @@ Used to enable the streaming pre-aggregations. The default value is `false`, mea
 
 Used for MySQL client compatibility. No practical usage.
 
-<!--
-### enable_collect_table_level_scan_stats (Invisible to users)
-
-This variable is introduced to solve compatibility issues.
-
-Default value: `true`.
--->
-
 ### enable_connector_adaptive_io_tasks
 
 * **Description**: Whether to adaptively adjust the number of concurrent I/O tasks when querying external tables. Default value is `true`. If this feature is not enabled, you can manually set the number of concurrent I/O tasks using the variable `connector_io_tasks_per_scan_operator`.
@@ -401,7 +393,6 @@ Used to enable the strict mode when loading data using the INSERT statement. The
 * **Default**: false, which means the system selects a replica for each query.
 * **Introduced in**: v2.5.6, v3.0.8, v3.1.4, and v3.2.0.
 
-
 ### enable_lake_tablet_internal_parallel
 
 * **Description**: Whether to enable Parallel Scan for Cloud-native tables in a shared-data cluster.

docs/en/integrations/authenticate_to_aws_resources.md

@@ -26,10 +26,6 @@ Returns a DOUBLE value. The formula is as follows, where `n` represents the row
 
 ![corr formula](../../../_assets/corr_formula.png)
 
-<!--$$
-\frac{\sum_{i=1}^{n}((x_i - \bar{x})(y_i - \bar{y}))}{\sqrt{\sum_{i=1}^{n}((x_i - \bar{x})^2) \cdot \sum_{i=1}^{n}((y_i - \bar{y})^2)}}
-$$-->
-
 ## Usage notes
 
 - A data row is counted only when the two columns in this row are non-null values. Otherwise, this data row is eliminated from the result.

docs/en/sql-reference/System_variable.md

@@ -26,10 +26,6 @@ Returns a DOUBLE value. The formula is as follows, where `n` represents the row
 
 ![covar_pop formula](../../../_assets/covar_pop_formula.png)
 
-<!--$$
-\frac{\sum_{i=1}^{n} (x_i - \bar{x})(y_i - \bar{y})}{n}
-$$-->
-
 ## Usage notes
 
 - A data row is counted only when the two columns in this row are non-null values. Otherwise, this data row is eliminated from the result.

docs/en/sql-reference/sql-functions/aggregate-functions/corr.md

@@ -26,10 +26,6 @@ Returns a DOUBLE value. The formula is as follows, where `n` represents the row
 
 ![covar_samp formula](../../../_assets/covar_samp_formula.png)
 
-<!--$$
-\frac{\sum_{i=1}^{n} (x_i - \bar{x})(y_i - \bar{y})}{n-1}
-$$-->
-
 ## Usage notes
 
 - A data row is counted only when the two columns in this row are non-null values. Otherwise, this data row is eliminated from the result.

docs/en/sql-reference/sql-functions/aggregate-functions/covar_pop.md

@@ -29,16 +29,3 @@ SET PROPERTY [FOR 'user'] 'key' = 'value' [, 'key' = 'value']
     SET PROPERTY FOR 'jack' 'max_user_connections' = '1000';
     ```
 
-<!--
-2. Modify cpu_share to 1000 for the user jack
-
-    ```SQL
-    SET PROPERTY FOR 'jack' 'resource.cpu_share' = '1000';
-    ```
-
-3. Modify the weight of the normal level for the user jack
-
-    ```SQL
-    SET PROPERTY FOR 'jack' 'quota.normal' = '400';
-    ```
--->

docs/en/sql-reference/sql-functions/aggregate-functions/covar_samp.md

@@ -225,53 +225,6 @@ FROM par_tbl1
 GROUP BY datekey, k1;
 ```
 
-<!--
-### Align partitions with multiple base tables
-
-![Partitioned Materialized View-3](../../../_assets/partitioned_mv-3.png)
-
-You can create a materialized view whose partitions are aligned with those of multiple base tables, as long as the partitions of the base tables can align with each other, that is, the base tables use the same type of Partitioning Key. You can use JOIN to connect the base tables, and set the Partition Key as the common column. Alternatively, you can connect them with UNION. The base tables with aligned partitions are called reference tables. Data changes in any of the reference tables will trigger the refresh task on the corresponding partitions of the materialized view.
-
-This feature is supported from v3.3 onwards.
-
-```SQL
--- Connect tables with JOIN.
-CREATE MATERIALIZED VIEW par_mv6
-REFRESH ASYNC
-PARTITION BY datekey
-AS SELECT 
-  par_tbl1.datekey,
-  par_tbl1.k1 AS t1k1,
-  par_tbl3.k1 AS t2k1, 
-  sum(par_tbl1.v1) AS SUM1, 
-  sum(par_tbl3.v1) AS SUM2
-FROM par_tbl1 JOIN par_tbl3 ON par_tbl1.datekey = par_tbl3.datekey_new
-GROUP BY par_tbl1.datekey, t1k1, t2k1;
-
--- Connect tables with UNION.
-CREATE MATERIALIZED VIEW par_mv7
-REFRESH ASYNC
-PARTITION BY datekey
-AS SELECT 
-  par_tbl1.datekey,
-  par_tbl1.k1 AS t1k1,
-  sum(par_tbl1.v1) AS SUM1
-FROM par_tbl1
-GROUP BY 
-  par_tbl1.datekey,
-  par_tbl1.k1
-UNION ALL
-SELECT
-  par_tbl3.datekey_new,
-  par_tbl3.k1 AS t2k1, 
-  sum(par_tbl3.v1) AS SUM2
-FROM par_tbl3
-GROUP BY 
-  par_tbl3.datekey_new,
-  par_tbl3.k1;
-```
--->
-
 ### Achieve incremental refresh and transparent rewrite
 
 You can create a partitioned materialized view that refreshes by partitions to achieve incremental updates of the materialized view and transparent rewrite of queries with partial data materialization.