add checklist item: delete redundant paragraph-ending sentences
All checks were successful
check / check (push) Successful in 8s
All checks were successful
check / check (push) Successful in 8s
This commit is contained in:
@@ -404,43 +404,48 @@ passes, because fixing one pattern often introduces another.
|
||||
|
||||
### Pass 3: Paragraph and Section-Level Review
|
||||
|
||||
21. Check paragraph lengths across the piece and verify they actually vary. If
|
||||
21. Review the last sentence of each paragraph. If it restates the point the
|
||||
paragraph already made, delete it. Models frequently close paragraphs with a
|
||||
summary sentence that adds nothing, treating each paragraph as a
|
||||
self-contained unit that needs its own conclusion.
|
||||
|
||||
22. Check paragraph lengths across the piece and verify they actually vary. If
|
||||
most paragraphs have between three and five sentences, rewrite some to be
|
||||
one or two sentences and let others run to six or seven.
|
||||
|
||||
22. Check section lengths for suspicious uniformity. If every section is roughly
|
||||
23. Check section lengths for suspicious uniformity. If every section is roughly
|
||||
the same word count, combine some shorter ones or split a longer one
|
||||
unevenly.
|
||||
|
||||
23. Check the first word of every paragraph for chains of connectors ("However,"
|
||||
24. Check the first word of every paragraph for chains of connectors ("However,"
|
||||
"Furthermore," "Moreover," "Additionally," "That said"). If more than two
|
||||
transition words start consecutive paragraphs, rewrite those openings to
|
||||
start with their subject.
|
||||
|
||||
24. Check whether every argument is followed by a concession or qualifier. If
|
||||
25. Check whether every argument is followed by a concession or qualifier. If
|
||||
the piece both-sides every point, pick a side on at least some of them and
|
||||
cut the hedging.
|
||||
|
||||
25. Read the first paragraph and ask whether deleting it would improve the
|
||||
26. Read the first paragraph and ask whether deleting it would improve the
|
||||
piece. If it's scene-setting that previews the argument, delete it and start
|
||||
with paragraph two.
|
||||
|
||||
26. Read the last paragraph and check whether it restates the thesis or uses a
|
||||
27. Read the last paragraph and check whether it restates the thesis or uses a
|
||||
phrase like "at the end of the day" or "moving forward." If so, either
|
||||
delete it or rewrite it to say something the piece hasn't said yet.
|
||||
|
||||
### Pass 4: Overall Texture
|
||||
|
||||
27. Read the piece aloud and listen for passages that sound too smooth, too
|
||||
28. Read the piece aloud and listen for passages that sound too smooth, too
|
||||
even, or too predictable. Human prose has rough patches. If there aren't
|
||||
any, the piece still reads as machine output.
|
||||
|
||||
28. Check that the piece contains at least a few constructions that feel
|
||||
29. Check that the piece contains at least a few constructions that feel
|
||||
idiosyncratic: a sentence with unusual word order, a parenthetical that goes
|
||||
on a bit long, an aside only loosely connected to the main point, a word
|
||||
choice that's specific and unexpected.
|
||||
|
||||
29. Verify that you haven't introduced new patterns while fixing the original
|
||||
30. Verify that you haven't introduced new patterns while fixing the original
|
||||
ones. Run the entire checklist again from the top on the revised version.
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user