Apply suggestions from code review

pingcap · Feb 22, 2024 · 8ed5f17 · 8ed5f17
1 parent e5f6c08
commit 8ed5f17
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 8 deletions.
diff --git a/faq/sql-faq.md b/faq/sql-faq.md
@@ -207,9 +207,9 @@ TiDB supports changing the priority on a [global](/system-variables.md#tidb_forc
 
 - `DELAYED`: this statement has normal priority and is the same as the `NO_PRIORITY` setting for `tidb_force_priority`.
 
-> **NOTE:**
+> **Note:**
 >
-> TiDB started supporting the feature [Resource Control](/tidb-resource-control.md) in v6.6.0. Users can utilize this feature to execute SQLs with different priorities under different resource groups. By configuring proper quotas and priorities for these resource groups, users can gain better scheduling control for SQLs with different priorities. When resource control is enabled, statement priority will no longer take effect. We recommend using [Resource Control](/tidb-resource-control.md) to manage the resource usage between different SQLs.
+> Starting from v6.6.0, TiDB supports [Resource Control](/tidb-resource-control.md). You can use this feature to execute SQL statements with different priorities in different resource groups. By configuring proper quotas and priorities for these resource groups, you can gain better scheduling control for SQL statements with different priorities. When resource control is enabled, statement priority will no longer take effect. It is recommended that you use [Resource Control](/tidb-resource-control.md) to manage resource usage for different SQL statements.
 
 You can combine the above two parameters with the DML of TiDB to use them. For example:
 

diff --git a/system-variables.md b/system-variables.md
@@ -2451,9 +2451,9 @@ For a system upgraded to v5.0 from an earlier version, if you have not modified
 - This variable is used to change the default priority for statements executed on a TiDB server. A use case is to ensure that a particular user that is performing OLAP queries receives lower priority than users performing OLTP queries.
 - The default value `NO_PRIORITY` means that the priority for statements is not forced to change.
 
-> **NOTE:**
+> **Note:**
 >
-> TiDB started supporting the feature [Resource Control](/tidb-resource-control.md) in v6.6.0. Users can utilize this feature to execute SQLs with different priorities under different resource groups. By configuring proper quotas and priorities for these resource groups, users can gain better scheduling control for SQLs with different priorities. When resource control is enabled, statement priority will no longer take effect. We recommend using [Resource Control](/tidb-resource-control.md) to manage the resource usage between different SQLs.
+> Starting from v6.6.0, TiDB supports [Resource Control](/tidb-resource-control.md). You can use this feature to execute SQL statements with different priorities in different resource groups. By configuring proper quotas and priorities for these resource groups, you can gain better scheduling control for SQL statements with different priorities. When resource control is enabled, statement priority will no longer take effect. It is recommended that you use [Resource Control](/tidb-resource-control.md) to manage resource usage for different SQL statements.
 
 ### tidb_gc_concurrency <span class="version-mark">New in v5.0</span>
 

diff --git a/tidb-configuration-file.md b/tidb-configuration-file.md
@@ -529,9 +529,9 @@ Configuration items related to performance.
 - Value options: The default value `NO_PRIORITY` means that the priority for statements is not forced to change. Other options are `LOW_PRIORITY`, `DELAYED`, and `HIGH_PRIORITY` in ascending order.
 - Since v6.1.0, the priority for all statements is determined by the TiDB configuration item [`instance.tidb_force_priority`](/tidb-configuration-file.md#tidb_force_priority) or the system variable [`tidb_force_priority`](/system-variables.md#tidb_force_priority). `force-priority` still takes effect. But if `force-priority` and `instance.tidb_force_priority` are set at the same time, the latter takes effect.
 
-> **NOTE:**
+> **Note:**
 >
-> TiDB started supporting the feature [Resource Control](/tidb-resource-control.md) in v6.6.0. Users can utilize this feature to execute SQLs with different priorities under different resource groups. By configuring proper quotas and priorities for these resource groups, users can gain better scheduling control for SQLs with different priorities. When resource control is enabled, statement priority will no longer take effect. We recommend using [Resource Control](/tidb-resource-control.md) to manage the resource usage between different SQLs.
+> Starting from v6.6.0, TiDB supports [Resource Control](/tidb-resource-control.md). You can use this feature to execute SQL statements with different priorities in different resource groups. By configuring proper quotas and priorities for these resource groups, you can gain better scheduling control for SQL statements with different priorities. When resource control is enabled, statement priority will no longer take effect. It is recommended that you use [Resource Control](/tidb-resource-control.md) to manage resource usage for different SQL statements.
 
 ### `distinct-agg-push-down`
 
@@ -878,9 +878,9 @@ Configuration items related to read isolation.
 - The default value `NO_PRIORITY` means that the priority for statements is not forced to change. Other options are `LOW_PRIORITY`, `DELAYED`, and `HIGH_PRIORITY` in ascending order.
 - Before v6.1.0, this configuration is set by `force-priority`.
 
-> **NOTE:**
+> **Note:**
 >
-> TiDB started supporting the feature [Resource Control](/tidb-resource-control.md) in v6.6.0. Users can utilize this feature to execute SQLs with different priorities under different resource groups. By configuring proper quotas and priorities for these resource groups, users can gain better scheduling control for SQLs with different priorities. When resource control is enabled, statement priority will no longer take effect. We recommend using [Resource Control](/tidb-resource-control.md) to manage the resource usage between different SQLs.
+> Starting from v6.6.0, TiDB supports [Resource Control](/tidb-resource-control.md). You can use this feature to execute SQL statements with different priorities in different resource groups. By configuring proper quotas and priorities for these resource groups, you can gain better scheduling control for SQL statements with different priorities. When resource control is enabled, statement priority will no longer take effect. It is recommended that you use [Resource Control](/tidb-resource-control.md) to manage resource usage for different SQL statements.
 
 ### `max_connections`