From a47d4b7b6fb0c3bc5853183781e9ff1bb92139df Mon Sep 17 00:00:00 2001 From: David E Worth Date: Tue, 12 Nov 2024 09:12:48 -0600 Subject: [PATCH] fix(docs): replace `it"s` with `it is` (#3227) Signed-off-by: David Worth --- site/src/content/docs/ref/actions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/src/content/docs/ref/actions.mdx b/site/src/content/docs/ref/actions.mdx index c65cd75df1..80549174eb 100644 --- a/site/src/content/docs/ref/actions.mdx +++ b/site/src/content/docs/ref/actions.mdx @@ -69,7 +69,7 @@ Any binaries you execute in your `cmd` actions must exist on the machine they ar ### `wait` Action Configuration -The `wait` action temporarily halts the component stage it"s initiated in, either until the specified condition is satisfied or until the maxTotalSeconds time limit is exceeded (which, by default, is set to 5 minutes). To define `wait` parameters, execute the `wait` key; it"s essential to note that _you cannot use `cmd` and `wait` in the same action_. Essentially, a `wait` action is _yaml sugar_ for a call to `./zarf tools wait-for`. +The `wait` action temporarily halts the component stage it is initiated in, either until the specified condition is satisfied or until the maxTotalSeconds time limit is exceeded (which, by default, is set to 5 minutes). To define `wait` parameters, execute the `wait` key; it is essential to note that _you cannot use `cmd` and `wait` in the same action_. Essentially, a `wait` action is _yaml sugar_ for a call to `./zarf tools wait-for`. Within each of the `action` lists (`before`, `after`, `onSuccess`, and `onFailure`), the following action configurations are available: