Skip to content

Fix README typo#220

Merged
zhangh43 merged 1 commit into
eloqdata:mainfrom
zhangh43:typo
Sep 29, 2025
Merged

Fix README typo#220
zhangh43 merged 1 commit into
eloqdata:mainfrom
zhangh43:typo

Conversation

@zhangh43

@zhangh43 zhangh43 commented Sep 28, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Documentation
    • Updated Quick Start with OS-specific setup guidance across three sections.
    • Clarified Step 1 to select the package matching the operating system for both EloqDoc-RocksDB and EloqDoc-RocksDBCloud.
    • Replaced example tarball names with versioned filenames (e.g., eloqdoc-0.2.6-ubuntu22-amd64.tar.gz).
    • Aligned file names and paths in extraction commands for consistency.

@zhangh43 zhangh43 requested a review from xiexiaoy September 28, 2025 23:01
@coderabbitai

coderabbitai Bot commented Sep 28, 2025

Copy link
Copy Markdown

Walkthrough

README.md updated to add OS-specific guidance in Quick Start Step-1, replace tarball filenames with versioned eloqdoc-0.2.6-ubuntu22-amd64.tar.gz, instruct users to choose OS-matching packages in EloqDoc-RocksDB and EloqDoc-RocksDBCloud sections, and adjust extraction commands for consistency.

Changes

Cohort / File(s) Summary
Documentation: Quick Start and install steps
README.md
- Added OS-specific guidance for Step-1 in three sections
- Replaced tarball names from eloqdoc-debug-ubuntu22-amd64.tar.gz to eloqdoc-0.2.6-ubuntu22-amd64.tar.gz across steps
- Added explicit instruction to select OS-matching packages for EloqDoc-RocksDB and EloqDoc-RocksDBCloud
- Minor consistency fixes in tar/gzip extraction paths and commands

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • lzxddz

Poem

I thump my paws—new steps so neat,
Versioned tarballs, a tidy treat.
Pick your OS, unzip with cheer,
RocksDB clouds, the path is clear.
Hop, hop—docs aligned, complete! 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title Check ⚠️ Warning The title “Fix README typo” implies a minor single typo correction, but the changeset actually provides updated OS-specific guidance steps, replaces multiple tarball filenames to a new version, and standardizes file paths in the README, so the title does not accurately reflect the scope of the updates. Rename the pull request to clearly summarize the primary changes, for example “Update README Quick Start with OS-specific guidance and v0.2.6 tarball filenames,” so that the title accurately conveys the scope of the documentation updates.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

Please see the documentation for more information.

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.


Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)
README.md (1)

11-11: Fix small typos and grammar for polish.

Applying these quick edits will align with the PR’s goal.

-... MongoDB API compability.
+... MongoDB API compatibility.
-👉 **Use Cases**: web applications, ducument store, ...
+👉 **Use Cases**: web applications, document store, ...
-All released package can be found at [download] page.
+All released packages can be found on the [download] page.
-After uncompress the package, you should see three directories:
+After you uncompress the package, you should see three directories:
-**Step-6**, open another terminal and run mongo client.
+**Step-6**, open another terminal and run the Mongo shell client.
-**Step-4**, start a S3 emulator, takes `minio` as an exmaple.
+**Step-4**, start an S3 emulator (using MinIO as an example).
-By default, `minio` listens on `http://127.0.0.1:9000`, whose default credentials is `minioadmin:minioadmin`,.
+By default, MinIO listens on http://127.0.0.1:9000. The default credentials are `minioadmin:minioadmin`.
-... EloqDoc-RocksDB and EloqDocRocksDBCloud from scratch.
+... EloqDoc-RocksDB and EloqDoc-RocksDBCloud from scratch.

Also applies to: 19-19, 68-68, 76-76, 100-104, 145-145, 155-156, 193-194

🧹 Nitpick comments (3)
README.md (3)

73-74: Use gzip flag and quote paths for portability.

On some systems tar needs -z to handle .tar.gz. Also quote $HOME paths.

-mkdir $HOME/eloqdoc-rocksdb && tar -xf eloqdoc-0.2.6-ubuntu22-amd64.tar.gz -C $HOME/eloqdoc-rocksdb
+mkdir -p "$HOME/eloqdoc-rocksdb" && tar -xzf eloqdoc-0.2.6-ubuntu22-amd64.tar.gz -C "$HOME/eloqdoc-rocksdb"
-mkdir $HOME/eloqdoc-rocksdbcloud && tar -xf eloqdoc-0.2.6-ubuntu22-amd64.tar.gz -C $HOME/eloqdoc-rocksdbcloud
+mkdir -p "$HOME/eloqdoc-rocksdbcloud" && tar -xzf eloqdoc-0.2.6-ubuntu22-amd64.tar.gz -C "$HOME/eloqdoc-rocksdbcloud"

Also applies to: 129-130


65-66: Optional: parameterize version to reduce churn.

Consider documenting with a version variable to ease future updates.

export ELOQDOC_VERSION=0.2.6
wget -c "https://download.eloqdata.com/eloqdoc/eloqdss_rocksdb/eloqdoc-${ELOQDOC_VERSION}-ubuntu22-amd64.tar.gz"

And similarly for RocksDBCloud.

Also applies to: 121-122


62-66: Clarify supported OS/architectures or add a package matrix

Download links are valid (HTTP 200). To avoid confusion for non-Ubuntu users, explicitly state the supported OS/arch (e.g. Ubuntu 22.04 x86_64) or include a table listing all available packages (Ubuntu 22, Ubuntu 24, macOS arm64, etc.) with their respective links.
Applies also to the Rocks S3 section (lines 118–122).

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8611752 and 34cc0ae.

📒 Files selected for processing (1)
  • README.md (4 hunks)

@xiexiaoy xiexiaoy left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@zhangh43 zhangh43 merged commit 76c626b into eloqdata:main Sep 29, 2025
2 checks passed
@coderabbitai coderabbitai Bot mentioned this pull request Dec 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants