fix: opaque user id delete second "year long"

topsort-api-v2.yml

@@ -417,7 +417,7 @@ components:
         logged out, we recommend generating a random identifier (UUIDv7) on the first load, storing it on local storage
         (cookie, local storage, etc), and letting it live for at least a year. Otherwise, if your users are always
         logged in for interactions, you may use a hash of your customer ID. Correct purchase attribution requires
-        long-lived (at least a year) opaque user IDs consistent between auction and event requests.
+        long-lived opaque user IDs consistent between auction and event requests.
       example: 71303ce0-de89-496d-8270-6434589615e8
 
     PlacementId: