From 70eaaa1f3bf74b75be8057c5a8e25e0c0ab183dd Mon Sep 17 00:00:00 2001
From: Mauren Berti <698465+stormqueen1990@users.noreply.github.com>
Date: Wed, 19 Apr 2023 13:39:21 -0400
Subject: [PATCH] Change wording on scale-to-zero

Change wording to make it clear it's the workloads that are currently scaled to zero that won't be caught by the command.
---
 .../pod-security-standards.md                                   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md
index 13f97c5f360..b51d7c9759a 100644
--- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md
+++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md
@@ -25,7 +25,7 @@ You must perform the following steps _while still in Kubernetes v1.24_:
 1. Map your active PSPs to Pod Security Standards:
     1. See which PSPs are still active in your cluster:
        :::caution
-       This strategy may miss workloads that aren't currently running, such as CronJobs, workloads that scale to zero, or workloads that haven't rolled out yet.
+       This strategy may miss workloads that aren't currently running, such as CronJobs, workloads currently scaled to zero, or workloads that haven't rolled out yet.
        :::
        
        ```shell