From 28b50215b81f6deb6dc53f5d95b8932f5d81e341 Mon Sep 17 00:00:00 2001
From: seancrasto <103709488+seancrasto@users.noreply.github.com>
Date: Tue, 7 Feb 2023 18:05:50 -0500
Subject: [PATCH] Update job.md

Corrected spelling of specifying.
---
 content/en/docs/concepts/workloads/controllers/job.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md
index a05ad752c3..ecdcb62027 100644
--- a/content/en/docs/concepts/workloads/controllers/job.md
+++ b/content/en/docs/concepts/workloads/controllers/job.md
@@ -794,7 +794,7 @@ These are some requirements and semantics of the API:
   are evaluated in order. Once a rule matches a Pod failure, the remaining rules
   are ignored. When no rule matches the Pod failure, the default
   handling applies.
-- you may want to restrict a rule to a specific container by specifing its name
+- you may want to restrict a rule to a specific container by specifying its name
   in`spec.podFailurePolicy.rules[*].containerName`. When not specified the rule
   applies to all containers. When specified, it should match one the container
   or `initContainer` names in the Pod template.