fix: typo

[rohit-goswami]

Description

Testing (ignore for documentation update)

Type of change

• Bug fix
• New feature
• Breaking change
• Documentation update

Checklist:

• I have read and agree to the Code of Conduct.
• I have signed the Contributor License Agreement (CLA).
• I have considered the Security Policy.
• I have self-reviewed and tested my code.
• I have updated documentation as needed.
• I agree to the project's custom license.

Additional Notes:

Summary by CodeRabbit

• Style
  • Improved readability in the “Deepfake Check” post.
  • Replaced an em dash with a comma in the U.S. deepfake job interviews paragraph; meaning unchanged.
  • Standardized display of monetary amounts in “The Fake Celebrity Love Story” by rendering $81,000 and $350,000 as inline code for clearer emphasis.
  • No content changes; purely formatting and punctuation refinements.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
reclaim-blog	Ready	Preview	Comment	Sep 9, 2025 8:11am

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Rohit Goswami seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

Edits to a single MDX blog post adjust punctuation in one paragraph and change formatting of two monetary amounts to inline code styling. No logic, metadata, or exports were modified.

Changes

Cohort / File(s)	Summary of Edits
Content formatting updates content/posts/deepfake-check.mdx	Replaced an em-dash with a comma in the U.S. deepfake job interviews paragraph; formatted $81,000 and $350,000 as inline code; content unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Rohit blogs #24 — Adds the full MDX post for the same path; this PR applies minor punctuation/formatting tweaks to that file.

Pre-merge checks (1 passed, 1 warning, 1 inconclusive)

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The current description is merely the default template with empty placeholders and does not document any of the actual changes made in this pull request.	Fill out the Description section with a summary of the punctuation and formatting adjustments and mark the appropriate Type of change and Checklist items to reflect this documentation update.
Title Check	❓ Inconclusive	The title “fix: typo” is overly generic and does not clearly convey the specific change made in this pull request.	Update the title to succinctly describe the specific typo or formatting change, such as “fix: replace em-dash with comma in deepfake-check post.”

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A hop, a dash—now comma in place,
Two shiny sums in code’s embrace.
I twitch my nose, reviews run quick,
Formatting neat, precise, and slick.
Carrot-check passed; ship it, swift! 🥕✨

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch rohit_blogs

---

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: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

content/posts/deepfake-check.mdx (1)

29-29: Add descriptive alt text to images (accessibility).

Both images render without alt text. Provide succinct descriptions to improve screen-reader support and SEO.

-![](https://i.postimg.cc/GhsrkBZ4/image-3.png)
+![Illustration related to deepfake scams (describe key visual briefly)](https://i.postimg.cc/GhsrkBZ4/image-3.png)

-![](https://media2.giphy.com/media/v1.Y2lkPTc5MGI3NjExanRyZXo3ajY0czlodnAwM3ZmazVoOWpvNHk2Mm1qZmVzZHE3NjVyNiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/M6EibzKIEJwzcWlTx5/giphy.gif)
+![GIF demo: Reclaim verification checkmark appearing on a video frame before joining a call](https://media2.giphy.com/media/v1.Y2lkPTc5MGI3NjExanRyZXo3ajY0czlodnAwM3ZmazVoOWpvNHk2Mm1qZmVzZHE3NjVyNiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/M6EibzKIEJwzcWlTx5/giphy.gif)

Also applies to: 109-109

🧹 Nitpick comments (2)

content/posts/deepfake-check.mdx (2)

47-47: Use an em dash for smoother cadence (style nit).

Change “private data, just a” to “private data—just a” for cleaner flow and to match common editorial style.

-Companies wouldn’t need to see the private data, just a cryptographic confirmation: *this is a real person, not an AI deepfake.*
+Companies wouldn’t need to see the private data—just a cryptographic confirmation: *this is a real person, not an AI deepfake.*

---

63-63: Avoid code styling for currency amounts (semantics/accessibility).

Inline code implies code, not money, and can confuse screen readers. Prefer plain text or bold/italics.

-Eventually, she sent over `$81,000` in cash and even sold her condo worth `$350,000`, all to fund her “relationship.”
+Eventually, she sent over $81,000 in cash and even sold her condo worth $350,000, all to fund her “relationship.”

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a53507b and d7e3d78.

📒 Files selected for processing (1)

• content/posts/deepfake-check.mdx (2 hunks)