Merge pull request #36607 from NitishKumar06/Nitish/36393issue

Avoid confusing term in API Priority and Fairness concept

Author: k8s-ci-robot

content/en/docs/concepts/cluster-administration/flow-control.md

@@ -172,7 +172,7 @@ server.
 
 The flow control API involves two kinds of resources.
 [PriorityLevelConfigurations](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#prioritylevelconfiguration-v1beta2-flowcontrol-apiserver-k8s-io)
-define the available isolation classes, the share of the available concurrency
+define the available priority levels, the share of the available concurrency
 budget that each can handle, and allow for fine-tuning queuing behavior.
 [FlowSchemas](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#flowschema-v1beta2-flowcontrol-apiserver-k8s-io)
 are used to classify individual inbound requests, matching each to a
@@ -182,7 +182,7 @@ semantics.
 
 ### PriorityLevelConfiguration
 
-A PriorityLevelConfiguration represents a single isolation class. Each
+A PriorityLevelConfiguration represents a single priority level. Each
 PriorityLevelConfiguration has an independent limit on the number of outstanding
 requests, and limitations on the number of queued requests.