正しいスペルと文法
Prompt detail
元のメッセージを徹底的に校正し、最適化してください。
##元のコンテンツ:
{{@Source_Content}}
##校正は以下の手順に従ってください。
1. テキスト全体を注意深く読み、内容、文脈、そしてトーンを理解してください。
2. 文法、スペル、句読点の誤りを修正し、ぎこちない、あるいは不正確な文や段落を修正して校正してください。変更点ごとに項目別の修正メモを添付してください。元のトーンとスタイル（フォーマル、カジュアル、テクニカルなど）を維持し、核となる情報を変更しないでください。
3. 元の意味を維持し、核となる情報を恣意的に変更しないでください。
4. 言語が自然で、流暢で、適切なフォーマルさであることを確認してください。必要に応じて、文の構造と語彙を調整してください。
5. 元の文章に含まれる慣用句、文化的な言及、比喩的な表現に注意してください。
6. 問題が本当に誤りであるかどうか確信が持てない場合は、変更を提案しないでください。
7. 冗長または曖昧な表現を削除して、明確さと論理の流れを改善します。
What the prompt does
Rough drafts, hasty emails, and unpolished documents undermine your credibility. This prompt takes any piece of writing — an email, a report section, a Slack message, or a proposal — and performs a comprehensive proofread. It corrects grammar, spelling, punctuation, and awkward phrasing while preserving your original tone and meaning.
With remio, you can pull content directly from your emails, meeting notes, or documents and run it through this proofreading workflow without switching apps. You get back a polished version alongside itemized revision notes explaining every change made.
When to use
• Before sending a high-stakes email to a client or executive, ensuring zero typos and maximum clarity.
• When finalizing a proposal or SOW draft that multiple teammates contributed to, smoothing out inconsistent tone and fixing errors across sections.
• After quickly drafting a company-wide announcement in Slack and wanting a second pass for professionalism.
• When editing a non-native English speaker's written deliverable without altering their intended meaning.
• Before publishing internal documentation or knowledge base articles that need to read cleanly.
Prompt examples
Input: Proofread this client follow-up email:
"Hi Sarah, Thanks for the call yesterday. I wanted to follow-up on a few of the items we discussed. First, regarding the Q3 deliverables — we are on track to deliver all milestones accept the UX audit, which has been delayed do to a resource constraint. We will keep you in the loop on the revised timeline. Also, I wanted to confirmed that the budget reallocation you mentioned is fine on our end. Looking forward to our next sync."
remio responds:
Here is your polished email:
"Hi Sarah, Thanks for the call yesterday. I wanted to follow up on a few of the items we discussed. First, regarding the Q3 deliverables — we are on track to deliver all milestones except the UX audit, which has been delayed due to a resource constraint. We will keep you updated on the revised timeline. Also, I wanted to confirm that the budget reallocation you mentioned works on our end. Looking forward to our next sync."
Revision notes:
1. "follow-up" → "follow up" (verb form, no hyphen)
2. "accept" → "except" (incorrect word)
3. "do to" → "due to" (spelling error)
4. "keep you in the loop" → "keep you updated" (more concise)
5. "confirmed" → "confirm" (verb tense correction)
6. "is fine" → "works" (more natural phrasing)
Tip 1: Specify the intended audience and context before the text (e.g., "This is a formal email to a C-level client") so the proofreader calibrates formality and word choice accordingly.
Tip 2: If the original was drafted in a hurry after a meeting, use remio to surface the meeting transcript first, then paste both the draft and transcript so the proofreader can verify factual accuracy alongside grammar.
Tip 3: Flag any intentional style choices (brand-specific spelling, internal jargon) so they aren't incorrectly marked as errors.
More tips
レミオは知識に関するあらゆるニーズを満たします
詳しい機能はこちら
ウェブサイト、ローカル フォルダー、ファイルからリソースをキャプチャします。
ナレッジベース全体から、信頼できる回答を即座に取得できます。
デスクトップ、ブラウザ、モバイルで使えるアシスタント。
無制限の無料録音と文字起こし、ボットなし。