FAQ content updated

[vianmangal]

FAQ content updated

spent a lot of water and tokens to review your slop

Greptile Summary

This PR updates account and payment information on the FAQ page. The main changes are:

• Clarified Google and Apple account sign-in.
• Reworded the direct UPI payment explanation.
• Clarified that UniPool does not process users' money.

Confidence Score: 4/5

The account eligibility wording conflicts with the Terms and needs to be aligned before merging.

The payment wording matches the direct UPI flow. The FAQ permits anyone to sign in, but the Terms restrict service eligibility to university students and staff.

landing/src/pages/FaqPage.tsx

T-Rex Logs

What T-Rex did

• Reproduced the eligibility policy contradiction by visiting the real /faq route and the /terms route, confirming that Google or Apple sign-in is allowed while university email verification is optional on /faq and required on /terms.
• Collected reproducibility artifacts, including a session video, eligibility screenshots, and the Playwright script used to exercise both routes, to support review of the observed contradiction.
• Verified the payment FAQ workflow by comparing the prior expansion of 'Does UniPool hold the money?' with the after-capture expansion to 'Does UniPool handle payments?' showing a direct-UPI answer.
• Confirmed the run completed with successful post-run assertions and exit code 0, and captured updated UI evidence such as the updated payment accordion and related logs.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
landing/src/pages/FaqPage.tsx	Updates sign-in and payment copy, with the new eligibility statement conflicting with the existing Terms.

_{Reviews (1): Last reviewed commit: "FAQ content updated" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Eligibility Policy Contradicts Terms

This answer says anyone with a Google or Apple account can use UniPool, while the Terms require users to be students or staff at a supported university and sign in with an institute email. A non-university user can complete the current sign-in flow based on this FAQ but remain ineligible under the Terms, leaving users with conflicting account requirements.

Artifacts

▶ Screen recording from the T-Rex run

• Shows the flow or interaction that T-Rex exercised.

Faq Eligibility

• Shows the rendered state that T-Rex checked.

Terms Eligibility

• Shows the rendered state that T-Rex checked.

Repro: Playwright script that exercised and captured both real application routes

• Contains supporting evidence from the run (text/javascript; charset=utf-8).

Repro: successful browser execution output containing both exact rendered policy passages

• Keeps the command output available without making the summary code-heavy.

Repro: Vite server output for the repository landing application used by the browser run

• Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}