fix: security features title being overflowed in smaller devices

[HarshMN2345]

What does this PR do?

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• Style
  • Updated feature section headers for improved responsiveness, with scaling text sizes optimized for various screen sizes.

[coderabbitai]

Walkthrough

The h2 header classes in the features component were updated to include responsive text sizing. The change replaced the static text size with a base size of text-3xl and added responsive breakpoints: sm:text-4xl for small screens and md:text-5xl for medium screens. All other existing styles were preserved. This is a styling-only modification with no logic or runtime behavior changes.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file affected with a localized CSS class update
• Straightforward responsive text sizing pattern following Tailwind conventions
• No logic changes or behavioral impact to verify
• Change is homogeneous and cosmetic in nature

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: fixing responsive text sizing for the security features title on smaller devices to prevent overflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-security-features-title-overflown-in-small-screens

---

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.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/routes/(marketing)/(components)/features.svelte (1)

75-75: Consider making line-height responsive.

With text size varying from 1.875rem to 3rem across breakpoints, the fixed leading-12 (48px) may not scale proportionally. Consider responsive line-height for better typography:

-class="text-title font-aeonik-pro text-primary max-w-[700px] text-3xl leading-12 text-pretty sm:text-4xl md:text-5xl"
+class="text-title font-aeonik-pro text-primary max-w-[700px] text-3xl leading-tight text-pretty sm:text-4xl sm:leading-snug md:text-5xl md:leading-tight"

Or use a responsive leading scale that matches your design system.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d5f194c and 9a39e6a.

📒 Files selected for processing (1)

• src/routes/(marketing)/(components)/features.svelte (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: tests
• GitHub Check: build
• GitHub Check: assets

🔇 Additional comments (1)

src/routes/(marketing)/(components)/features.svelte (1)

75-75: Verify that text-title doesn't conflict with explicit size utilities.

The class list includes both the custom text-title utility and explicit Tailwind size utilities (text-3xl, sm:text-4xl, md:text-5xl). If text-title defines a font-size, this could lead to:

• CSS specificity conflicts
• Unpredictable rendering due to cascade order
• One class overriding the other

Confirm the definition of text-title and ensure the explicit size utilities are not redundant or conflicting. The verification script in the previous comment will help identify this.