From 7710e2edea542ed3bd3aa3755bf73dc6a910412f Mon Sep 17 00:00:00 2001
From: Abhiram <22r11a0561@gcet.edu.in>
Date: Wed, 11 Mar 2026 00:37:06 +0530
Subject: [PATCH] fix(docs): correct "a unschedulable" to "an unschedulable"
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Fixed article grammar error: "a unschedulable" →
"an unschedulable" on the Kubernetes docs page.

Part of GSoC 2026 preparation contributions.
---
 docs/scaling/remote-tasks/kubernetes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/scaling/remote-tasks/kubernetes.md b/docs/scaling/remote-tasks/kubernetes.md
index b9ae91b4..b7f30aa2 100644
--- a/docs/scaling/remote-tasks/kubernetes.md
+++ b/docs/scaling/remote-tasks/kubernetes.md
@@ -19,7 +19,7 @@ Here are the current defaults for different resource types:
 * `disk`: 10240 \(10GB\)
 
 When setting `@resources`, keep in mind the configuration of your Kubernetes cluster.
-Your pod will be stuck in an unschedulable state if Kubernetes is unable to provision
+Your pod will be stuck in an an unschedulable state if Kubernetes is unable to provision
 the requested resources. Additionally, as a good measure, don't request more resources
 than what your workflow actually needs. On the other hand, never optimize resources
 prematurely.