Writing Revision Prompt Builder Guide

Name the edit you need

This walkthrough fixes subject–verb agreement while preserving a conditional commitment. The page creates an editing prompt; it does not perform inline correction. A useful review checks what a revision means as well as whether it reads smoothly.

Step 1: identify protected meaning

Before: “The team are ready, but we may postpone the launch if approval is delayed.” Identify two details to preserve: postponement is possible rather than certain, and it depends on delayed approval. Paste the exact sentence and select Grammar.

Step 2: inspect the unchanged source

Generate the exact request below. The output still contains “The team are ready”. This is expected because the tool wraps the text without editing it. The after state here is an editing request ready to copy, not corrected prose.

Input and selections
Text: The team are ready, but we may postpone the launch if approval is delayed.
Action: Grammar

Exact tool output
Fix all grammar, spelling, and punctuation errors in this text:

"The team are ready, but we may postpone the launch if approval is delayed."

Provide the improved version without explanations.

Step 3: compare a possible revision

For a context treating the team as one unit, an editor might write: “The team is ready, but we may postpone the launch if approval is delayed.” This is an editorial example, not generated output. Agreement conventions can vary with dialect and intended meaning, so choose the convention appropriate to your document.

Step 4: audit the commitments

After getting a revision elsewhere, compare “may” and the approval condition with the original. Reject a rewrite that says “will postpone” without justification. If you then request a more formal tone, repeat this meaning check rather than assuming the earlier check still applies.

Mistake 1: expecting tracked changes

The page provides no inline suggestions or change history. Save the original yourself and compare it with the later revision sentence by sentence.

Mistake 2: asking for everything at once

Combining grammar, simplification, and tone changes can obscure why meaning shifted. Start with the specific problem, review the result, then request another pass only if needed.

Worked example: preserve a conditional reopening

Simplify adds an instruction to use accessible language while keeping the main ideas. The reading room sentence is copied unchanged, including may and the repair condition. The builder does not decide which words are essential. When a separate assistant returns a revision, check that a possible Monday reopening has not become an unconditional announcement.

Input and selections
input: We may reopen the reading room on Monday if repairs finish.
action: simplify

Exact tool output
Simplify this text using clearer, more accessible language while keeping the main ideas:

"We may reopen the reading room on Monday if repairs finish."

Provide the improved version without explanations.

Worked example: request a formal tone

The poster message uses Make formal. Compare the input with the quoted section of the output: the informal greeting has not been rewritten yet. Only the instruction before it changes. An eventual revision should preserve who needs to send edits and the before-lunch timing; a formal tone should not introduce a different deadline or additional approval step.

Input and selections
input: Hey team, please send the poster edits before lunch.
action: formal

Exact tool output
Rewrite this text in a formal, professional tone suitable for business communication:

"Hey team, please send the poster edits before lunch."

Provide the improved version without explanations.

Mistake 3: expecting tracked corrections

The result contains a request, not inline edits or a change history. Keep the source separately if you want to compare it with a revision produced elsewhere.

Mistake 4: expecting multiple actions at once

One selected action supplies one opening instruction. Choosing Formal after Grammar replaces the requested operation; it does not create a remembered sequence of editing passes.

Mistake 5: confusing brevity with preservation

Simplify asks to keep main ideas, but defines no word limit and checks no facts. If a particular caveat must survive, add that requirement to the copied request.

Tips for better results

• Start with a short passage that has enough context to stand alone.
• Compare actions using the same source so the changed instruction is visible.
• Read the fixed no-explanations closing; edit it yourself if you want a separate assistant to explain its proposed changes.