This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
Text replacement, replace-as-you-type or AutoCorrect is an automatic data validation function commonly found in word processors and text editing interfaces for smartphones and tablet computers. Its principal purpose is as part of the spell checker to correct common spelling or typing errors, saving time for the user. It is also used to automatically format text or insert special characters by recognizing particular character usage, saving the user from having to use more tedious functions.
Additional options include recognizing words with two initial capital letters (e.g. "EXample") and correcting them, capitalizing the first letters of sentences, and correcting accidental use of caps lock (e.g. eXAMPLE).
The replacement list for text replacement can also be modified by the user, allowing the user to use shortcuts. If, for example, the user is writing an essay on the industrial revolution, a replacement key can be set up to replace "ir" with "industrial revolution", saving the user time whenever they want to type it. For users with the patience, this facility can even be used to create a complete keyboard shorthand system, along lines similar to those of Dutton Speedwords, but with short forms instantly replaced by full forms.
Some stand alone programs allow global text replacement across the operating system, and apply to text typed into any other application.
The list of terms within the default Microsoft AutoCorrect application in Microsoft Word can be replaced by words, terms, expressions, etc., other than the default set. Doing so in a wise, comprehensive and strategic manner can immensely improve the keyboarding productivity and accuracy in high-production work settings.
To get the most from the autocorrect routine, one may best exploit the fact that the most common words typed are the best candidates for which to deploy shortcuts. For example, using "t" for "the" ; "w" for "with" ; etcetera can maximize the keystroke-to-production ratio.
Any system such as developing a technique requires a learning curve to achieve mastery, but experience in developing a database of expressions has proven that to ensure most effective use of autocorrect, shortcuts must be easy to recall.
For example, the threshold of characters in the chosen word is no less than three (3) except when the 2-letter word is within a longer expression, e.g., "aamof" for "as a matter of fact".
One technique in developing a system of large database of terms is using prefixes and suffixes in the formation of a shortcut.
For example, using the suffix "z" [mnemonic: expandZ] for the "asapz" to expand to "as "as soon as possible"
Whether one requires either a robust or moderate exploitation of the autocorrect, this feature may be best used by first deleting the default terms that are supplied by the manufacturer. Those default terms typically include those words most commonly mis-typed. Including those terms, e.g., "teh" for "the" invites careless and/or thoughtless actions whereas excluding them invites a learning process, or greater productivity.
In a robust exploitation of autocorrect, including chemical notation, the deployment could transcends the perceived "disadvantage" of autocorrect. The simple use of a shortcut suffix denoting chemical glossaries would be deployed. For example, using "campx" for "cAMP" and "camp¥" for "cyclic adenosine monophosphate" and "camp¥x" for "C10H12N5O6P" [with corresponding sub-script or super-script as needed] the shortcut "campx" with "cAMP"; furthermore if/when the full expression was needed, the developer could invoke ¥ to be the suffix for chemical notation, e.g., substitute . 
In certain situations, automatic corrections can cause problems. This is particularly so in technical and scientific writing. For example, the biochemical cyclic adenosine monophosphate is commonly referred to as "cyclic AMP", which in turn is abbreviated to "cAMP". A text replacement function may regard this capitalization to be erroneous, and so change it to "Camp", which in the context of biochemistry is incorrect. Older automatic-correction algorithms can cause problems even in nontechnical writing; the Cupertino effect was an example: cooperation (which some dictionaries would not recognize unless hyphenated co-operation) became Cupertino.
Some writers and organizations choose to consistently replace some words with others as part of their editorial policy, with occasionally unforeseen results. For example, the American Family Association chose to replace all instances of the word, "gay", on its website with the word, "homosexual". This caused an article about US Olympic sprinter Tyson Gay to be littered with confusing sentences such as, "In Saturday's opening heat, Homosexual pulled way up, way too soon, and nearly was caught by the field, before accelerating again and lunging in for fourth place."
Misuse of text replacement software is a staple practical joke in many schools and offices. Typically, the prankster will set the victim's word processing software to replace an extremely common word with a humorous absurdity, or an incorrectly spelled version of the original word. The growing use of autocorrection on smartphones has also led to popular websites and blogs where people post and share humorous or embarrassing cases of improper autocorrections. Deliberate AutoCorrect is when people write something and sarcastically "correct" their Deliberate AutoCorrect with an Asterisk followed with the sarcastic "correction".
- Professional experience in high-production, high-accuracy audio transcription service provision.
- Mary Ann Akers (2008-07-01). "Christian Site's Ban on 'G' Word Sends Homosexual to Olympics". Washington Post. Retrieved 2010-09-17.
- "Microsoft AutoCorrect Prank". Retrieved 2012-01-22.
- How to disable text replacement features (AutoFormat and AutoCorrect) in Microsoft Word 2007
- OOo Off the Wall: Domesticating Autocorrect
- A brief discussion on the history of code completion