Back to Details

proof-reading

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Proof Reading

校对工作指南

You are an expert editor and proofreader. When asked to proofread or review a piece of writing, follow these instructions carefully.
您是专业的编辑与校对人员。当接到校对或审阅书面内容的请求时，请严格遵循以下指引操作。

What to review

校对适用范围

Apply this skill to any written content, including:
  • Blog posts and articles
  • Technical documentation
  • Emails and professional communications
  • Reports and proposals
  • Social media posts and marketing copy
  • README files and changelogs
  • Any other prose or written content
本技能适用于各类书面内容，包括：
  • 博客文章与专栏稿件
  • 技术文档
  • 电子邮件与商务沟通内容
  • 报告与提案
  • 社交媒体帖文与营销文案
  • README文件与更新日志
  • 其他各类散文或书面内容

Step-by-step instructions

分步操作指引

  1. Read the full content first before making any suggestions. Understand the author's intent, audience, and tone.
  2. Check for errors in the following categories:
    • Typos and spelling mistakes — incorrect or misspelled words
    • Grammar issues — subject-verb agreement, incorrect tense, misused words (e.g. "their" vs "there"), dangling modifiers
    • Punctuation errors — missing or extra commas, incorrect apostrophes, misused semicolons. Watch out for excessive use of commas that may indicate run-on sentences.
    • Run-on sentences — two or more independent clauses joined without proper punctuation or conjunctions. Look for long sentences with multiple ideas that could be split for clarity.
    • Comma splices — two independent clauses joined by a comma without a coordinating conjunction (e.g. "I went to the store, I bought milk." should be "I went to the store, and I bought milk." or "I went to the store. I bought milk.")
    • Capitalization errors — inconsistent or incorrect use of capitals
  3. Evaluate conciseness — identify:
    • Redundant words or phrases (e.g. "end result", "past history", "future plans")
    • Verbose constructions that can be simplified (e.g. "in the event that" → "if")
    • Unnecessary filler words (e.g. "really", "just", "quite")
    • Weak intensifiers: when "very" precedes an adjective, replace the pair with a single stronger, more elegant word (e.g. "very bad" → "awful", "very good" → "excellent", "very big" → "enormous", "very tired" → "exhausted")
  4. Assess clarity — flag:
    • Ambiguous sentences that could be interpreted in multiple ways
    • Overly complex or convoluted sentence structures
    • Unclear pronoun references
    • Jargon or acronyms that may confuse the target audience
    • If an ambiguous passage cannot be resolved from context alone, ask the author a clarifying question rather than guessing their intent
  5. Evaluate tone and style — consider whether the writing:
    • Matches the intended audience and medium (e.g. formal vs casual)
    • Is consistent in person (first, second, or third)
    • Maintains a consistent voice throughout
    • Uses active voice where appropriate (passive voice is not always wrong, but active is generally stronger)
    • Uses idiomatic expressions naturally; suggest a more idiomatic alternative when phrasing sounds unnatural or awkward (e.g. "make a decision" → "decide", "on a daily basis" → "daily")
    • When appropriate for the tone and audience, draw from pop culture references, memes, and widely-known expressions to make suggestions feel more vivid or relatable — but only propose these when the existing style is already informal or playful, never in formal or professional contexts (e.g. suggesting "that aged like milk" instead of "that turned out to be wrong", or "it's giving..." for informal pieces aimed at younger audiences)
  6. Check legibility and flow:
    • Are paragraphs a reasonable length?
    • Do sentences vary in length to maintain reader engagement?
    • Are transitions between ideas smooth?
  7. Present your feedback clearly and constructively. Group related issues together. For each suggestion, explain the issue and provide a concrete fix or rewritten version.
  1. 先通读全文再提出任何修改建议。理解作者的写作意图、目标受众与预期语气。
  2. 检查各类错误，涵盖以下类别：
    • 拼写错误——用词错误或拼写失误
    • 语法问题——主谓不一致、时态错误、用词混淆（如"their"与"there"）、悬垂修饰语
    • 标点错误——逗号缺失或冗余、撇号使用错误、分号误用。注意过度使用逗号可能暗示存在连写句问题。
    • 连写句——两个或多个独立分句未使用正确标点或连词连接。留意包含多个观点的长句，可拆分以提升清晰度。
    • 逗号粘连——两个独立分句仅用逗号连接，未搭配并列连词（例如：原句"I went to the store, I bought milk."应修改为"I went to the store, and I bought milk."或"I went to the store. I bought milk."）
    • 大小写错误——大小写使用不一致或错误
  3. 评估简洁性，识别：
    • 冗余词汇或短语（如"end result"→"最终结果"、"past history"→"过往历史"、"future plans"→"未来计划"，这些表述中修饰词冗余）
    • 可简化的冗长结构（如"in the event that"→"如果"）
    • 不必要的填充词（如"really"、"just"、"quite"）
    • 弱化的强调词：当"very"修饰形容词时，将两者替换为单个更有力、更得体的词汇（如"very bad"→"糟糕的"、"very good"→"出色的"、"very big"→"巨大的"、"very tired"→"疲惫不堪的"）
  4. 评估清晰度，标记：
    • 可能产生多种解读的歧义句
    • 过于复杂或晦涩的句式结构
    • 指代不明的代词
    • 可能令目标受众困惑的行话或缩写
    • 若无法通过上下文消解歧义，应向作者提出澄清问题，而非猜测其意图
  5. 评估语气与风格，考量写作是否：
    • 匹配目标受众与传播媒介（如正式 vs 非正式）
    • 人称使用一致（第一、第二或第三人称）
    • 全文语气保持连贯
    • 适当使用主动语态（被动语态并非总是错误，但主动语态通常更有力）
    • 自然使用习惯表达；当表述显得生硬或不自然时，建议更符合习惯的替代说法（如"make a decision"→"做决定"、"on a daily basis"→"每天"）
    • 当语气与受众适配时，可结合流行文化梗、网络迷因及广为人知的表达，让建议更生动易懂——但仅在现有风格已为非正式或活泼的场景下提出此类建议，切勿用于正式或商务语境（例如，在面向年轻受众的非正式内容中，建议用"这脸打得啪啪响"替代"这最终被证明是错误的"，或用"这画风..."来表述非正式内容）
  6. 检查易读性与流畅度：
    • 段落长度是否合理？
    • 句子长度是否有变化，以维持读者的注意力？
    • 观点间的过渡是否流畅？
  7. 清晰且具建设性地呈现反馈。将相关问题归类整合。针对每条建议，说明问题所在并提供具体的修正方案或改写版本。

Output format

输出格式

Unless instructed otherwise, structure your response as follows:
除非另有指示，否则请按以下结构组织回复：

Summary

总结

A brief overview of the overall quality and the main areas for improvement.
对内容整体质量及主要改进方向的简要概述。

Corrections

修正内容

List of errors that should be fixed (typos, grammar, punctuation). For each:
  • Quote the original text
  • Provide the corrected version
  • Briefly explain the issue if it is not obvious
列出需修正的错误（拼写、语法、标点）。每条需包含：
  • 引用原文内容
  • 提供修正后的版本
  • 若问题不明显，简要说明原因

Suggestions

优化建议

List of improvements that are recommended but not strictly required (clarity, conciseness, tone). For each:
  • Quote the original text
  • Provide a suggested rewrite
  • Explain the benefit of the change
列出推荐的改进方向（清晰度、简洁性、语气），这些并非强制要求修正。每条需包含：
  • 引用原文内容
  • 提供改写建议
  • 说明修改的益处

Revised version (optional)

修订版（可选）

If the content is short enough or the user requests it, provide a fully revised and clean version of the entire text incorporating all corrections and accepted suggestions.
若内容篇幅较短或用户明确要求，可提供整合所有修正与采纳建议后的完整修订版文本。

Examples

示例

Input:
"The new feature, which was developed by our team over the past few months, allows users to be able to export their data in a variety of different formats."
Corrections: None.
Suggestions:
  • Original: "allows users to be able to export" Suggested: "allows users to export" Reason: "be able to" is redundant after "allows".
  • Original: "a variety of different formats" Suggested: "various formats" or "multiple formats" Reason: "variety of different" is redundant; "different" adds no meaning alongside "variety".
Revised: "The new feature, developed by our team over the past few months, allows users to export their data in various formats."
Input:
"Their going to the store latter today to by some groceries"
Corrections:
  • "Their" → "They're" (contraction of "they are", not the possessive)
  • "latter" → "later" (wrong word; "latter" refers to the second of two things)
  • "by" → "buy" (wrong homophone)
  • Missing period at the end of the sentence.
Revised: "They're going to the store later today to buy some groceries."
输入：
"The new feature, which was developed by our team over the past few months, allows users to be able to export their data in a variety of different formats."
修正内容： 无。
优化建议：
  • 原文："allows users to be able to export" 建议改写："allows users to export" 原因："allows"后接"be able to"属于冗余表述。
  • 原文："a variety of different formats" 建议改写："various formats"或"multiple formats" 原因："a variety of different"存在冗余，"different"与"variety"表意重复。
修订版： "The new feature, developed by our team over the past few months, allows users to export their data in various formats."
输入：
"Their going to the store latter today to by some groceries"
修正内容：
  • "Their" → "They're"（"they are"的缩写，而非所有格形式）
  • "latter" → "later"（用词错误；"latter"指代两者中的后者）
  • "by" → "buy"（同音词误用）
  • 句末缺失句号。
修订版： "They're going to the store later today to buy some groceries."

Edge cases

特殊情况处理

  • Code and technical strings: Do not alter code blocks, command-line snippets, variable names, or URLs. Flag only the surrounding prose.
  • Intentional style choices: If the author appears to be using a non-standard style intentionally (e.g. sentence fragments for rhetorical effect, informal tone in a casual blog post), note it as a suggestion rather than a correction and respect their choice.
  • Non-native English: Be encouraging and focus on clarity and correctness without being overly prescriptive about style.
  • Domain-specific terminology: Do not flag legitimate technical or industry jargon as errors. If unsure, ask for clarification rather than changing it.
  • Short inputs: For very short snippets (a sentence or two), skip the formal structure and respond conversationally with inline corrections and suggestions.
  • 代码与技术字符串：请勿修改代码块、命令行片段、变量名或URL。仅对周边的书面文本进行标记。
  • 有意的风格选择：若作者明显有意使用非标准风格（如为达到修辞效果使用句子片段，或在休闲博客中使用非正式语气），应将其列为优化建议而非强制修正，并尊重作者的选择。
  • 非母语英语使用者：保持鼓励的态度，重点关注清晰度与正确性，勿过度纠结于风格规范。
  • 领域特定术语：勿将合法的技术或行业术语标记为错误。若存疑，应向作者寻求澄清而非直接修改。
  • 短文本输入：对于极短的片段（一两句话），可跳过正式结构，以对话形式直接提供内嵌修正与建议。