docs(search-events): Clarify Seer AI features requirement

Author: sentry-junior[bot]

docs/specs/search-events.md

@@ -143,7 +143,7 @@ Requests for a metric over time ("per hour", "per day", "trend", "over time") re
 
 - **Logs timestamp handling**: Logs don't support query-based timestamp filters like `timestamp:-1h`. Instead, use `statsPeriod=24h` parameter
 - **Project ID mapping**: API requires numeric project IDs, not slugs. Tool automatically converts project slugs to IDs
-- **Seer translation**: Seer translates natural-language queries when the organization has the required Seer features and AI features are not hidden. If Seer is unavailable or cannot translate the query, the tool falls back to the configured embedded agent.
+- **Seer translation**: Seer translates natural-language queries when the organization has the required Seer features and AI features are enabled. If Seer is unavailable or cannot translate the query, the tool falls back to the configured embedded agent.
 - **Seer cross-event filters**: Time series results do not apply cross-event filters. When Seer returns those filters for a time series, the response always begins with a warning identifying the omitted filters and the broader results, even when `includeExplanation` is false.
 - **Seer project scope**: For a successful Seer translation without `projectSlug`, search and Explorer links use `project=-1` to match the all-accessible-project scope sent to Seer. Other unscoped searches retain their existing default scope.
 - **Parallel attribute fetching**: For spans/logs/metrics, fetches both string and number attribute types in parallel for better performance