Showing posts with label revision/editing/proofreading. Show all posts
Showing posts with label revision/editing/proofreading. Show all posts

Monday, March 17, 2008

In Soviet Russia, Paper Proofreads You!

By Travis Willmore

Say you have a classmate who trusts your writing judgment. We’ll call him Bob. There may come a time when Bob calls upon you to help proofread his work. This is a totally different situation from offering assistance in revising a paper, which has been dealt with at length here. Editing and proofreading involve targeted line-by-line changes to help fine-tune a paper. Excellent information on to proofread your own work, as well as that of others, can be found here.

If there is a recurring error in Bob’s work, it may be effective—and less discouragingly repetitive—if you note the first instance and mention that it recurs frequently throughout the paper. If the error is of uniform enough nature, he will be able to go through and make the corrections without having every individual instance marked. If he keeps capitalizing Coffee when you know that coffee is not a proper noun, you probably only need to mention it once.

Sometimes you will run across an unclear passage: one with more than one possible meaning. Rather than narrowing it down to a single specific meaning on your own, ask Bob what he intended the passage to mean before you proceed. If Bob writes, “I launched a cow from a wooden catapult on an English farm that must have been around since the 1580s,” does he mean the cow, the catapult, or the farm looks to be of 1580s vintage? Don’t just assume and fix the passage so it fits your assumption. Bob’s intention may well have been the less likely one.

You will also want to check with the writer about making changes when they deal with style preferences, rather than set-in-stone rules. If Bob doesn't use the serial comma (“this, this, and this” loses the second comma to become “this, this and this”), you have a situation in which either option is technically correct. In that case, it’s a good idea to check if Bob’s choices on the matter were intentional before making corrections that impose your own stylistic preferences.

More important than any of these individual techniques is the attitude you bring to proofreading when Bob calls you in to help fine-tune his work. Keep in mind that you want to be positive in your tone when pointing out problem areas, and recognize situations when the writer just wants you to add a coat of polish rather than rebuild the whole car. You will have a more satisfied Bob and he will have a more satisfying paper as a result.

Thursday, February 14, 2008

The Big Picture

By Travis Willmore

The big picture is often difficult to see when revising a paper. It’s easily obscured by minor spelling and punctuation issues that need editing—little distractions that get in the way of your concentration on improving the content of your paper. But wait…aren’t revision and editing basically the same thing?

Actually, no. Revision is something much more urgent than the red-underlined spellchecker stuff crying out “Edit me!” Revision should be applied in liberal doses before you even start to think about line-by-line editing. It means taking a look at that Big Picture we mentioned and asking yourself big questions like:

-Do the facts I mention in my paper support my main point?
-Do I, in fact, have a main point?
-Are my arguments adequately supported and my examples sufficiently explained?
-Is the information presented in an order that lets the reader clearly follow my thought process?
-Do my introduction and my conclusion complement each other?

Feel free to move major sections around or take out entire paragraphs if they don’t fit your overall vision. Swap your conclusion with your introduction if it makes for a stronger intro. Remember, nothing in your original draft is locked in. Any component can be modified or discarded in the interest of creating a more coherent whole.

This is why the editing, the nitty-gritty i-before-e-except-after-c work, can wait until revision is done. No need to obsess over the punctuation of a sentence in your first draft when you might cut out that sentence’s whole paragraph during revision. It’s better to save the final coat of proofreading polish until the larger form underneath is something worth polishing.

Wednesday, August 1, 2007

WRITING IS LIKE COFFEE


EDITING VS. REVISION

Revision and editing are practically the same thing, right? Dude, where do you get those ideas? Some people may think this (we aren’t necessarily implicating you), but editing and revision are very different processes. Assuming revision is simply changing words, fixing some commas, and moving one paragraph is a dangerous assumption when revising. This is editing. When writing teachers ask you for revision, they’re probably looking for re-vision, that is, to have the vision again. Yes, this sounds scary, but if you do it, you’ll impress your professor. Revision and editing are like coffee. Some days you’re doing pretty okay and maybe only need a tall. Sometimes if you’re feeling shlumpy, you may need a grande. Other days just suck, and you definitely need a venti. If major revision were coffee, it would be the venti.

What does that mean? Well, to start with, you may have to re-think your idea or even change your thesis. In its most radical stages, revision could entail completely rewriting your whole paper. This could happen if you finish your paper and realize the last sentence in your conclusion is really what you want to write. But it might mean that you haven’t clarified your thesis and simply need to rewrite the introduction so it’s coherent. It might mean that you have a super duper introduction, but got bored and rushed through the rest. Your ideas might not be fully developed, so you need to go back and unpack them. (i.e. rewrite these paragraphs.) You may have one awesome paragraph and some muddy ones. Perhaps that awesome paragraph really comes first and the rest just needs to be thrown out and rewritten. Occasionally, revision could be paragraph rearranging if you’ve already rewritten a lot, but we would consider this only a grande. Revision can mean a lot of things, but editing it is not.

What is editing then? If you are sick to death of your paper and can’t possibly think of anything to add or rewrite and find yourself simply fixing comma splices and changing words with a thesaurus, then you’re probably editing without knowing it. Even going through and fixing little lexical ambiguities falls under the heading of editing and proof reading. Things are good. You only need a tall.

Thursday, May 17, 2007

Own the Quote, Don't Let the Quote Own You


We're talking this week about effectively using quotes in research papers. Today, our suggestion is to make sure that rather than sprinkling quotes into your paper in isolated moments, you make sure to discuss any quote you use, so that the quote is serving your own argument, rather than the other way around.

Consider the following paragraph:

Sometimes things aren't so easy. "The problem with their plan," psychologist Jane Smith said, "is that they didn't account for the degree to which people are controlled by forces that we can neither prove the existence of nor agree on the function of. I'm talking, of course, about the unconscious, or the subconscious, depending on whether you're Freudian or Jungian about things, which makes a big difference, of course, if you study it closely, though Jung was a student of Freud's, but still, what I'm trying to impress upon you is that sometimes you just don't know" (312).
That paragraph is completely controlled by a quote--the writer hasn't managed to contribute anything to it other than a brief introductory sentence, and it's unclear what the writer wants us to understand from that quote. An example of a writer taking control of the use of a quote might be:
Dogs might salivate at the sound of a bell, but strict behavioral psychology often fails to capture the somewhat more complex behavior of human beings. We know, of course, that people are hungry for food, but other motivations behind human behavior can be maddeningly inscrutable. As Jane Smith notes, strict behaviorists "didn't account for the degree to which people are controlled by forces that we can neither prove the existence of nor agree on the function of" (312). Regardless of whether one prefers Freudian, Jungian, or some other psychology, most people agree that they have experienced moments in which deeper forces seemed to be pushing them to choose one action over another--and those forces aren't as simple as responding to a dinner bell.
All of that stuff--the quote, the paragraphs, etc.--was just made up off the top of our head. What we're trying to show, though, is that in the first example, a somewhat messy and not particularly focused quote had nevertheless been allowed to dominate a paragraph. In the second example, the quote has been trimmed to its useful point, and has been used within a context (and paragraph) controlled by the writer.

Wednesday, April 25, 2007

Three Tricks for Talking to Peers About Their Writing: Gravity, Summary, and More


As an extension of yesterday's post on working effectively in peer response groups, we thought we'd offer some more specific descriptions of ways to respond to a fellow student's writing that are specific and helpful, but not aggressive or critical. (We've stolen these ideas from a book called A Community of Writers, by Peter Elbow and Pat Belanoff.)

1. Point out "Centers of Gravity." The idea here is that after reading a piece, it's helpful to any writer to find out what specific sentences, words, or images were most memorable or leapt out at the reader. This isn't meant to be a formal version of making bland compliments before attacking the writer, though. A writer simply needs to know which sentences worked well, what images readers reacted to, and what material stands out in the piece. When discussing centers of gravity, then, you should try to be as specific and as exact as possible. Point to which sentence, or where in the piece things are working. If a writer knows what works, it can help him figure out how to revise other areas in the piece so that even more works.

2. Use summary and/or "sayback." Most pieces of writing have rough spots in them where a reader is uncertain or confused. Rather than telling a writer, "Your fourth paragraph was confusing," the method of summary/sayback suggests that you go ahead and summarize what you did understand in the paragraph. When you "say back" to the writer what you guessed about in your reading, the writer can then hear what you got right and what you didn't. With that knowledge, the writer can make much more effective decisions about how to fix that spot. If all the writer knows is that paragraph four doesn't work...well, there's no starting point for revision. If the writer knows it's actually sentence three that throws that paragraph into confusion, because readers are guessing that the writer means hedgehods cheat on each other instead of understanding that hedgehods never make promises in the first place, then the writer knows which sentence to fix, and how to fix it.

3. Describe what was almost said, or where you wanted more. It's common in an early draft for some sections of writing to be more fully developed than others. But if you say to someone, "Your fifth paragraph is hardly a paragraph! It's just a little fragment," then they're going to get angry. It's helpful, instead, to point out sections of a paper where a writer seemed like she was about to make an important point, but then moved on too soon. Likewise, there are times that a topic is greatly interesting, but a writer decides she better move on, because she's afraid not everyone wants to hear more about that. It can very useful to writers to hear where in a paper you, as a reader, really wanted to hear more about something. In either case, you're helping the writer see where further development is possible in the paper.

One of the strengths of these methods of feedback is that rather than being evaluative (suggesting that material in a draft is either "good" or "bad"), they're instead descriptive. Centers of gravity are good, but if they're not in the appropriate place in the paper or aren't fully developed, there's still work to be done with them. Summary and sayback of a confusing point is just description of a reading experience--the writer can decide what degree of reader uncertainty is okay, and what needs to be changed. And pointing to areas where something was almost said, or where more could be said, is neither praise nor criticism. It's effectively a way of saying, "This is good, but not quite finished."

And that is true of any early draft! By using some simple feedback methods like these, students often find it easier to have an informative, specific, and open discussion about their writing--and no one gets frustrated or has their feelings hurt.

Tuesday, April 24, 2007

But Who am I to Say? (Working in Peer Response Groups)


If you're in a course that involves a lot of writing, it's likely that you've spent some time in a peer response (or "workshop") group of some kind by this point in the term. Though peer response groups have all of the strengths and weaknesses of any kind of group work, there is the additional challenge in a writing group of feeling nervous about sharing your writing, as well as nervous about commenting on someone else's.

If this nervousness leads to people playing it safe, though--in other words, making only vague comments like "It was pretty good," or "Maybe fix the spelling on this one word here..."--then the time spent in your peer response group will feel unproductive.

Many students, however, say that they don't feel comfortable contributing to peer response sessions for yet another reason. They say, "Who am I to tell fellow students how to write? I'm not any more of an authority on writing than they are!" That's true, if you interpret your role in the response group only as that of a fellow writer.

If you'd like to have more valuable and more enjoyable peer response sessions, though--both as a commenter and as someone whose work is being commented on--you might think about your role in the group a bit differently. We have two main suggestions for working in peer respone groups:

1. Comment as a reader, not as a writer. No one wants to be told what to do, especially on their own work. That's why when a fellow student reads a paper you wrote and then starts to comment on it by saying, "Here's what you should have done...," you're likely to be unable to hear the rest of that comment beneath the roar of your own resentment. That comment is the comment of one writer telling another writer what to do.

When you comment as a reader, though, you can just say, "There was a paragraph on page 2 that confused me. I think the reason it confused me was..." Or: "I like the discussion you have about blind newts on page three, but it stopped too soon for me--I'd love to hear more about their mating habits." The writer is left free to make decisions about how she would like to address those comments, and the responder is able to simply describe his experience of reading the paper, without making value judgments as to whether the paper is "good" or "bad," or what "should" have been done.

And you don't have to be an authority on writing to describe your experience of reading something. If you made it into college, you're a perfectly good authority on reading.

2. Listen to comments as a writer, not as a reader. It's tempting, when receiving feedback on your work, to want to tell the group how they "should" have read your paper, or what your intended meaning was. That kind of response, though, is essentially a reader who knows the paper super-well (because she wrote it) correcting the reading of others. In psychology class, they call this "defensiveness." (Hint: The countermove to this is to say, "I find your labeling of my behavior as 'defensive' to be aggressively reductive of my thoughts and feelings, in that it defines my natural and healthy desire to defend myself as somehow 'abnormal' or 'unhealthy.'" Just please don't say that in writing group.)

It's more valuable as a writer simply to listen to the readers discuss your paper. Take some notes on what they talk about, and where they had thoughts in their reading of your work. It's highly unlikely that a peer is ever going to give a "false" description of their reading of your work--in other words, why would someone ever say, "The third paragraph confused me" if the third paragraph didn't actually confuse them? That would be bizarre. The members of your group will probably try their best to accurately describe their experience of reading your paper. If you listen, and take some notes, you can choose later how to address those issues when you revise.

We don't want to sound too radical here in the Writing Center, but let's just say this: If you're careful to keep track of when your role is that of a writer, and when it is that of a reader, you might actually find the peer response groups enjoyable and valuable. It's possible!

Monday, April 23, 2007

Spellcheck Stumbles Here!

In the first in a continuing series, we list errors Microsoft Word's "spellcheck" feature will not catch.

its for it's
led for lead
groan for grown
addition for addiction
atone for a tone
yore for your
sail for sale
mane for man
painting your room "Gobi Desert" when you suspect you should have gone with "Nubby Wool"


Those first eight items can be caught through proofreading. The last one you can just let go. "Gobi Desert" and "Nubby Wool" are pretty much the same color--no regret necessary.

Monday, March 12, 2007

In Praise of Ragged Drafts, Or: How Not to Be a Figure Skater


The end of term is nearing. There are a lot of final projects and final exams to deal with, and the deadlines are looming, and the deadlines are, for the most part, final. It's a time of heightened pressure.

It's hard to write under pressure. This is true even for professional writers. They get used to it and they develop strategies for it, but still: it's difficult. Students who have multiple classes, who might have a job as well, and who have various other responsibilities often have more pressure than even a professional writer. So today, we at the Writing Center would like to make a suggestion: Write a quick and ragged and imperfect and weird first draft of that final paper you're having a hard time getting started on.

We know. You have concerns about that. Or you just don't write that way. But hear us out.

First: If you let yourself write a quick, sloppy, ragged first draft, you will feel better on the day that you wrote it. If you stare at the computer screen for two hours and only have two paragraphs to show for it, it's frustrating and you feel like you still have that same writing task, only now you've lost two hours. If you write six ragged pages in two hours, you feel like you've produced some stuff.

Second: It's easier to get back into it when you come back to it again. (And yes, we're suggesting that you come back to it again.) If you come back to two paragraphs, you still have a mostly-empty computer screen in front of you. If you come back to five or six pages, you have a lot of writing there to work with. You can dive in and begin fixing, improving, moving, fine-tuning, and all of that, immediately.

Third: Most of the difference between "strong" writers and "weak" writers is that strong writers revise. They add, cut, move, refine, and correct. If you purposely write a quick and ragged draft that you know you won't turn in, then you know that you will engage in a revision process, as well. Because you have to. But that's good!

Fourth: You have less situational stress, should a "situation" occur. If you have some kind of unforeseen task arise or some other hitch in your plans, you know you at least have a draft of that writing assignment done. In an academic emergency, then, you still have choices. You could turn in your draft and know that although it's ragged, at least you completed the course. Or you could turn it in to your instructor and be able to show that despite your unforeseen stress, you truly HAVE been working on the assignment. (An instructor who can see that you've really been working on something is usually more comfortable granting you an extension than an instructor who can't tell if you've truly been thinking about it or if you're just making an excuse.) Or because you know that you have the ragged draft, you also know that if you suddenly have limited time, you can just clean that up as much as possible as quickly as possible, and be done.

Many student writers report a writing process that is fairly high-stakes: they write one draft, one time through. If something goes wrong in it they think, "Oh well--looks like this isn't going to turn out that great." This is essentially the model of a high-stakes figure skating competition: if the skater falls during the big routine, there's nothing to be done about it. The announcers lament how awful it is that the skater fell, but then speak about how she'll just have to pick herself up and try and go on and complete the routine as well as she can. No chance for gold now!

But writing does not need to be like figure skating. If you stumble through an awkward paragraph in your first draft, you can still go back! You can fix it! Gold is still possible!

If you're stuck, then, or you're staring at the screen, perhaps consider giving yourself permission to just write a ragged first draft. You'll know that the draft will only get better as you work on it more. And you'll be writing.