From b541bd2fec982e43c70a117723549272f214bda6 Mon Sep 17 00:00:00 2001
From: avinashsoni9829 <45571070+avinashsoni9829@users.noreply.github.com>
Date: Tue, 9 Jan 2024 11:03:16 +0530
Subject: [PATCH] Update Semaphore.java

improved grammaticall explaination
---
 src/share/classes/java/util/concurrent/Semaphore.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/share/classes/java/util/concurrent/Semaphore.java b/src/share/classes/java/util/concurrent/Semaphore.java
index c144b492db..2411fcf7f3 100644
--- a/src/share/classes/java/util/concurrent/Semaphore.java
+++ b/src/share/classes/java/util/concurrent/Semaphore.java
@@ -46,7 +46,7 @@
  * However, no actual permit objects are used; the {@code Semaphore} just
  * keeps a count of the number available and acts accordingly.
  *
- * <p>Semaphores are often used to restrict the number of threads than can
+ * <p>Semaphores are often used to restrict the number of threads that can
  * access some (physical or logical) resource. For example, here is
  * a class that uses a semaphore to control access to a pool of items:
  * <pre>