Updated wording for HTTP Proxies

As per @zroubalik's suggestion.
kedacore · Mar 28, 2022 · 3212f08 · 3212f08
1 parent 0bbcc78
commit 3212f08
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/content/docs/2.7/operate/cluster.md b/content/docs/2.7/operate/cluster.md
@@ -67,7 +67,7 @@ All applicable scalers will use this timeout. Setting a per-scaler timeout is cu
 
 ## HTTP Proxies
 
-Some scalers issue HTTP requests to external servers (i.e. cloud services). As certain companies require external servers to be accessed by proxy servers, adding the relevant environment variables to the KEDA Operator deployment (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, etc.) would allow the scaler to connect via the desired proxy.
+Some scalers issue HTTP requests to external servers (i.e. cloud services). As certain companies require external servers to be accessed by proxy servers, adding the relevant environment variables to both the KEDA Operator, and KEDA Metrics Server deployments (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, etc.) would allow the scaler to connect via the desired proxy.
 
 ```yaml
 - env: