From 4ef3e3a7f37486fd7f4e4ac0c16953ae7bffd3be Mon Sep 17 00:00:00 2001
From: Patryk Bundyra <73306396+PBundyra@users.noreply.github.com>
Date: Thu, 28 Mar 2024 09:47:34 +0100
Subject: [PATCH] Update
 site/content/en/docs/admission-check-controllers/provisioning.md

Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
---
 .../content/en/docs/admission-check-controllers/provisioning.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/content/en/docs/admission-check-controllers/provisioning.md b/site/content/en/docs/admission-check-controllers/provisioning.md
index 52fb2b4b97..b8c350e811 100644
--- a/site/content/en/docs/admission-check-controllers/provisioning.md
+++ b/site/content/en/docs/admission-check-controllers/provisioning.md
@@ -23,7 +23,7 @@ There are two ways to configure ProvisioningRequest sent for your Jobs.
 
 - **ProvisioningRequestConfig:** This configuration in the AdmissionCheck applies to all the jobs that go through this check.
 It enables you to set `provisioningClassName`, `managedResources`, and `parameters`
-- **Job annotation**: This configuration applies only to a specific job. It enables you to set `parameters`, and if both the annotation and the ProvisioningRequestConfig refer same one, annotation overrides it.
+- **Job annotation**: This configuration enables you to set `parameters` to a specific job. If both the annotation and the ProvisioningRequestConfig refer to the same parameter, the annotation value takes precedence.
 
 ### ProvisioningRequestConfig
 A `ProvisioningRequestConfig` looks like the following: