Fix table rendering

[tyaga001]

Summary by CodeRabbit

• Documentation
  • Reworked two comparative blog posts for clearer presentation: several passages converted to blockquote-style emphasis for readability.
  • Added a comprehensive security attributes table to the feature-comparison article.
  • Expanded and clarified sections on deployment models, data modeling, queries, transactions, replication, backups, and security.
  • Refined wording for a more neutral, objective tone and improved overall consistency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

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

Project	Deployment	Review	Updated (UTC)
devtoolsacademy	Ready	Preview, Comment	Jan 6, 2026 3:32pm

[coderabbitai]

Walkthrough

Reformats and edits two blog MDX pages: converts multiple paragraphs into blockquotes, adds an HTML table for security attributes on the feature comparison page, and applies sentence-level wording and presentation adjustments; no code, exports, or public API changes.

Changes

Cohort / File(s)	Summary
Feature comparison page src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx	Converts many prose lines into blockquote-prefixed paragraphs, inserts a new HTML <table> for security attributes (Authentication, Authorization, Encryption in Transit/Rest, Auditing, License), and revises wording across Deployment Models, Data Modeling, Query/Indexing, Transactions, Replication, Backup, and Security sections.
Architecture & design page src/app/blog/eloqdoc-vs-mongodb-architecture-and-design/page.mdx	Changes multiple introductory and section paragraphs into blockquotes and applies minor typographic and phrasing tweaks; no structural or exported-symbol changes.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Ruff and UV blog: comparison table fixed #154: Similar blog MDX change converting Markdown tables to HTML <table> markup.
• Eloqdoc vs Mongodb Articles #158: Adds the same MDX blog pages that this PR edits; directly related to content and formatting changes.

Pre-merge checks

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided; the author did not fill in any of the required template sections including Summary, Type of Change, Changes Made, or other applicable sections.	Add a comprehensive pull request description following the template, including a summary of changes, type of change classification, detailed list of changes made, and verification of testing steps.
Title check	❓ Inconclusive	The title 'Fix table rendering' is vague and does not clearly describe the primary changes, which involve formatting conversions (blockquotes, table additions) across two blog markdown files.	Provide a more descriptive title that clarifies the changes, such as 'Format blog posts with blockquotes and add security comparison table' to better reflect the actual content modifications.

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bfb6ad6 and bdb0e20.

📒 Files selected for processing (1)

• src/app/blog/eloqdoc-vs-mongodb-architecture-and-design/page.mdx

🚧 Files skipped from review as they are similar to previous changes (1)

• src/app/blog/eloqdoc-vs-mongodb-architecture-and-design/page.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build (18.x)

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx (2)

331-371: Table structure looks good.

The HTML table is correctly structured and will render properly in MDX. The feature comparison data is clear and consistent.

Optional: Consider adding a caption for accessibility

Adding a <caption> element would improve accessibility and SEO:

 <table>
+  <caption>Security and Licensing Feature Comparison</caption>
   <thead>
     <tr>

---

433-439: Consider voice consistency throughout the article.

The pronoun changes shift from first-person to third-person in the conclusion, but earlier sections still use first-person (e.g., "I'll share a candid comparison" on Line 44). This mixed perspective may feel inconsistent to readers.

If a neutral, third-person voice is preferred, consider revising the entire article for consistency.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a702c6b and 223a86c.

📒 Files selected for processing (1)

• src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build (18.x)

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI Agents

In @src/app/blog/eloqdoc-vs-mongodb-architecture-and-design/page.mdx:
- Line 138: Replace the unhyphenated compound adjective "forward looking design"
with the hyphenated form "forward-looking design" in the sentence that currently
reads "From my perspective, EloqDoc’s architecture is a forward looking
design..." so the compound adjective correctly precedes the noun.

In @src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx:
- Around line 336-376: The table lacks semantic accessibility markers: add a
descriptive <caption> for the table and add scope="col" to the three header <th>
cells in the thead and scope="row" to the first <td> in each body row (or
convert those first-column cells to <th scope="row">) so screen readers can
correctly announce headers and cell relationships; ensure the caption text
clearly describes the table (e.g., "Security feature comparison between MongoDB
and EloqDoc").

🧹 Nitpick comments (2)

src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx (2)

214-214: Consider simplifying "in conjunction with" for readability.

The phrase "in conjunction with" could be replaced with a simpler alternative like "along with" or "and" to improve readability without changing the meaning.

Alternative wording

-To order events consistently across distributed nodes, the Data Substrate utilises hybrid logical clocks (HLCs) in conjunction with its own timestamping mechanism.
+To order events consistently across distributed nodes, the Data Substrate utilises hybrid logical clocks (HLCs) along with its own timestamping mechanism.

---

239-239: Consider simplifying "in conjunction with" for readability.

Similar to Line 214, the phrase "in conjunction with" could be replaced with a simpler alternative like "combined with" or "and" for better readability.

Alternative wording

-> EloqDoc's architecture distinctly handles replication. Instead of maintaining multiple complete copies of data on different nodes (such as primary-secondary), EloqDoc uses shared durable storage (object store) in conjunction with caching.
+> EloqDoc's architecture distinctly handles replication. Instead of maintaining multiple complete copies of data on different nodes (such as primary-secondary), EloqDoc uses shared durable storage (object store) combined with caching.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 223a86c and bfb6ad6.

📒 Files selected for processing (2)

• src/app/blog/eloqdoc-vs-mongodb-architecture-and-design/page.mdx
• src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx

🧰 Additional context used

🪛 LanguageTool

src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx

[style] ~214-~214: ‘in conjunction with’ might be wordy. Consider a shorter alternative.
Context: ...e utilises hybrid logical clocks (HLCs) in conjunction with its own timestamping mechanism. This a...

(EN_WORDINESS_PREMIUM_IN_CONJUNCTION_WITH)

---

[style] ~239-~239: ‘in conjunction with’ might be wordy. Consider a shorter alternative.
Context: ...s shared durable storage (object store) in conjunction with caching. The object storage (e.g., S3) ...

(EN_WORDINESS_PREMIUM_IN_CONJUNCTION_WITH)

src/app/blog/eloqdoc-vs-mongodb-architecture-and-design/page.mdx

[grammar] ~138-~138: Use a hyphen to join words.
Context: ...ive, EloqDoc’s architecture is a forward looking design that aligns with how clou...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (2)

src/app/blog/eloqdoc-vs-mongodb-architecture-and-design/page.mdx (1)

30-30: LGTM! Effective use of blockquotes for emphasis.

The conversion of key paragraphs to blockquotes improves visual hierarchy and readability, making introductory context and important takeaways stand out clearly.

Also applies to: 34-34, 73-73, 99-99, 103-103, 107-107, 144-144

src/app/blog/eloqdoc-vs-mongodb-feature-comparison/page.mdx (1)

42-48: LGTM! Consistent use of blockquotes for visual hierarchy.

The blockquote formatting effectively highlights key comparisons, introductions, and conclusions throughout the article, improving readability and visual flow.

Also applies to: 52-52, 87-87, 110-110, 123-123, 131-131, 140-140, 150-152, 165-165, 169-169, 190-190, 201-201, 212-212, 218-218, 224-224, 239-239, 250-250, 262-262, 273-273, 293-293, 310-310, 321-321, 332-334, 380-380, 384-384, 404-404, 413-413, 438-444