fuzzify-the-performance-descending-degree-for-adding-index

docs-2.0/2.quick-start/4.nebula-graph-crud.md

@@ -485,7 +485,7 @@ Users can add indexes to tags and edge types with the [CREATE INDEX](../3.ngql-g
 
 !!! caution "Must-read for using indexes"
 
-    Both `MATCH` and `LOOKUP` statements depend on the indexes. But indexes can dramatically reduce the write performance (as much as 90% or even more). **DO NOT** use indexes in production environments unless you are fully aware of their influences on your service.
+    Both `MATCH` and `LOOKUP` statements depend on the indexes. But indexes can dramatically reduce the write performance<!-- (as much as 90% or even more)-->. **DO NOT** use indexes in production environments unless you are fully aware of their influences on your service.
 
     Users **MUST** rebuild indexes for pre-existing data. Otherwise, the pre-existing data cannot be indexed and therefore cannot be returned in `MATCH` or `LOOKUP` statements. For more information, see [REBUILD INDEX](../3.ngql-guide/14.native-index-statements/4.rebuild-native-index.md).
 

docs-2.0/3.ngql-guide/14.native-index-statements/1.create-native-index.md

@@ -32,7 +32,7 @@ Although the same results can be obtained by using alternative indexes for queri
 
 !!! caution
 
-    Indexes can dramatically reduce the write performance. The performance reduction can be as much as 90% or even more. **DO NOT** use indexes in production environments unless you are fully aware of their influences on your service.
+    Indexes can dramatically reduce the write performance. The performance can be greatly reduced<!-- as much as 90% or even more-->. **DO NOT** use indexes in production environments unless you are fully aware of their influences on your service.
 
     Indexes cannot make queries faster. It can only locate a vertex or an edge according to properties or count the number of vertices or edges.
 

docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md

@@ -18,7 +18,7 @@ This topic applies to native nGQL only.
 
 ## Precautions
 
-- Correct use of indexes can speed up queries, but indexes can dramatically reduce the write performance. The performance reduction can be 90% or even more. **DO NOT** use indexes in production environments unless you are fully aware of their influences on your service.
+- Correct use of indexes can speed up queries, but indexes can dramatically reduce the write performance. The performance can be greatly reduced<!-- as much as 90% or even more-->. **DO NOT** use indexes in production environments unless you are fully aware of their influences on your service.
 
 - If the specified property is not indexed when using the `LOOKUP` statement, Nebula Graph randomly selects one of the available indexes.
 

docs-2.0/8.service-tuning/2.graph-modeling.md

@@ -145,7 +145,7 @@ Put a group of properties that are on the same level into the same tag. Differen
 
 ### Use indexes correctly
 
-Using property indexes helps find VIDs through properties, but can lead to performance reduction by 90% or even more. Only use an index when you need to find vertices or edges through their properties.
+Using property indexes helps find VIDs through properties, but can lead to great performance reduction<!-- by 90% or even more-->. Only use an index when you need to find vertices or edges through their properties.
 
 ### Design VIDs appropriately