fixing more PR comments

Author: splindsay-92

src/pages/docs/guides/pub-sub/notifications-center.mdx

@@ -491,15 +491,15 @@ notification payloads, and platform-specific setup, see the [push notifications
 ### Best practices for offline handling
 
 * **Enable history on inbox channels** to allow users to retrieve missed notifications
-* **Set appropriate history retention** based on your use case (24 hours to 1 year)
+* **Set appropriate history retention** based on your use case (2 minutes to 1 year)
 * **Use push notifications for critical alerts** that require immediate user attention
 * **Consider notification priorities** - not all notifications need push delivery
 
 ## Production-ready checklist
 
 Before launching your notification center, review these key points:
 
-* **Authentication:** Use token authentication for all client-side communication with short TTLs (1-4 hours).
+* **Authentication:** Use JWT authentication for all client-side communication with short TTLs (1-4 hours max).
 * **Capabilities:** Apply the principle of least privilege - clients should only have publish access to an outbox and subscribe access to their own inbox.
 * **Validation:** Validate all notification request data in your processing pipeline, never trust client data.
 * **Monitoring:** Subscribe to [`[meta]log` channels](/docs/platform/errors#meta) to track integration errors and issues.
@@ -511,7 +511,7 @@ Before launching your notification center, review these key points:
 
 ## Next steps
 
-* Read the [token authentication documentation](/docs/auth/token) for detailed auth implementation.
+* Read the [JWT authentication documentation](/docs/auth/token) for detailed auth implementation.
 * Explore [integration options](/docs/platform/integrations) to choose the right processing pipeline for your needs.
 * Learn about [push notifications](/docs/push) to handle offline delivery.
 * Review the [batch publish API](/docs/api/rest-api#batch-publish) for efficient multi-channel publishing.