PR review feedback

Signed-off-by: Tom Kerkhove <[email protected]>

Author: tomkerkhove

articles/api-management/how-to-self-hosted-gateway-on-kubernetes-in-production.md

@@ -38,25 +38,24 @@ While we provide [guidance on the minimum number of replicas](#number-of-replica
 
 There are two ways to autoscale the self-hosted gateway horizontally:
 
-- Autoscale based on resource usage (CPU & Memory)
+- Autoscale based on resource usage (CPU and memory)
 - Autoscale based on the number of requests per second
 
 This is possible through native Kubernetes functionality, or by using [Kubernetes Event-driven Autoscaling (KEDA)](https://keda.sh/). KEDA is a CNCF Incubation project that strives to make application autoscaling simple.
 
 > [!NOTE]
 > KEDA is an open-source technology that is not supported by Azure support and needs to be operated by customers.
 
-### Resource-based Autoscaling
+### Resource-based autoscaling
 
-Kubernetes allows you to autoscale the self-hosted gateway based on resource usage by using a [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). It allows you to [define CPU & memory thresholds](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-resource-metrics), and the number of replicas to scale out or in.
+Kubernetes allows you to autoscale the self-hosted gateway based on resource usage by using a [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). It allows you to [define CPU and memory thresholds](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-resource-metrics), and the number of replicas to scale out or in.
 
 An alternative is to use Kubernetes Event-driven Autoscaling (KEDA) allowing you to scale workloads based on a [variety of scalers](https://keda.sh/docs/latest/scalers/), including CPU and memory.
-We recommend using KEDA to scale the self-hosted gateway horizontally, if you are already using KEDA to scale other workloads as a unified app autoscaler. If that is not the case, then we strongly suggest to rely on the native Kubernetes functionality through Horizontal Pod Autoscaler.
 
 > [!TIP]
 > If you are already using KEDA to scale other workloads, we recommend using KEDA as a unified app autoscaler. If that is not the case, then we strongly suggest to rely on the native Kubernetes functionality through Horizontal Pod Autoscaler.
 
-### Traffic-based Autoscaling
+### Traffic-based autoscaling
 
 Kubernetes does not provide an out-of-the-box mechanism for traffic-based autoscaling.