docs: adjust inverted-index wording for high-cardinality columns (#2450)

Author: fengys1996

docs/user-guide/manage-data/data-index.md

@@ -39,7 +39,7 @@ CREATE TABLE monitoring_data (
 );
 ```
 
-However, when you have a large number of unique tag values (Cartesian product among all columns indexed by inverted index), the inverted index may not be the best choice due to the overhead of maintaining the index. It may bring high memory consumption and large index size. In this case, you may consider using the skipping index.
+However, when a column has very high cardinality, the inverted index may not be the best choice due to the overhead of maintaining the index. It may bring high memory consumption and large index size. In this case, you may consider using the skipping index.
 
 ### Skipping Index
 

i18n/zh/docusaurus-plugin-content-docs/current/user-guide/manage-data/data-index.md

@@ -39,7 +39,7 @@ CREATE TABLE monitoring_data (
 );
 ```
 
-需要注意的是，当标签值的组合数（即倒排索引覆盖的列的笛卡尔积）非常大时，倒排索引可能会带来较高的维护成本，导致内存占用增加和索引体积膨胀。这种情况下，建议考虑使用跳数索引作为替代方案。
+需要注意的是，当列的基数非常大时，倒排索引可能会带来较高的维护成本，导致内存占用增加和索引体积膨胀。这种情况下，建议考虑使用跳数索引作为替代方案。
 
 ### 跳数索引
 

i18n/zh/docusaurus-plugin-content-docs/version-1.0/user-guide/manage-data/data-index.md

@@ -39,7 +39,7 @@ CREATE TABLE monitoring_data (
 );
 ```
 
-需要注意的是，当标签值的组合数（即倒排索引覆盖的列的笛卡尔积）非常大时，倒排索引可能会带来较高的维护成本，导致内存占用增加和索引体积膨胀。这种情况下，建议考虑使用跳数索引作为替代方案。
+需要注意的是，当列的基数非常大时，倒排索引可能会带来较高的维护成本，导致内存占用增加和索引体积膨胀。这种情况下，建议考虑使用跳数索引作为替代方案。
 
 ### 跳数索引
 

versioned_docs/version-1.0/user-guide/manage-data/data-index.md

@@ -39,7 +39,7 @@ CREATE TABLE monitoring_data (
 );
 ```
 
-However, when you have a large number of unique tag values (Cartesian product among all columns indexed by inverted index), the inverted index may not be the best choice due to the overhead of maintaining the index. It may bring high memory consumption and large index size. In this case, you may consider using the skipping index.
+However, when a column has very high cardinality, the inverted index may not be the best choice due to the overhead of maintaining the index. It may bring high memory consumption and large index size. In this case, you may consider using the skipping index.
 
 ### Skipping Index