Clarify anomaly detection methods and execution vs data freshness

[joostboon]

Summary

Follow-up to #2117. Fixes inaccuracies and improves clarity:

• Fix ML references: dbt package tests use z-score based anomaly detection, Elementary Cloud uses ML. Both pages were incorrectly stating "ML-based"
• Clarify execution_sla vs data_freshness_sla: added explicit explanation that execution_sla checks if the model ran, while data_freshness_sla checks if the data is actually fresh
• Cross-link from execution_sla page to data_freshness_sla for discoverability
• Remove em dashes

Test plan

• Verify all three pages render correctly

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-sla-and-volume-threshold-test-docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}