diff --git a/content/en/getting_started/tagging/_index.md b/content/en/getting_started/tagging/_index.md
index 40bbd56aed3..b390adb40b6 100644
--- a/content/en/getting_started/tagging/_index.md
+++ b/content/en/getting_started/tagging/_index.md
@@ -58,7 +58,8 @@ Below are Datadog's tagging requirements:
 
 1. Tags must **start with a letter** and after that may contain the characters listed below:
 
-    - Alphanumerics
+    - Letters (all Unicode letters are supported, e.g., a, ó, 気, 녕, ك, and ดี)
+    - Numbers
     - Underscores
     - Minuses
     - Colons
@@ -68,7 +69,7 @@ Below are Datadog's tagging requirements:
 
     Other special characters are converted to underscores.
 
-2. Tags can be **up to 200 characters** long and support Unicode letters (which includes most character sets, including languages such as Japanese).
+2. Tags can be **up to 200 characters** long.
 3. Tags are converted to lowercase. Therefore, `CamelCase` tags are not recommended. Authentication (crawler) based integrations convert camel case tags to underscores, for example `TestTag` --> `test_tag`.
 4. A tag can be in the format `value` or `<KEY>:<VALUE>`. Commonly used tag keys are `env`, `instance`, and `name`. The key always precedes the first colon of the global tag definition, for example:
 
@@ -171,4 +172,4 @@ For more information, see [Using Tags][1].
 [22]: /getting_started/tagging/using_tags/#developers
 [23]: /account_management/billing/usage_attribution/
 [24]: /getting_started/tagging/using_tags/#ci-visibility
-[25]: /containers/troubleshooting/log-collection?tab=datadogoperator#missing-host-level-tags-on-new-hosts-or-nodes
\ No newline at end of file
+[25]: /containers/troubleshooting/log-collection?tab=datadogoperator#missing-host-level-tags-on-new-hosts-or-nodes