chore: readme cleanup

[nitisht]

Summary by CodeRabbit

• Documentation
  • Updated product description for clearer, more concise messaging
  • Enhanced Quickstart section with improved login instructions and formatting

[coderabbitai]

Walkthrough

This PR refines README.md documentation by rephrasing the "Why Parseable?" marketing highlights section for conciseness and clarifying Quickstart instructions, including explicit formatting of default credentials (admin / admin) and improved line spacing around production-deployment guidance.

Changes

README Documentation Refinements

Layer / File(s)	Summary
Why Parseable? highlights rewording README.md	Condensed and rephrased the three feature bullets (data lake architecture, fully featured, agent ready) to shorter, more direct descriptions while preserving link targets and structure.
Quickstart instructions and login clarification README.md	Adjusted Quickstart phrasing for data ingestion and dashboard viewing, reformatted default credentials as admin / admin, and separated production-deployment guidance into its own line.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• parseablehq/parseable#1323: Modifies README.md wording in the "Why Parseable?" and Quickstart sections with similar login instruction updates.
• parseablehq/parseable#1663: Edits README.md to reword "Why Parseable?" and Quickstart content with overlapping default UI login credentials and phrasing adjustments.

Suggested reviewers

• nikhilsinhaparseable

Poem

📝 A README refined, with words more clear,
Marketing shines, login's now sincere.
admin / admin for all to see,
Quickstart now guides both you and me.
Parsed with care, docs take their bow. 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided; the template requires a Description section with goal, rationale, and key changes, plus completion of checklist items.	Add a pull request description following the template, including the Description section with details about the README changes and mark relevant checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: readme cleanup' accurately reflects the main change—updating and cleaning up the README.md file with rephrased sections and improved formatting.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch nitisht-patch-1

---

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

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 26: Update the README sentence that currently begins "Purpose built for
observability..." to use the hyphenated compound modifier "Purpose-built" so it
reads "Purpose-built for observability and designed around proven data
engineering patterns, Parseable gives you everything you need to make sense of
your telemetry data, right out of the box."; edit the exact sentence text in
README.md to replace "Purpose built" with "Purpose-built".

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: f0906607-1ea2-4edb-b2d9-35e3283e60e0

📥 Commits

Reviewing files that changed from the base of the PR and between 709c089 and f657b4f.

📒 Files selected for processing (1)

• README.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Hyphenate “Purpose-built” for correct grammar.

Line 26 should use “Purpose-built” (compound modifier) for correct English usage and consistency with polished docs tone.

✍️ Proposed edit

-Purpose built for observability and designed around proven data engineering patterns, Parseable gives you everything you need to make sense of your telemetry data, right out of the box.
+Purpose-built for observability and designed around proven data engineering patterns, Parseable gives you everything you need to make sense of your telemetry data, right out of the box.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Purpose built for observability and designed around proven data engineering patterns, Parseable gives you everything you need to make sense of your telemetry data, right out of the box.
	Purpose-built for observability and designed around proven data engineering patterns, Parseable gives you everything you need to make sense of your telemetry data, right out of the box.

🧰 Tools

🪛 LanguageTool

[grammar] ~26-~26: Use a hyphen to join words.
Context: ...ngle binary. ## Why Parseable? Purpose built for observability and designed aro...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 26, Update the README sentence that currently begins
"Purpose built for observability..." to use the hyphenated compound modifier
"Purpose-built" so it reads "Purpose-built for observability and designed around
proven data engineering patterns, Parseable gives you everything you need to
make sense of your telemetry data, right out of the box."; edit the exact
sentence text in README.md to replace "Purpose built" with "Purpose-built".