Grammar and style checking for written content
Comprehensive grammar and style checking that learns from your writing patterns and preferences over time.
Use when you want to:
I'll help you:
Example:
User: Check this email for errors
User: "I hope this email finds you good. Theirs a few things I wanted to discuss about the project were working on."
I'll also help you:
Example:
User: Check my blog post for readability
User: Analyze my writing style trends
User: Make this more concise
User: What are my common writing mistakes?
I'll also help you:
Example:
User: Does this match my professional voice?
User: Rewrite this for a technical audience
User: What makes my writing distinctive?
User: Create a style guide for my blog
Spelling & Grammar:
Sentence Structure:
Formatting:
Readability Metrics:
Style Consistency:
Writing Patterns:
Style Profile Matching:
Proactive Improvements:
At Level 1:
At Level 2:
At Level 3:
User: Check this email for errors
User: "Hi Sarah,
I hope this email finds you good. Theirs a few things I wanted to discuss about the project were working on.
First, the deadline is tommorow and were not quite ready yet. Theirs some bugs in the testing enviroonment that need fixing.
Can we meet at 3pm to discuss?
Thanks,
John"
Assistant: 🔍 Grammar Check Results
FOUND 8 ERRORS:
1. "finds you good" → finds you well (common phrase)
2. "Theirs" → There's (possession vs contraction)
3. "were working" → we're working (verb vs contraction)
4. "tommorow" → tomorrow (spelling)
5. "were not quite ready" → we're not quite ready (verb vs contraction)
6. "Theirs some bugs" → There are some bugs (possession vs existence)
7. "enviroonment" → environment (spelling)
8. "3pm" → 3 PM (formatting consistency)
CORRECTED VERSION:
"Hi Sarah,
I hope this email finds you well. There's a few things I wanted to discuss about the project we're working on.
First, the deadline is tomorrow and we're not quite ready yet. There are some bugs in the testing environment that need fixing.
Can we meet at 3 PM to discuss?
Thanks,
John"
**Note:** I preserved your casual tone and style.
User: Check my blog post for readability
User: [Long blog post about productivity]
Assistant: 📊 Readability Analysis
READABILITY SCORES:
- Flesch-Kincaid Grade: 12.4 (College level)
- Average sentence length: 22 words
- Average word length: 5.2 characters
- Passive voice: 15% (good, below 20% threshold)
- Paragraph length: Avg 4.7 sentences
SENTENCE STRUCTURE:
- Short sentences (< 15 words): 20%
- Medium sentences (15-25 words): 50%
- Long sentences (25+ words): 30%
ISSUES FOUND:
1. Very long sentence (42 words) in paragraph 3
Suggestion: Break into two sentences
2. Consecutive long sentences in paragraph 5
Suggestion: Add short sentence for pacing
3. Jargon-heavy sentence in paragraph 2
Suggestion: Simplify or explain terms
STYLE NOTES:
✓ Active voice usage is good (85% active)
✓ Paragraph structure is consistent
✓ Flow is logical and clear
⚠ Consider more sentence variety (shorter intro sentences)
OVERALL:
Your writing is clear and professional. The college-level reading score is appropriate for your audience. Reducing some long sentences would improve readability further.
Want me to suggest specific changes?
User: What are my common writing mistakes?
Assistant: 📈 Your Writing Pattern Analysis (Last 30 days)
COMMON MISTAKES (Top 5):
1. Their/There/They're confusion (12 times)
- Mistake: Using "their" for "there are"
- Pattern: Happens when typing quickly
- Fix: Auto-correct now enabled for this
2. Your/You're confusion (8 times)
- Mistake: Using "your" instead of "you're"
- Pattern: Casual writing contexts
- Fix: Added to your personal dictionary
3. Comma splices (6 times)
- Mistake: Joining independent clauses with only a comma
- Pattern: Long sentences with multiple clauses
- Suggestion: Use periods or semicolons
4. Inconsistent capitalization (5 times)
- Mistake: "email" vs "Email" vs "EMAIL"
- Pattern: Technical writing contexts
- Suggestion: Choose one style and stick to it
5. Passive voice overuse (4 instances > 20% threshold)
- Pattern: Professional emails and reports
- Suggestion: Try more active voice when appropriate
IMPROVEMENT TRENDS:
✓ Spelling errors: Down 40% (auto-correct working)
✓ Grammar errors: Down 25% (learning from mistakes)
✓ Passive voice: Down 15% (more active voice usage)
⚠ Comma usage: No change (still learning)
YOUR STRENGTHS:
✓ Clear sentence structure (most of the time)
✓ Good paragraph organization
✓ Strong vocabulary
✓ Consistent tone
FOCUS AREAS:
1. Their/There/They're - Practice with quick exercises
2. Sentence variety - Mix short and long sentences
3. Active voice - More "I did" vs "It was done by me"
Keep writing - you're improving!
User: Does this blog post match my usual voice?
User: [New blog post]
Assistant: 🎯 Style Profile Comparison
YOUR TYPICAL VOICE (from 50+ samples):
- Tone: Conversational but professional
- Sentence length: 18 words average
- Vocabulary: Accessible, occasional technical terms
- Structure: Short paragraphs, clear headers
- Personality: Friendly, first-person, anecdotes
THIS POST COMPARED TO YOUR STYLE:
MATCH SCORE: 78/100
✅ MATCHES YOUR STYLE:
- Conversational tone ✓
- First-person perspective ✓
- Short paragraphs ✓
- Clear structure ✓
⚠ DIFFERENT FROM YOUR USUAL STYLE:
- Sentence length: 26 words (vs 18 average) - too long
- Vocabulary: More technical jargon than usual
- Tone: Slightly more formal
- Structure: Longer paragraphs
SPECIFIC DEVIATIONS:
1. Paragraph 2: Very long (8 sentences vs your 3-4 norm)
→ Suggestion: Break into 2 paragraphs
2. Paragraph 4: Technical term "microservices architecture" without explanation
→ Your style usually explains technical terms
3. Tone: "This methodology leverages..." (formal)
→ Your usual style: "This approach uses..." (conversational)
RECOMMENDATION:
This post is good but doesn't fully sound like you. It reads more like a formal whitepaper than your typical blog voice.
REWRITE SUGGESTION (to match your style):
[Shows a version that sounds more like you]
Want me to apply this rewrite?
**Ready to check your writing? Just paste your text and I'll help!**34:["$","$L3a",null,{"content":"$3b","frontMatter":{"name":"grammar-check","description":"Grammar and style checking for written content"}}]