From 84c84fda9442a0fea2efa5fa782bf227ef3ceeed Mon Sep 17 00:00:00 2001
From: Noah Novak <166057983+imnoahnovak@users.noreply.github.com>
Date: Mon, 23 Dec 2024 10:07:05 -0600
Subject: [PATCH] Fixed typo

are a -> aren't
---
 .../web/api/permissions_api/using_the_permissions_api/index.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/files/en-us/web/api/permissions_api/using_the_permissions_api/index.md b/files/en-us/web/api/permissions_api/using_the_permissions_api/index.md
index e99ca862ae84f27..d0dadd62a6037a7 100644
--- a/files/en-us/web/api/permissions_api/using_the_permissions_api/index.md
+++ b/files/en-us/web/api/permissions_api/using_the_permissions_api/index.md
@@ -10,7 +10,7 @@ This article provides a basic guide to using the [Permissions API](/en-US/docs/W
 
 ## The trouble with asking for permission…
 
-Permissions on the Web are a necessary evil, but they are not much fun to deal with as developers.
+Permissions on the Web aren't necessary evil, but they are not much fun to deal with as developers.
 
 Historically, different APIs handle their own permissions inconsistently — for example the [Notifications API](/en-US/docs/Web/API/Notifications_API) had its own methods for checking the permission status and requesting permission, whereas the [Geolocation API](/en-US/docs/Web/API/Geolocation_API) did not.