diff --git a/data/deprecations/15-4-non-expiring-access-tokens.yml b/data/deprecations/15-4-non-expiring-access-tokens.yml
index 651c170ae4b05e0299c00f354ed838f0580143e9..eddbde2f96aa3c4b168b9ca1ef12f40e5ffb6883 100644
--- a/data/deprecations/15-4-non-expiring-access-tokens.yml
+++ b/data/deprecations/15-4-non-expiring-access-tokens.yml
@@ -5,7 +5,7 @@
   reporter: hsutor
   body: |  # Do not modify this line, instead modify the lines below.
     Access tokens that have no expiration date are valid indefinitely, which presents a security risk if the access token
-    is divulged. Because access tokens that have an exipiration date are better, from GitLab 15.3 we
+    is divulged. Because access tokens that have an expiration date are better, from GitLab 15.3 we
     [populate a default expiration date](https://gitlab.com/gitlab-org/gitlab/-/issues/348660).
 
     In GitLab 16.0, any [personal](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html),
diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md
index 190d895e8d2a2d6a0e0d7c907012e8997a27b756..63c4c76ca299c3fe5699305abcd99ff091ceaa75 100644
--- a/doc/update/deprecations.md
+++ b/doc/update/deprecations.md
@@ -3389,7 +3389,7 @@ However, since certificate-based integration with Kubernetes clusters is depreca
 </div>
 
 Access tokens that have no expiration date are valid indefinitely, which presents a security risk if the access token
-is divulged. Because access tokens that have an exipiration date are better, from GitLab 15.3 we
+is divulged. Because access tokens that have an expiration date are better, from GitLab 15.3 we
 [populate a default expiration date](https://gitlab.com/gitlab-org/gitlab/-/issues/348660).
 
 In GitLab 16.0, any [personal](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html),