Skip to content

fix(docs): correct 'occured' to 'occurred' in timings column documentation - #38

Open
Jah-yee wants to merge 1 commit into
asg017:mainfrom
Jah-yee:fix-occured
Open

Jah-yee wants to merge 1 commit into
asg017:mainfrom
Jah-yee:fix-occured

Conversation

@Jah-yee

@Jah-yee Jah-yee commented Oct 19, 2026 •

Copy link
Copy Markdown

Summary

fix(docs): correct 'occured' to 'occurred' in timings column documentation.

Changes

  • docs.md
    • Before: The 'timings' column contains timestamps of when specific events happened while making the request. It is a JSON object, where the keys are the name of the e...
    • After: The 'timings' column contains timestamps of when specific events happened while making the request. It is a JSON object, where the keys are the name of the e...

Verification

  • Changes are limited to the lines shown above; no unrelated edits.
  • Please let me know if you would prefer a different wording or scope.

@Jah-yee

Jah-yee commented Oct 19, 2026

Copy link
Copy Markdown
Author

Thanks for filing this issue! This PR fixes the spelling in the timings column documentation. The vendored sqlite3.c was left untouched since it's upstream code.

@Jah-yee

Jah-yee commented Nov 2, 2026

Copy link
Copy Markdown
Author

Following up on the documentation fix in docs.md for the timings column description — the sentence explaining that the values are ISO-8601 timestamps "of when it occured" now reads "occurred", which is the only line this PR changes.

The repo has been active since this was opened, so I would like to check whether that paragraph has been rewritten in the meantime. If it has, feel free to close this PR — I will not re-open it. If the paragraph is unchanged, a review is welcome; the diff is a single-word correction inside the existing sentence, with no changes to the surrounding markdown, the table of event keys, or the Go code that produces those timings.

This branch has not been deployed

No deployments
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.

1 participant