Update SSD data tiering information in datastores.md

[ashotland]

Corrected typos and clarified SSD data tiering details.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview, Comment	Jun 21, 2026 9:35am

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Clarify SSD data tiering support and requirements in datastores docs
📝 Documentation 🕐 Less than 5 minutes

Description

• Clarify what SSD Data Tiering offloads to SSD versus what stays in memory.
• Document current platform availability and required compute/BYOC tiers.
• Keep the “more data types coming soon” note for future capability expansion.

High-Level Assessment

For a doc-only clarification, directly updating the existing section is the simplest and most discoverable approach; no alternative architecture is warranted.

Files changed (1) +3 / -2

Documentation (1) +3 / -2

datastores.mdAdd SSD Data Tiering availability/requirements details +3/-2

Add SSD Data Tiering availability/requirements details

• Refines the SSD Data Tiering bullet points by clarifying that large string values are offloaded while keys and small values remain in memory. Adds a statement describing current support (AWS/BCP) and prerequisites (enhanced Compute tier or supported BYOC instance families).

docs/cloud/datastores.md

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. coming soon placeholder text 📘 Rule violation ⚙ Maintainability

Description

The updated SSD data tiering section includes the placeholder statement `Support for more data types
is coming soon.` This violates the requirement to avoid placeholder content in documentation.

Code

docs/cloud/datastores.md[190]

+  Support for more data types is coming soon.

Evidence

PR Compliance ID 9 prohibits placeholder documentation text. The modified line explicitly states
Support for more data types is coming soon., which is non-specific placeholder content.

AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested: AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested: AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested: AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested: AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested: AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested: AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested: AGENTS.md: Documentation Must Not Include Placeholder Content; Examples Must Be Real and Tested
docs/cloud/datastores.md[190-190]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs include placeholder content (`coming soon`) instead of a concrete, validated statement.
## Issue Context
The documentation guidelines prohibit placeholder content because it can become outdated and mislead readers.
## Fix Focus Areas
- docs/cloud/datastores.md[190-190]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Wrong provider acronym ✓ Resolved 🐞 Bug ≡ Correctness

Description

The SSD Data Tiering documentation is inconsistent and confusing because it claims support on "AWS
and BCP" even though the rest of the docs use "GCP" for Google Cloud Platform, and the same section
contains multiple misspellings and inconsistent terminology (e.g., "ehanced" vs the documented
"Enhanced" tier). These issues reduce clarity and make provider and tier naming unreliable within
the page.

Code

docs/cloud/datastores.md[189]

+  SSD data tiering is curretly supported on AWS and BCP and requires ehanced Compute tier or supported BYOC instance family.

Evidence

The cited SSD Data Tiering section includes the provider acronym "BCP" even though the same page
elsewhere lists supported providers using "GCP" and the tiering feature documentation also uses a
dedicated "### GCP" section, indicating "GCP" is the intended acronym. In the same nearby lines, the
tiering bullets contain typos (e.g., "offloeads", "curretly", "ehanced"), and earlier in the page
the compute tier name is presented as "Enhanced" with correct spelling and capitalization,
demonstrating internal inconsistency between the new text and established terminology.

docs/cloud/datastores.md[28-31]
docs/managing-dragonfly/tiering.md[123-126]
docs/cloud/datastores.md[40-47]
docs/cloud/datastores.md[187-190]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The SSD Data Tiering section contains inconsistent provider naming (uses `BCP` instead of the repo’s standard `GCP`) and multiple misspellings/terminology mismatches (including `ehanced` vs the documented `Enhanced` tier), which makes the user-facing documentation unclear and inconsistent.
## Issue Context
This documentation page consistently refers to Google Cloud Platform as `GCP` (including in provider lists and a `### GCP` section), and it defines product terminology such as the `Enhanced` compute tier earlier on the same page. The SSD Data Tiering bullets should align with these established acronyms and terms and should be free of typos.
## Fix Focus Areas
- docs/cloud/datastores.md[187-190]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---