From 47a994fcf8a0ac39f23e38a9ffaec1c745693a40 Mon Sep 17 00:00:00 2001
From: Gonzalo Servat <gservat@gitlab.com>
Date: Wed, 15 May 2024 03:28:58 +0000
Subject: [PATCH] Fix "exipiration" typo in deprecations
---
data/deprecations/15-4-non-expiring-access-tokens.yml | 2 +-
doc/update/deprecations.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/data/deprecations/15-4-non-expiring-access-tokens.yml b/data/deprecations/15-4-non-expiring-access-tokens.yml
index 651c170ae4b0..eddbde2f96aa 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 190d895e8d2a..63c4c76ca299 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),
--
GitLab