This content was created with AI assistance and may contain errors or inaccuracies. Always verify against authoritative academic sources.

Week 235: Writing Polish

Week 235 of 288~32 min read

Learning Objectives

•Eliminate ambiguity and unnecessary jargon
•Strengthen paragraph transitions and flow
•Vary sentence structure for readability
•Remove redundancy while maintaining completeness
•Perfect technical terminology and notation
•Apply consistent style throughout the manuscript
•Time separation (wait 24-48 hours between writing and editing)
•Format separation (edit on paper or different screen)
•Role separation (pretend you're editing someone else's work)
•Word choice (right word for meaning)
•Sentence structure (clear syntax)
•Paragraph structure (logical development)
•Section flow (coherent narrative)
•"It might be possible that perhaps the effect could be due to..."
•Better: "The effect is likely due to..." or "We attribute the effect to..."
•"superconducting qubit two-level system energy relaxation rate measurement"
•Better: "measurement of the energy relaxation rate in superconducting qubits"
•"The sample was prepared and then was measured and the results were analyzed"
•Better: "We prepared the sample, measured it, and analyzed the results"
•"We used RB to characterize the CZ gate in our transmon-based QPU"
•Better: Define acronyms on first use; explain technical terms
•Mark unclear sentences
•Note missing information
•Identify unsupported claims
•Check topic sentences
•Verify transitions
•Assess paragraph length
•Identify passive voice
•Find weak verbs
•Spot redundancy
•Check subject-verb agreement
•Verify reference format
•Confirm number consistency
•Is this sentence necessary?
•Does it say exactly what I mean?
•Is it as short as possible without losing meaning?
•Is the most important information prominent?
•Does it connect to surrounding sentences?
•**Topic sentence:** States the paragraph's main point (usually first sentence)
•**Support:** All sentences support the topic
•**Coherence:** Sentences connect logically
•**Necessity:** Paragraph contributes to section
•**Length:** Not too long (aim for 3-6 sentences in science writing)
•Before: "The data show that there is an increase in fidelity"
•After: "The data reveal a fidelity increase" or "Fidelity increased (Fig. 2)"
•"In the event that" → "If"
•"Due to the fact that" → "Because"
•"In order to" → "To"
•"At the present time" → "Now" / "Currently"
•"For the purpose of" → "For" / "To"
•Agent unknown or unimportant: "The sample was damaged during shipping"
•Agent obvious: "The samples were stored at 4 K" (obviously by researchers)
•Emphasis on action: "This effect was first observed in 1995"
•Spell out numbers below 10 unless with units: "three qubits" but "3 mK"
•Use SI units or field-standard equivalents
•Space between number and unit: "10 μs" not "10μs"
•Use proper symbols: "μ" not "u", "Ω" not "ohm" (in equations)
•Equations are part of sentences—they need punctuation
•Introduce equations: "The Hamiltonian is given by" followed by equation
•Define all variables when first introduced
•Reference equations by number: "Equation (3)" or "Eq. (3)"
•Define on first use: "quantum error correction (QEC)"
•After definition, use abbreviation consistently
•Common abbreviations may not need definition (e.g., DNA)
•Journal-specific conventions may apply
•Citations go after the claim, before the period: "...as shown previously [1]."
•Multiple citations: "[1-3]" or "[1, 2, 3]" depending on journal
•Self-citation: Use sparingly and appropriately
•Citing reviews instead of primary sources
•Missing recent relevant work
•Incorrect citation format for journal
•Highlight any sentence you had to read twice
•Mark any technical term that might be unclear to a general physics reader
•Identify sentences longer than 30 words
•List any ambiguous pronouns
•Verify every numerical value against data sources
•Check all equation derivations or references
•Confirm consistent notation throughout
•Ensure all claims are appropriately qualified
•Read only the first sentence of each paragraph in sequence
•Assess: Does this read as a coherent summary?
•Identify weak transitions
•Add or strengthen connecting language
•Target: Reduce manuscript by 10% without losing content
•Eliminate redundant phrases
•Combine short, related sentences
•Remove hedging language where inappropriate
•Identify every passive voice construction
•Convert to active where appropriate
•Find repeated sentence structures
•Vary sentence length (short for emphasis, longer for complex ideas)
•Run spell-check and grammar-check (but don't blindly accept)
•Verify every reference is correctly formatted
•Check that every citation is necessary
•Confirm reference numbers match bibliography
•Print manuscript and read aloud (catch errors ears find that eyes miss)
•Note remaining issues
•Make final corrections
•Prepare for Week 236 review simulation
•[Guide.md](Guide.md) - Detailed editing strategies
•[Templates/Editing_Checklist.md](Templates/Editing_Checklist.md) - Line-by-line checklist
•[ ] Completed clarity pass
•[ ] Verified technical precision
•[ ] Strengthened all transitions
•[ ] Reduced redundancy (target: 10% reduction)
•[ ] Varied sentence structure
•[ ] Corrected all grammar issues
•[ ] Verified all citations
•[ ] Completed final read-through
•[ ] Manuscript ready for review simulation

Previous weekNext week

Learning Objectives

•Eliminate ambiguity and unnecessary jargon

•Strengthen paragraph transitions and flow

•Vary sentence structure for readability

•Remove redundancy while maintaining completeness

•Perfect technical terminology and notation

•Apply consistent style throughout the manuscript

•Time separation (wait 24-48 hours between writing and editing)

•Format separation (edit on paper or different screen)

•Role separation (pretend you're editing someone else's work)

•Word choice (right word for meaning)

•Sentence structure (clear syntax)

•Paragraph structure (logical development)

•Section flow (coherent narrative)

•"It might be possible that perhaps the effect could be due to..."

•Better: "The effect is likely due to..." or "We attribute the effect to..."

•"superconducting qubit two-level system energy relaxation rate measurement"

•Better: "measurement of the energy relaxation rate in superconducting qubits"

•"The sample was prepared and then was measured and the results were analyzed"

•Better: "We prepared the sample, measured it, and analyzed the results"

•"We used RB to characterize the CZ gate in our transmon-based QPU"

•Better: Define acronyms on first use; explain technical terms

•Mark unclear sentences

•Note missing information

•Identify unsupported claims

•Check topic sentences

•Verify transitions

•Assess paragraph length

•Identify passive voice

•Find weak verbs

•Spot redundancy

•Check subject-verb agreement

•Verify reference format

•Confirm number consistency

•Is this sentence necessary?

•Does it say exactly what I mean?

•Is it as short as possible without losing meaning?

•Is the most important information prominent?

•Does it connect to surrounding sentences?

•**Topic sentence:** States the paragraph's main point (usually first sentence)

•**Support:** All sentences support the topic

•**Coherence:** Sentences connect logically

•**Necessity:** Paragraph contributes to section

•**Length:** Not too long (aim for 3-6 sentences in science writing)

•Before: "The data show that there is an increase in fidelity"

•After: "The data reveal a fidelity increase" or "Fidelity increased (Fig. 2)"

•"In the event that" → "If"

•"Due to the fact that" → "Because"

•"In order to" → "To"

•"At the present time" → "Now" / "Currently"

•"For the purpose of" → "For" / "To"

•Agent unknown or unimportant: "The sample was damaged during shipping"

•Agent obvious: "The samples were stored at 4 K" (obviously by researchers)

•Emphasis on action: "This effect was first observed in 1995"

•Spell out numbers below 10 unless with units: "three qubits" but "3 mK"

•Use SI units or field-standard equivalents

•Space between number and unit: "10 μs" not "10μs"

•Use proper symbols: "μ" not "u", "Ω" not "ohm" (in equations)

•Equations are part of sentences—they need punctuation

•Introduce equations: "The Hamiltonian is given by" followed by equation

•Define all variables when first introduced

•Reference equations by number: "Equation (3)" or "Eq. (3)"

•Define on first use: "quantum error correction (QEC)"

•After definition, use abbreviation consistently

•Common abbreviations may not need definition (e.g., DNA)

•Journal-specific conventions may apply

•Citations go after the claim, before the period: "...as shown previously [1]."

•Multiple citations: "[1-3]" or "[1, 2, 3]" depending on journal

•Self-citation: Use sparingly and appropriately

•Citing reviews instead of primary sources

•Missing recent relevant work

•Incorrect citation format for journal

•Highlight any sentence you had to read twice

•Mark any technical term that might be unclear to a general physics reader

•Identify sentences longer than 30 words

•List any ambiguous pronouns

•Verify every numerical value against data sources

•Check all equation derivations or references

•Confirm consistent notation throughout

•Ensure all claims are appropriately qualified

•Read only the first sentence of each paragraph in sequence

•Assess: Does this read as a coherent summary?

•Identify weak transitions

•Add or strengthen connecting language

•Target: Reduce manuscript by 10% without losing content

•Eliminate redundant phrases

•Combine short, related sentences

•Remove hedging language where inappropriate

•Identify every passive voice construction

•Convert to active where appropriate

•Find repeated sentence structures

•Vary sentence length (short for emphasis, longer for complex ideas)

•Run spell-check and grammar-check (but don't blindly accept)

•Verify every reference is correctly formatted

•Check that every citation is necessary

•Confirm reference numbers match bibliography

•Print manuscript and read aloud (catch errors ears find that eyes miss)

•Note remaining issues

•Make final corrections

•Prepare for Week 236 review simulation

•[Guide.md](Guide.md) - Detailed editing strategies

•[Templates/Editing_Checklist.md](Templates/Editing_Checklist.md) - Line-by-line checklist

•[ ] Completed clarity pass

•[ ] Verified technical precision

•[ ] Strengthened all transitions

•[ ] Reduced redundancy (target: 10% reduction)

•[ ] Varied sentence structure

•[ ] Corrected all grammar issues

•[ ] Verified all citations

•[ ] Completed final read-through

•[ ] Manuscript ready for review simulation