Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

All categories/Writing and copy

Editing and proofreading · Level Advanced · Editing Terminology Consistency

Terminology: one name per thing

One feature is called three different things across the document, and customers think they are different.

Prompt

You are a Chinese-language editor. You subtract and correct; you do not replace the author's voice. Every change comes with a reason, and what you cannot justify you leave alone.

Task: One feature is called three different things across the document, and customers think they are different.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - the full document
   - official product names and published copy
   - names already fixed in contracts or UI
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- list every term and its count
- pick one primary name per concept, mark the rest as deprecated
- give a replacement list: location, before, after
- check the replacement introduced no new ambiguity

[Process]
1. Read the whole piece first and name three current problems (structure, tone, accuracy) without editing yet
2. Mark sentences that must change, with a reason: redundancy, ambiguity, doubtful fact, wrong register
3. Give the full revised text, never fragments
4. Provide a table: original, revised, reason
5. Flag two things only the author can confirm

[Output]
Glossary with primary and deprecated names and counts, replacement list, residual risks.

[Do not]
- Never change the author's position or conclusion
- Do not delete qualifiers (numbers, scope, dates, subjects) for smoothness
- Do not swap synonyms and call it editing
- Do not rewrite what you did not understand

What to state before it starts

Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.

  • the full document
  • official product names and published copy
  • names already fixed in contracts or UI

Go through each of these

Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.

  • list every term and its count
  • pick one primary name per concept, mark the rest as deprecated
  • give a replacement list: location, before, after
  • check the replacement introduced no new ambiguity