diff --git a/docs/docs/support/advisory/a10009.md b/docs/docs/support/advisory/a10009.md
index 7137fdceaf..014700760a 100644
--- a/docs/docs/support/advisory/a10009.md
+++ b/docs/docs/support/advisory/a10009.md
@@ -6,7 +6,7 @@ title: Technical Advisory 10009
 
 Version: 2.53.0
 
-Date: Calendar week 23/24 2024
+Date: 2024-05-28
 
 ## Description
 
diff --git a/docs/docs/support/advisory/a10010.md b/docs/docs/support/advisory/a10010.md
new file mode 100644
index 0000000000..c2fd95902e
--- /dev/null
+++ b/docs/docs/support/advisory/a10010.md
@@ -0,0 +1,30 @@
+---
+title: Technical Advisory 10010
+---
+
+## Date and Version
+
+Version: 2.53.0
+
+Date: 2024-05-28
+
+## Description
+
+Version 2.53.0 optimizes the way tokens are created and migrates them to the v2 implementation already used by OAuth / OIDC tokens created through the session API.
+
+Because of this tokens events are no longer created on the user itself. To be as backwards compatible as possible a separate event is created on the user for the audit log.
+
+## Statement
+
+This change was tracked in the following PR:
+[perf(oidc): optimize token creation](https://github.com/zitadel/zitadel/pull/7822), which was released in Version [2.53.0](https://github.com/zitadel/zitadel/releases/tag/v2.53.0)
+
+## Mitigation
+
+If you use the ListEvents API to check the audit trail of a user or being able to compute Daily or Monthly Active Users, be sure to also include the `user.token.v2.added` event type in your search
+if you already query for the `user.token.added` event type.
+
+## Impact
+
+Once this update has been released and deployed, the `user.token.added` event will no longer be created when a user access token is created, but instead a `user.token.v2.added`.
+Existing `user.token.added` events will be untouched.
diff --git a/docs/docs/support/technical_advisory.mdx b/docs/docs/support/technical_advisory.mdx
index 565dae3904..e205b87683 100644
--- a/docs/docs/support/technical_advisory.mdx
+++ b/docs/docs/support/technical_advisory.mdx
@@ -164,7 +164,19 @@ We understand that these advisories may include breaking changes, and we aim to
       Fixes rare cases where updating projections was blocked by a `WRITE_TOO_OLD`-error when using cockroachdb.
     </td>
     <td>2.53.0</td>
-    <td>2024-05-27</td>
+    <td>2024-05-28</td>
+  </tr>
+  <tr>
+    <td>
+      <a href="./advisory/a10010">A-10010</a>
+    </td>
+    <td>Event type of token added event changed</td>
+    <td>Breaking Behavior Change</td>
+    <td>
+      Version 2.53.0 improves the token issuance. Due to this there are changes to the event types created on token creation.
+    </td>
+    <td>2.53.0</td>
+    <td>2024-05-28</td>
   </tr>
 </table>