docs: fix DuckDB SQL example spelling#2416
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Pull request overview
Updates the DuckDB SQL documentation example output to correct a spelling error in one of the displayed choice values, improving clarity and professionalism in the docs.
Changes:
- Corrects “Confectionary” → “Confectionery” in a DuckDB query output example.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| │ varchar │ varchar │ varchar[] │ int64 │ | ||
| ├──────────────────────┼───────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼────────┤ | ||
| │ Which foods tend t… │ nutrition │ [Meat, Confectionary, Fruits and vegetables, Potatoes] │ 2 │ | ||
| │ Which foods tend t… │ nutrition │ [Meat, Confectionery, Fruits and vegetables, Potatoes] │ 2 │ |
There was a problem hiding this comment.
The spelling correction is applied in the first query output (choices list), but the later example output for choices[answer] AS correct_answer still shows "Confectionary". This makes the doc inconsistent and may confuse readers; please update the later output text to match the corrected spelling as well (and consider searching the doc for any other occurrences).
Summary
Related issue
Guideline alignment
Validation
git diff --checkNote
Low Risk
Docs-only change that corrects a single word in a rendered DuckDB query output example; no code paths or behavior are affected.
Overview
Fixes a typo in the DuckDB SQL docs example output by correcting the
choiceslist spelling from "Confectionary" to "Confectionery" indocs/hub/datasets-duckdb-sql.md.Reviewed by Cursor Bugbot for commit d062e6f. Bugbot is set up for automated code reviews on this repo. Configure here.