Skip to content

Fix grammar and formatting issues in README#642

Merged
aivus merged 1 commit into
masterfrom
fix-readme-grammar
Jul 3, 2026
Merged

Fix grammar and formatting issues in README#642
aivus merged 1 commit into
masterfrom
fix-readme-grammar

Conversation

@aivus

@aivus aivus commented Jul 3, 2026

Copy link
Copy Markdown
Member

Summary

Fixes several grammar, typo, and formatting issues in README.md.

Issue Fix
"may be saved not correctly" → "may not be saved correctly"
"Thease plugins ... can be coppied" → "These plugins ... can be copied"
"when error occured" → "when error occurred"
encoding: 'utf8' indented with spaces (rest use tabs) Re-aligned to tabs
"Parameters-" (×2) → "Parameters -"
"called each time when resource's downloading/handling/saving to was failed" → "called each time a resource's downloading/handling/saving fails"
const crypto = require('crypto'); import crypto from 'crypto'; (package is pure ESM)

Notes

  • Left the generate-filenamy-*-plugin.js links unchanged — "filenamy" is misspelled but matches the actual filenames on disk, so the links are correct.
  • Left the British/American spelling mix ("behaviour"/"behavior") alone to avoid needless churn.

🤖 Generated with Claude Code

- Fix typos: "Thease"→"These", "coppied"→"copied", "occured"→"occurred"
- Fix broken grammar in note and onResourceError description
- Add missing space in "Parameters-" labels
- Align mixed tab/space indentation in afterResponse example
- Use ESM import instead of require in generateFilename example (package is pure ESM)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aivus aivus merged commit 09b7bd1 into master Jul 3, 2026
14 checks passed
@aivus aivus deleted the fix-readme-grammar branch July 3, 2026 08:05
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