From eb79ba0d0acd1fe4602a96ea1898535930dd6dec Mon Sep 17 00:00:00 2001
From: Loann Le <84412881+taoism4504@users.noreply.github.com>
Date: Thu, 31 Mar 2022 19:50:24 -0700
Subject: [PATCH] updated the ssct faq page (#14806)

---
 website/content/docs/faq/ssct.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/faq/ssct.mdx b/website/content/docs/faq/ssct.mdx
index e26c3470d1..be3829e31f 100644
--- a/website/content/docs/faq/ssct.mdx
+++ b/website/content/docs/faq/ssct.mdx
@@ -39,7 +39,7 @@ For the sake of standardization between OSS and Enterprise, and due to the value
 
 Server Side Consistent Tokens introduces the following key changes:
 
-- Token length : Server side consistent tokens are longer, being 95+ characters as opposed to 27+ characters.
+- Token length : Server side consistent tokens are longer, being 95+ characters as opposed to 27+ characters. Since the token can be subject to change (see [Token](/docs/concepts/tokens)), we recommend that you plan for a maximum length of 255 bytes to future proof yourself if you have workflows that rely on the token size.
 - By default, Vault 1.10 will use the new token prefixes and new token format.
 - Tokens don't visibly have a ".namespaceID" suffix
 - Token prefix: Token prefixes are being changed as follows: