Update README.md

[omiaydin1]

Purpose or design rationale of this PR

Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

• No, this PR doesn't involve a new deployment, git tag, docker image tag
• Yes

Breaking change label

Does this PR have the breaking-change label?

• No, this PR is not a breaking change
• Yes

Summary by CodeRabbit

• Documentation
  • Updated documentation formatting.

[coderabbitai]

📝 Walkthrough

Walkthrough

A formatting change to README.md removing one blank line after the main header. No functional or structural modifications were made.

Changes

Cohort / File(s)	Summary
Documentation Formatting README.md	Removed a blank line after the "# Scroll Monorepo" header for improved formatting consistency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A blank line vanished without a trace,
The header stands proud in its rightful place,
Formatting fine-tuned, clean and neat,
The README now feels complete! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description only contains the empty template without any actual content—the purpose/design rationale section is completely unfilled, and no checkboxes are marked to indicate the conventional commit type or deployment considerations.	Fill in the 'Purpose or design rationale' section describing the change, select the appropriate conventional commit type (likely 'style'), and indicate deployment/breaking change status.
Title check	❓ Inconclusive	The title 'Update README.md' is vague and generic, describing only the file modified without conveying the specific nature or purpose of the change (formatting adjustment).	Use a conventional commit format (e.g., 'style: remove blank line from README.md header') to clearly describe what was changed and why.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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