Take the 2-minute tour ×
Writers Stack Exchange is a question and answer site for authors, editors, reviewers, professional writers, and aspiring writers. It's 100% free, no registration required.

Can you provide me with some techniques for minimizing redundancy in English sentence structure on three levels?

  1. The Document Level
  2. The Paragraph Level
  3. The Sentence Level

I'm trying to get better at making shorter documents with more meaning and work on perfecting my elevator pitch skills.

share|improve this question
add comment

1 Answer

The document level? meaning chapters and such? This has more to do with your understanding of the material, and less to do with the act of writing. You should have, in order, a title (along with date, author, etc), table of contents, abstract and definition of terms in the case of technical documents, a introductory chapter/part, the contents, a conclusion chapter/part and a bibliography in the case of technical documents.

As for the other two categories:

  1. Each time you want to write analogies write a metaphor instead — at most 5 words, and make sure it doesn't require explanation (it's a bad metaphor otherwise). Analogies are long and boring. When you mean to write a analogy, a lot of the time what you really intend is a metaphor.

  2. Don't explain yourself. What I mean is having follow up sentences like this one explaining what should have been "understood" in your sentences. It's better to write it out clearly: "don't write about what you're currently writing" or "avoid meta-writing." Eliminate the follow-up or the initial sentence to fix the problem when it appears (whichever one robs the other of it's thunder).

  3. Don't start a sentence with "However," "But," and so on; you can do so occasionally if it's for emphasis. I recommend using a semi-colon to link the two sentences together when they are related (like I have done in the previous sentence) or parentheses for a short note. Em dashes can also be used, but sparingly. If the sentence is not related, just simply start with the subject. You can also scrap the sentence altogether and rephrase it as a different kind of sentence, such as a rhetorical question opening the way to some new chain of thought.

  4. Avoid "pleonasms" (redundant or repeated terms). It doesn't have to happen in the same sentence; if you emphasize something in one sentence try not emphasize it again (just in a different way) in your next sentences. No need to beat on a dead horse.

    However that's not to say true pleonasms aren't something you should worry about: 12 midnight => midnight, 12 noon => noon; 3 am in the morning => 3 am; biography of her life => biography; each and every => each; end result => result; personal opinion => opinion; personally, I think/feel => I think/feel; cooperate together => cooperate; etc etc.

  5. Any word, expression or sentence that doesn't add anything or change the sentence is just fluff, and you should omit it. Reduce clauses to phrases, phrases to single words. Remove intensifiers that don't intensify. Avoid words such as really, very, quite, extremely, severely (intensifiers). And more importantly, use your own words. Using "fancy wording" just results in writing clichés, which makes your writing dull. (more info and examples) So when is it okay to use a cliché construct? When it's a saying or otherwise a very popular, and well understood, metaphor.

You can find simple exercises on the net.

share|improve this answer
    
Nitpick: You used the semi-colon incorrectly at the beginning of item 3. "Unless it's for emphasis" is not an independent clause, so you can't attach it to the previous independent clause with a semi-colon. You need a comma there or you have to reword your clause. Separately, American punctuation rules would put the comma inside the quotes of "However," and "But," where you have them outside; the same goes for the period after "pleonasms." [/editor] Other than that, plenty of good advice here. :) –  Lauren Ipsum Mar 4 '11 at 15:20
    
@Lauren Ipsum, I've converted it to community wiki, so feel free to edit away. :) –  srcspider Mar 4 '11 at 15:25
    
thanks. :) fixing now. actually fixing quite a bit. sorry. –  Lauren Ipsum Mar 4 '11 at 15:46
    
No just at the document level, not chapters and such. What I mean is "within a single document or single blog post". –  leeand00 Mar 4 '11 at 16:38
    
@leeand00, first paragraph should be an introduction or, if feasible, an abstract; the purpose is to ease your readers in not (necessarily) to make a summary. Everything in-between is your own business. At end you should have some sort of conclusion; not necessarily a verbose one, simple facts will do (particularly for technical writing) and simply wrapping things up with a opinion is sufficient for others. Just my take on it. –  srcspider Mar 4 '11 at 16:56
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.