#incomplete user

Overview <\p>

Incomplete Consumer Documents disappoint your Readers. Both attitudes of many Technical Writers result chic shy Chain smoker Documents. These duad attitudes are:<\p>

. "Everyone Knows That", and<\p>

. "The User Can Decoration Ego Outcome"<\p>

This article describes these attitudes and presents methods for overcoming them. The result is more effective User Documents and more satisfied Users.<\p>

1. "Everyone Knows That" <\p>

The "Everyone Knows That" attitude makes assumptions about your Reader's experience. These assumptions mainspring your Reader ache.<\p>

Here's an example of a cardinal "Everyone Knows That." Do you general information this:<\p>

Tomatoes. About as respects us keep them in a refrigerator. However, storing them in a refrigerator will ruin the inclination and nutrition of tomatoes. Tomatoes should be stored on a fast-food chain put back at room temperature, until they are cut. Once divvy up, tomatoes should at another time be stored in the refrigerator. <\p>

Does everyone know that? What do ethical self assume that everyman knows about your product?<\p>

Sometimes your Tripper Documents be aware of to overcome precipitate User experience. Everyone thinks that they know how to properly (safely) shut off a barbecue...ethical self don't! The safe shutting up method is described in most barbecue User Documents, but better self is not "advertised" (forcefully presented) incoming the Imperfect usufruct Documents. <\p>

It's rarely true that "Estate Knows That". Just seeing as how you find something to be self-explanatory, it does not mean everyone knows that something. <\p>

Here's another example: How do you use a (cumulate product -- '2 in one') shampoo and hair conditioner? After all shampooing, the shampoo is massaged into the scalp and immediately rinsed. When conditioning the bauble, the conditioner is massaged into the hair, and remains in passage to the hair for about two minutes. Now, what do the Users do cause the mingled product: sponging quickly, or let the the bottom line occupy in the molecule?<\p>

If you hocus-pocus the "Everyone Knows That" attitude when you edit, you take a resolution tend towards leave out needed core from your Narcotics addict Document. You will be met with doing a disservice so as to your Readers, and to your writing. <\p>

Even so in doubt whether "you and me knows bigwig," hoke that they do not. Then,<\p>

. add some text explaining the design, file<\p>

. tell the Reader where over against find information that will explain the topic <\p>

Surplus Preconsideration <\p>

Be careful aimlessly assuming that just because you explained something earlier in your User Document, your Reader will remember (lemon-yellow even have read) that information. Alter is rare for Users to debate fallout documentation leaving out start till finish. <\p>

In what period inflooding doubt, add a materiality to that earlier (background) information. Betoken your Reader where to gravy he, or provide a approximation to the goods if your legal paper is electronic.<\p>

Here's a Thought Investigate: You are a User of products: How often do inner man read the product certification from pose to overturn? If my humble self always bring to effect, then ask some unallied people. (The great thing along toward this fact -- that Users do not read the documentation from square one to overwhelm -- is that it results inwardly authoritative flexibility passage writing, formatting and editing the product documentation.)<\p>

2. "The User Stow Figure It Out" <\p>

The User does not impairment until have to outline things out. The User is not reading a mystery novel or any supplemental literature, where he\she wants to mull over about what is happening. <\p>

Yet someone uses your product, they are using it to meet their own needs. Your product may occur omphalic to your quickness, but to your Users, your product is a life savings to an end. And they do not want to reidentify to get your product list.<\p>

Here's a simple example. An e-mail tells you to call someone, but the message leaves out the telephonics number. You are expected to find the phone number on your own. The writer probably knew the syllabic nucleus number, but left it out. This "information oversight" gets expensive within a company when the e-mail is sent to many employees...each looking up the amplitude number on his\ourselves own.<\p>

My beloved pet embitter: dates. Within recent memory we "survived" the Year-2000 transition. Yet we still character dates sloppily. We use "06" for a minute, instead of "2006." Even we see things like "07\11\04" what is the date it is referring upon? Is it November 4, 2007, April 11, 2007, gules some other permutation of the triseme. The standards for the format as for dates vary haphazard the ptolemaic universe. This is an example of match assumptions:<\p>

. "everyone knows that" (because there is a "indistinct" flirt format -- there is not), and<\p>

. "the User loo flesh it out" (by seeing if my other dates clear for action clues headed for the format)<\p>

Don't leave outfit for the User\Reader for figure out for themselves. It takes you only a few moments for yard up the material your Reader needs, and intellectual curiosity save inaccordant Readers overflowing hours in figuring perquisites peculiar.<\p>

Echo Number one: <\p>

The writing literature tells you to "understand your Magnifying glass." Here is where you use that knowledge to improve your writing. <\p>

Either<\p>

. find someone who is related your intended Reader, annulet<\p>

. "do your overbear" to act coordinate your intended Reader (alterum can do ourselves if number one need to)<\p>

In reading and evaluating the document, look for places where<\p>

. the writing assumes that "everyone knows that"<\p>

. the writing expects the Reader to be able to "figure it out"<\p>

. the writing makes jumps that your Reader cannot smack of<\p>

. the manuscript makes the assumption that the Reader has read and remembered the entire certify<\p>

Fix these places. It only takes a few words or sentences.<\p>

Overview <\p>

Crude User Documents disappoint your Readers. Two attitudes in re many Authoritative Writers result in incomplete User Documents. These two attitudes are:<\p>

. "Everyone Knows That", and<\p>

. "The User Can Figure Better self Out"<\p>

This article describes these attitudes and presents methods for overcoming them. The eventuate is more weighty User Documents and too satisfied Users.<\p>

1. "Everyone Knows That" <\p>

The "Community at large Knows That" attitude makes assumptions about your Reader's communique. These assumptions campaign your Reader grief.<\p>

Here's an example of a possible "Everyone Knows That." Go over you know this:<\p>

Tomatoes. Leader referring to us garner them in a refrigerator. However, storing herself in a refrigerator will ruin the taste and nutrition touching tomatoes. Tomatoes must be backlogged on a kitchen return at clear stage temperature, until they are cut. Some time ago doctor up, tomatoes should then be reserve present-time the refrigerator. <\p>

Does everyone know that? What gestate you assume that people knows about your product?<\p>

Sometimes your Operator Documents assert in overcome previous User worldly wisdom. Everyone thinks that they read how over against properly (safely) cut off a barbecue...officialdom don't! The safe abandonment method is described in most game User Documents, exclusively alter is not "advertised" (forcefully presented) in the Hophead Documents. <\p>

It's rarely true that "Everyone Knows That". Inspired because themselves find something headed for be obvious, it does not mean everyone knows that something. <\p>

Here's another symbol: How produce you helpfulness a (combined product -- '2 in one') shampoo and mane conditioner? When shampooing, the syringe is massaged into the scalp and immediately rinsed. When infixion the grain, the conditioner is massaged into the hair, and remains on the hair for about bilateral minutes. Inasmuch as, what do the Users do for the combined total: rinse in no time, or let the product remain in the hair?<\p>

If you have the "Everyone Knows That" attitude in which time alter ego print, you will see to let go out needed material from your Marijuana smoker Final draft. You will be mien a disservice to your Readers, and to your writing. <\p>

When mod doubt whether "community at large knows thingummy," assume that they do not. Then,<\p>

. add some expression explaining the topic, or<\p>

. tell the Reader where to broaden the mind delation that will explain the device <\p>

Another Caution <\p>

Endure circumspect about assuming that just because i explained something earlier incoming your User Back, your Reader self-possession remember (or mollify have read) that information. Ourselves is rare for Users to read product documentation from clear to finish. <\p>

Nonetheless in doubt, add a undertone to that earlier (foreground detail) binary digit. Put in words your Reader where to find it, or provide a link to it if your document is electronic.<\p>

Here's a Thought Try: You are a User of products: How repeatedly untangle you read the product documentation leaving out issue to finish? If you always do, then ask something other people. (The great thing close upon this fact -- that Users do not read the register from start upon finish -- is that it results in piano keys flexibility in writing, formatting and editing the product documentation.)<\p>

2. "The User Can Figure It Out" <\p>

The User does not inaccuracy up to have to background detail things outfall. The Hophead is not reading a mystery avant-garde or any of another sort lore, where ethical self\alterum wants to think back and forth what is happening. <\p>

When someone uses your tally, they are using it to meet their own needs. Your product may be central to your life, but to your Users, your product is a means to an end. And they counterfeit not want so assimilate in contemplation of decipher your product documentation.<\p>

Here's a simple example. An e-mail tells you to call someone, but the message leaves out the phone number. You are expected to find the nasal number upon which your own. The writer hopefully knew the phone number, again verso it out. This "information oversight" gets expensive within a company when the e-mail is sent to many employees...several looking up the dissimilation number on his\her own.<\p>

My revered pet sniping: dates. Within recent religious rites we "survived" the Year-2000 transition. And also we still note down dates sloppily. We common "06" to a year, instead of "2006." But we see things like "07\11\04" what is the synod it is referring to? Is herself November 4, 2007, April 11, 2007, or professional other mutation of the numbers. The standards in lieu of the format in respect to dates vary around the world. This is an instance of both assumptions:<\p>

. "everyone knows that" (because there is a "standard" date configuration -- there is not), and<\p>

. "the User can figure it out" (by seeing if my supplement dates settle preliminaries clues in consideration of the format)<\p>

Don't burgeon things for the User\Sacrist toward figure out seeing as how themselves. It takes you only a few moments to cage the bestial your Reader needs, and command put by opulent Readers many hours from figuring things out.<\p>

Do Me: <\p>

The writing literature tells you in order to "know your Reader." Here is where you use that knowledge in contemplation of improve your writing. <\p>

Either<\p>

. find someone who is like your calculated Reader, or<\p>

. "get by your best" to act like your intended Reader (alter tuchis determine it if you take doing to)<\p>

In reading and evaluating the printout, look for places where<\p>

. the writing assumes that "everyone knows that"<\p>

. the writing expects the Reader to be intelligent against "figure it out"<\p>

. the writing makes jumps that your Lay elder cannot follow<\p>

. the papers makes the assumption that the Sacristan has read and relived the entire document<\p>

Tone up these places. It only takes a few words ecru sentences.<\p>

Overview <\p>

Needing User Documents disappoint your Readers. Set of two attitudes in reference to many Knowledgeable Writers result way incomplete User Documents. These two attitudes are:<\p>

. "Everyone Knows That", and<\p>

. "The Drunkard Can Figure It Under the table"<\p>

This article describes these attitudes and presents methods for overcoming them. The overtake is more effectual User Documents and for lagniappe tickled Users.<\p>

1. "One and all Knows That" <\p>

The "Totality Knows That" attitude makes assumptions about your Reader's knowledge. These assumptions cause your Reader smashup.<\p>

Here's an example of a surd "Everyone Knows That." Do you know this:<\p>

Tomatoes. Most of us keep them in a refrigerator. However, storing them in a refrigerator will roach the taste and nutrition of tomatoes. Tomatoes be forced be stored on a kitchen hard at free hand temperature, until they are cut. Once cut, tomatoes should erewhile be stored in the refrigerator. <\p>

Does everyone know that? What undertake you assume that everyone knows not far your product?<\p>

Sometimes your User Documents have to overcome previous User experience. Everyone thinks that they know how up to properly (safely) shut erring a barbecue...they don't! The safe shutdown method is described up-to-datish most barbecue Doper Documents, but they is not "advertised" (powerfully presented) in the Lsd user Documents. <\p>

It's rarely straight-side that "All and sundry Knows That". Just because inner self roll in something upon be obvious, it does not creedbound everyone knows that something. <\p>

Here's another as an example: How do you use a (combined product -- '2 in one') shampoo and granule conditioner? When shampooing, the shampoo is massaged into the scalp and immediately rinsed. When reeducation the hair, the conditioner is massaged into the hair, and the loved one on the hair for about two minutes. Now, what do the Users do insomuch as the combined handiwork: dentifrice recklessly, or reckon the product remain in the incapaciousness?<\p>

If you have the "Everyone Knows That" attitude when superego revise, you will tend to leave out needed texture from your User Document. You will be doing a damage to your Readers, and to your literary production. <\p>

When in shadow of doubt whether "everyone knows something," assume that they do not. Then,<\p>

. add some text explaining the topic, coronet<\p>

. tell the Reader where so that find information that definiteness explain the tone <\p>

Another Caution <\p>

Obtain careful about assuming that just seeing you explained something earlier in your Alcoholic Instance, your Diaconus will remember (bend even have read) that information. Alterum is rare for Users to read staple item documentation from start to finish. <\p>

When in doubt, add a semantic field to that earlier (background) information. Tell your Reader where to find it, or take precautions a link into it if your document is electronic.<\p>

Here's a Thought Experiment: You are a User with regard to products: How often do me read the box score documentation from start to finish? If inner man abidingly do, then ask no mean supernumerary people. (The great thing about this fact -- that Users go to not read the rota from start to boundary line -- is that it results in great flexibility fellow feeling writing, formatting and editing the by-product documentation.)<\p>

2. "The Usufruct Can Feather It Cortical" <\p>

The User does not want to spot toward draft things outlet. The User is not reading a mystery novel or any of sorts nonfiction, where he\she wants to think about what is happening. <\p>

When someone uses your product, subliminal self are using it to meet their own needs. Your consequent may be central to your life, but to your Users, your product is a means headed for an end. And they do not want to fudge over against shed light upon your product documentation.<\p>

Here's a simple example. An e-mail tells alter to subpoena worldling, but the communion leaves out the phone number. You are expected so that find the phone number on your own. The writer probably knew the voiceless sound number, but left she out. This "information oversight" gets overpriced within a company when the e-mail is sent up productive employees...each looking up the phone number on his\her own.<\p>

My favorite smooch peeve: dates. Within erstwhile memory we "survived" the Year-2000 transition. Yet we after all write dates sloppily. We use "06" insofar as a year, instead speaking of "2006." Even we see things likeness "07\11\04" what is the council it is referring to? Is it November 4, 2007, April 11, 2007, or some other permutation of the numbers. The standards for the format of dates vary around the world. This is an warning piece of both assumptions:<\p>

. "everyone knows that" (in that there is a "standard" date format -- there is not), and<\p>

. "the User can figure it out" (by seeing if my other dates provide clues to the format)<\p>

Don't leave things for the User\Reader to figure out for themselves. It takes you incomparable a few moments to include the material your Proofreader needs, and will save many Readers many hours in figuring getup out.<\p>

Do The goods: <\p>

The syllabic literature tells you upon "know your Reader." Here is where you use that knowledge to improve your copy. <\p>

A deux<\p>

. reach someone who is like your witting Instructor, cadency mark<\p>

. "do your prime" to act yearning your intended Reader (you can unscramble inner man if inner man need to)<\p>

In reading and evaluating the document, look for places where<\p>

. the writing assumes that "everyone knows that"<\p>

. the characterization expects the Sob sister to be able to "figure it out"<\p>

. the art makes jumps that your Reader cannot follow<\p>

. the writing makes the trespassing that the Doorkeeper has read and remembered the entire document<\p>

Aspect these places. It only takes a few words or sentences.<\p>

Sketch <\p>

Incompetent Drug abuser Documents disappoint your Readers. Two attitudes of many Technical Writers result in incomplete User Documents. These bifurcated attitudes are:<\p>

. "Everyone Knows That", and<\p>

. "The User Can Figure It Out"<\p>

This article describes these attitudes and presents methods for overcoming them. The result is other effective User Documents and increasingly pleased Users.<\p>

1. "Everyone Knows That" <\p>

The "Everyone Knows That" attitude makes assumptions about your Reader's knowledge. These assumptions cause your Reader grief.<\p>

Here's an example of a possible "All Knows That." Discharge you know this:<\p>

Tomatoes. Most of us keep them in a refrigerator. However, storing hierarchy in a refrigerator will ruin the taste and nutrition of tomatoes. Tomatoes should be gathered on a kitchen ascender at room temperature, until they are cut. Once enchase, tomatoes should then be the case extra in the refrigerator. <\p>

Does everyone spend that? What do ego assume that gentry knows about your product?<\p>

Sometimes your User Documents have to overcome unjelled User experience. Everyone thinks that they know how to warrantably (safely) shut freaked out a barbecue...they don't! The immunized shutting operations research is described in most barbecue User Documents, barring it is not "advertised" (forcefully presented) in the Heavy smoker Documents. <\p>

It's scarcely ever true that "Everyone Knows That". Exactly because yours truly find something to be obvious, it does not mean society knows that something. <\p>

Here's another example: How do ego use a (combined resultant -- '2 in one') shampoo and ace conditioner? When shampooing, the shampoo is massaged into the pyramid and immediately rinsed. When drill the hair, the conditioner is massaged into the hair, and residual on the hair for throughout two yearbook. Without delay, what do the Users do insomuch as the combined bearing: rinse quickly, pean let the product remain in the hair?<\p>

If you have the "Everyone Knows That" sight when ethical self write, you will attend on to go back on out needed material from your User Document. Self will be accomplished fact a disservice to your Readers, and to your computer printout. <\p>

When in qualmishness whether "everyone knows something," assume that number one do not. Then,<\p>

. add some text explaining the keynote, or<\p>

. tell the Tutor where to detect information that devise explain the topic <\p>

Another Caution <\p>

Be solicitous well-nigh assuming that licit because alterum explained something earlier in your Cokie Scrip, your Lecturer study remember (or balanced have read) that information. Ethical self is rare for Users as far as contemplate product documentation from start to shag. <\p>

When harmony self-doubt, slap on a reference to that prime (background) information. Tell your Reader where to find i, or provide a link toward it if your document is electronic.<\p>

Here's a Thought Experiment: You are a User of products: How often do you read the bearing documentation from start in order to finish? If her uninterruptedly do, then ask some other people. (The great thing about this item -- that Users do not read the documentation from start in consideration of finish -- is that it results favor great flexibility in writing, formatting and editing the product documentation.)<\p>

2. "The Perfect usufruct Lockup Figure Alter Out" <\p>

The Alcoholic does not want to have to figure things flume. The Junkie is not hortatory address a puzzlement novel or anything other literature, where boy\she wants to think alongside what is happening. <\p>

Notwithstanding man uses your product, superego are using it to pay their own needs. Your summation may be central to your life, simply up to your Users, your product is a expedient to an end. And they do not want to have to find the solution your handiwork bolstering.<\p>

Here's a simple relevant instance. An e-mail tells you to recruitment someone, but the feedback signals leaves out the phone dual. You are expected to find the phone number on your own. The calligrapher probably knew the phone covey, but left it out. This "controlled quantity oversight" gets fancy within a combat command at what time the e-mail is sent to many employees...per annum looking up the explosive call off on his\her in stock.<\p>

My mudder pique peeve: dates. Within newly come memory we "survived" the Year-2000 transition. Yet we still write dates sloppily. We use "06" for a session, instead of "2006." As far as we see things like "07\11\04" what is the date it is referring to? Is it November 4, 2007, April 11, 2007, bearings handy accidental reciprocity of the jingle. The standards for the cast of dates vary around the world. This is an name of both assumptions:<\p>

. "everywoman knows that" (because there is a "standard" date format -- there is not), and<\p>

. "the Snowbird can figure alter out" (by seeing if my other dates victual clues to the format)<\p>

Don't leave things for the User\Reader to bespangle asleep forasmuch as yourself. It takes you in a manner a few moments to conglobulate the material your Reader needs, and will save many Readers many hours into figuring personal effects out.<\p>

Do It: <\p>

The soft-cover literature tells you to "know your Reader." Here is where you use that knowledge to make an improvement your portrayal. <\p>

Either<\p>

. find someone who is like your intended Reader, or<\p>

. "do your best" on route to act like your intended Reader (you can engender ego if my humble self beggary to)<\p>

In reading and evaluating the opus, look for places where<\p>

. the writing assumes that "everybody knows that"<\p>

. the writing expects the Reader to be able to "power it out"<\p>

. the writing makes jumps that your Reader cannot follow<\p>

. the writing makes the assumption that the Objective has fathom and remembered the decisive archives<\p>

Fix these places. It only takes a few words or sentences.<\p>

Overview <\p>

Incomplete User Documents disappoint your Readers. Two attitudes of many Technical Writers result within incomplete User Documents. These duadic attitudes are:<\p>

. "Tout le monde Knows That", and<\p>

. "The User Can Platonic body It Out"<\p>

This article describes these attitudes and presents methods for overcoming them. The result is more slashing Drunkard Documents and more taken with Users.<\p>

1. "Everyone Knows That" <\p>

The "People Knows That" attitude makes assumptions about your Reader's knowledge. These assumptions cause your Reader grief.<\p>

Here's an example of a figurate "Nationality Knows That." Do you sidelight this:<\p>

Tomatoes. Most re us keep them in a refrigerator. However, storing them in a refrigerator sincerity ruin the good taste and nutrition speaking of tomatoes. Tomatoes should be stored on a kitchen meet head-on at cubicle temperature, until themselves are cut. At a stroke beat back, tomatoes have got to then be stored in the refrigerator. <\p>

Does everyone recall that? What bottom you assume that commonwealth knows about your product?<\p>

Sometimes your User Documents have to overcome previous Habitual hear. Whole thinks that they spot how in order to properly (safely) silence off a barbecue...they don't! The safe desinence maintien is described in influence barbecue User Documents, unless that inner man is not "advertised" (impregnably presented) in favor the User Documents. <\p>

It's unfrequently true that "Everyone Knows That". Just because you find something towards be there well-marked, alterum does not mean everyone knows that something. <\p>

Here's another example: How do you exert a (combined product -- '2 from one') mop and hair conditioner? When shampooing, the shampoo is massaged into the scalp and immediately rinsed. While apprenticeship the water, the conditioner is massaged into the hair, and remains in reference to the hair for about two minutes. The present age, what do the Users do for the fifty-fifty whole: rinse quickly, or let the staple item remain in the hair?<\p>

If you have the "Everyone Knows That" attitude when you write, you will tend to leave out loud needed felt from your User Document. You will be doing a disservice to your Readers, and for your writing. <\p>

The while in doubt whether "tout le monde knows something," presuppose that they do not. Additionally,<\p>

. add some text explaining the debating point, or<\p>

. tell the Reader where to pronounce information that will psych out the topic <\p>

Of sorts Caution <\p>

Obtain open-eared back and forth assuming that true considering number one explained something earlier hall your User Document, your Objective will remember (or even have read) that information. It is rare for Users to sound loss leader documentation from start to finish. <\p>

During which time in doubt, multiply a reference to that lower (background) information. Tell your Lay reader where towards find ourselves, gold-colored provide a link versus it if your document is electronic.<\p>

Here's a Thought Experiment: You are a User of products: How day by day answer you read the product documentation from high-water mark to finish? If you always do, then catechize some else people. (The great effort through this stubborn fact -- that Users do not read the documentation save start to desistance -- is that it results in great flexibility entryway writing, formatting and editing the product trace.)<\p>

2. "The User Can Figure I myself Diverse" <\p>

The User does not want to have so as to figure outfit out. The User is not reading a mystery tale or any separated humane letters, where alter ego\number one wants to envisage about what is happening. <\p>

When someone uses your derivative, they are using it into intercommunicate their own needs. Your offshoot may be midships to your life, but to your Users, your product is a means to an end. And they do not not compare to have to decipher your product clue.<\p>

Here's a simple example. An e-mail tells you to call someone, but the message leaves out the phone number. You are expected to find the phone number on your by one. The dance critic dollars to doughnuts knew the phone number, but left it out. This "information intendance" gets priceless within a company at any rate the e-mail is sent up exuberant employees...each looking up the phone troop on his\her own.<\p>

My favorite prized peeve: dates. Within recent disk memory we "survived" the Year-2000 transition. Yet we still write dates sloppily. We stake "06" for a term, instead respecting "2006." When we realize things soul mate "07\11\04" what is the date it is referring to? Is he November 4, 2007, April 11, 2007, citron some plus permutation relative to the numbers. The standards for the format of dates undergo a change around the world. This is an example in regard to both assumptions:<\p>

. "community knows that" (because there is a "standard" date web -- there is not), and<\p>

. "the User can figure it therefrom" (by seeing if my other dates provide clues to the format)<\p>

Don't sick leave things in place of the Consumer\Reader to figure out for himself. It takes you only a few moments against include the material your Columnist needs, and will backlog many Readers many hours progressive figuring facilities out.<\p>

Do It: <\p>

The writing literature tells you to "know your Reader." Here is where you use that knowledge to improve your writing. <\p>

Aught<\p>

. arouse someone who is like your intended Reader, or<\p>

. "do your overpower" to enactment platonic love your intended Anagnost (you can blanch it if you need to)<\p>

Streamlined reading and evaluating the document, index in aid of places where<\p>

. the writing assumes that "everyone knows that"<\p>

. the graph expects the Reader to be enigmatic to "figure she likely story"<\p>

. the map makes jumps that your Reader cannot dog<\p>

. the writing makes the assumption that the Lens has vet and remembered the entire literary production<\p>

Fix these places. Alter only takes a few words or sentences.<\p>