How to Stop Autocorrect from Ruining Your Technical Terms (Real Solutions That Work)

You’re typing a report about “JSON formatting” and autocorrect changes it to “JASON formatting.” Again. You’ve retyped “PostgreSQL” four times, and your phone insists it should be “postage sale.” I’ve watched this exact scenario play out dozens of times in our studio, usually followed by someone asking if they can just throw their device out the window.

I get it. Autocorrect was built for everyday writing, not specialized work. It doesn’t know your field’s vocabulary, and it certainly doesn’t care that you’re three paragraphs deep in explaining polymer synthesis or database architecture.

Here’s what I’ve learned after five years of helping students and remote workers fix this mess: You can’t just disable autocorrect entirely (though that’s tempting). You need a system that respects your technical language while still catching actual typos. This guide walks you through solutions I’ve tested on real projects, with real people, dealing with real frustration.

Let’s fix this.

Why Autocorrect Hates Your Technical Terms

Autocorrect operates on frequency. It learned from billions of everyday messages, emails, and texts. Words like “definitely” and “schedule” appear constantly, so the system recognizes them instantly.

Your technical terms? They’re statistical outliers.

When you type “epithelial,” autocorrect sees a rare word pattern. It assumes you meant something more common like “episcopal” or just made a typo. The system isn’t broken—it’s working exactly as designed, just not for your use case.

Here’s what makes technical terms particularly problematic:

• They often contain unusual character combinations
• They mix capital letters in non-standard ways (like JavaScript or pH)
• They include numbers, symbols, or special formatting
• They resemble common words closely enough to trigger corrections
• They vary slightly between style guides (is it “email” or “e-mail”?)

I’ve noticed three categories cause the most problems:

Programming languages and code: React, MySQL, API endpoints, variable names

Scientific terminology: Species names, chemical compounds, medical terms, research jargon

Industry-specific acronyms: GDPR, HVAC, STEM, B2B (which often become random words)

The solution isn’t one-size-fits-all. What works for a biology student differs from what works for a software developer.

Building Your Custom Dictionary (The Foundation)

Every device has a custom dictionary feature. Most people never touch it. That’s the problem.

I sit down with someone struggling with autocorrect, and the first thing I check is their dictionary. Empty. They’ve been fighting the same corrections for months without adding a single term.

Here’s how to actually use this feature:

On iPhone or iPad, go to Settings > General > Keyboard > Text Replacement. Don’t let the name fool you—this is your custom dictionary. Tap the plus sign and add your term in both fields. Yes, both. If you type “PostgreSQL” in the phrase field and “PostgreSQL” in the shortcut field, your device learns to leave it alone.

Android varies by manufacturer, but the path is usually Settings > System > Languages & Input > Virtual Keyboard > Gboard (or Samsung Keyboard) > Dictionary > Personal Dictionary. Add your terms to the language you type in.

Windows 10 and 11 hide this in Settings > Devices > Typing > Hardware Keyboard (scroll down) > Add a word to the dictionary. You can also right-click any underlined word and select “Add to dictionary.”

Mac users need to go to System Preferences > Keyboard > Text. Same principle as iOS—add your term to both columns.

Make it systematic, not reactive:

I tell people to spend 30 minutes doing this properly once. Open a recent document full of your technical terms. Copy every specialized word into your custom dictionary. Don’t wait for autocorrect to mess up again—add the words now.

You’ll need to maintain this list. New terms enter your field constantly. Set a monthly reminder to review your recent work and add any new vocabulary.

Text Replacement Shortcuts (The Game You Can Win)

Text replacement isn’t just for autocorrect problems. It’s how you type faster while keeping accuracy.

I use “pgsl” to type “PostgreSQL” because I’m tired of capitalizing it correctly every single time. My shortcut expands to the properly formatted version automatically.

Here’s the strategy that works:

Create shortcuts for your most-used technical terms. Make them intuitive but unlikely to trigger accidentally. I avoid single letters or common word fragments.

The shortcut should be faster than typing the full term but distinct enough that you won’t trigger it by accident. Don’t use “js” for JavaScript if you frequently type words like “jobs” or “jeans.”

Capitalization matters here:

Add both lowercase and properly capitalized versions. Your phone treats “api” and “API” as different entries. I learned this after watching someone add “http” to their dictionary, then get frustrated when “HTTP” still got corrected.

Some terms need multiple entries. “React” (the JavaScript library) and “react” (the verb) are different. Add “React” as a text replacement so autocorrect leaves the capitalized version alone.

Aggressive Autocorrect Settings (Dialing It Back)

Most platforms let you adjust how aggressive autocorrect behaves. The default settings assume you’re texting casually, not writing technical documentation.

iPhone and iPad settings to change:

Settings > General > Keyboard gives you three relevant toggles. “Auto-Correction” is the main switch—you can turn it off completely, but I don’t recommend that for most people. Instead, disable “Auto-Capitalization” if you work with terms that have specific capitalization rules. Turn off “Check Spelling” only if red underlines drive you crazy (they help me catch actual mistakes).

The “Predictive” toggle at the top controls that suggestion bar above your keyboard. I keep this on because it’s useful, but it does try to “help” with technical terms sometimes. Tap the quoted version of your word in the prediction bar (like “PostgreSQL”) to tell it you meant exactly what you typed.

Android (Gboard) adjustments:

Open any text field to bring up your keyboard. Tap the gear icon. Go to Text Correction. Here’s where it gets granular.

“Auto-correction” has three levels: Off, Modest, and Aggressive. Start with Modest. “Block offensive words” should be off for technical writing—I’ve seen it flag legitimate scientific terms. “Show suggestion strip” is worth keeping unless you need maximum screen space.

The “Personalization” section learns from your typing. Turn on “Use contacts” if you reference people by name in technical contexts. Gboard adapts faster when it can pull from multiple sources.

Windows and Word-specific settings:

Word has its own autocorrect separate from Windows. File > Options > Proofing > AutoCorrect Options opens the control panel.

I uncheck “Capitalize first letter of sentences” because technical writing often starts with lowercase terms or commands. “Correct TWo INitial CApitals” catches genuine mistakes while leaving abbreviations alone.

The “Replace text as you type” list shows every automatic replacement Word makes. Scroll through it. You’ll find some that conflict with your technical vocabulary. Delete those entries.

Application-Specific Solutions (Where You Actually Work)

You probably don’t type technical terms in Messages or Notes. You type them in your code editor, Word processor, or specialized software. Configure those tools properly and you solve 80% of the problem.

For developers and code editors:

VS Code, Sublime Text, and most modern editors have spell-check extensions you can customize. Install “Code Spell Checker” in VS Code (it’s the most popular). Open settings and add your technical terms to cSpell.userWords in your settings.json file.

This extension understands camelCase and snake_case. It won’t flag “getElementById” or “user_authentication_token” as errors.

For academic and scientific writing:

Word’s custom dictionary (mentioned earlier) syncs across your Microsoft account. Add a term once and it works on all your devices. Right-click any word, select “Add to Dictionary,” done.

Google Docs handles this differently. Right-click a flagged word and choose “Add to dictionary.” It saves to your Google account, not the document. The downside? Less control over organization.

For medical and scientific fields:

Many medical professionals I’ve worked with use expanded medical dictionaries. On iOS, you can add third-party keyboards like “Medical Spell Checker” that include terminology your default keyboard doesn’t know.

Scientific notation causes unique problems. Terms like “H₂O” or “5-HT₃” confuse autocorrect completely. I handle these with text replacement shortcuts: “h2o” expands to the proper formatted version with subscripts.

Platform-Specific Quirks and Workarounds

Each operating system has specific behaviors that drive people crazy once you notice them.

iOS loves learning the wrong lessons:

Your iPhone learns from what you type. Sounds great until it learns your typos. I’ve seen devices that consistently autocorrect “their” to “thier” because the user accidentally trained it wrong.

Reset this learning by going to Settings > General > Transfer or Reset iPhone > Reset > Reset Keyboard Dictionary. This wipes all learned behavior but keeps your text replacements. Do this if autocorrect seems to have learned all your mistakes.

Android manufacturer overlays:

Samsung keyboards behave differently from Google’s Gboard. OnePlus has its own quirks. If you’re following Gboard instructions but they don’t match your interface, check which keyboard you’re actually using.

Settings > System > Languages & Input shows all installed keyboards. You can switch between them and even download alternatives from the Play Store. SwiftKey offers better learning algorithms for technical terms than some stock keyboards.

Windows vs. Office autocorrect confusion:

These are separate systems that occasionally conflict. You can disable autocorrect in Word but still have Windows-level corrections happening. Check both locations if changes don’t seem to stick.

The Office autocorrect file lives in your user profile. If you need to transfer all your custom autocorrect entries to a new computer, you can copy the .acl file directly.

When You Need Nuclear Options

Sometimes you need autocorrect completely disabled for specific work.

I worked with a developer who coded in vim and never touched autocorrect, but struggled when documenting that code in Google Docs. We disabled autocorrect only in Docs using an extension.

Complete shutdown approaches:

Third-party keyboard apps let you disable features selectively. Gboard’s “Text Correction” settings include an “Off” option that kills autocorrect entirely. Your device still shows spelling suggestions but never changes what you type.

For iOS, you can’t install alternative keyboards that fully disable system-level autocorrect, but you can turn it off in Settings. The tradeoff? You lose all correction, even for obvious mistakes.

Document-specific solutions:

Word lets you disable autocorrect for individual documents. This helps when you’re writing something highly technical but don’t want to lose correction in other files.

Open the document, go to File > Options > Proofing > AutoCorrect Options, and uncheck the boxes. These settings save with the document. When you open it on another computer, autocorrect stays disabled.

Testing and Maintenance (Because Systems Drift)

Your autocorrect solution needs occasional maintenance. I check mine every few months because operating system updates sometimes reset preferences or change how features work.

Quick monthly check:

Type a sentence using your five most problematic terms. Does autocorrect leave them alone? If not, check your custom dictionary. Sometimes updates clear these entries.

Review your text replacement shortcuts. Are you still using all of them? I found “eeg” in my list months after I stopped working on that project. Clean out obsolete shortcuts—they clutter your predictions.

After major OS updates:

Always test autocorrect behavior after updating your phone or computer. I’ve seen iOS updates reset keyboard dictionaries without warning. Android updates sometimes change default keyboard settings.

Open your settings and verify everything looks correct. If something changed, you’ll catch it early instead of discovering it mid-project.

Real Scenarios I’ve Troubleshot

Case 1: Biology student with species names

She typed “Escherichia coli” about fifty times a day. Autocorrect insisted on “Escherichia cold” or “escherichia collie.”

We added both parts to her custom dictionary separately: “Escherichia” and “coli.” Then created a text replacement: “ecoli” expands to “Escherichia coli” with proper italics in apps that support rich text.

Problem solved in ten minutes. Months of frustration eliminated.

Case 2: Developer with framework names

His issue wasn’t autocorrect changing terms—it was the constant red underlines distracting him while coding. Every React component name, every npm package, flagged as misspelled.

We installed Code Spell Checker in VS Code and added his entire package.json dependencies list to the custom dictionary. The extension learned his project vocabulary. Red underlines disappeared except for actual typos.

Case 3: Medical resident documenting patient notes

Medication names got butchered constantly. “Metformin” became “met forming,” “lisinopril” turned into “listening pril.”

She couldn’t add hundreds of drug names manually. We found a medical keyboard extension for her phone and imported a medical dictionary package into Word on her laptop. The upfront setup took an hour, but it covered thousands of terms automatically.

What About Voice Typing?

Voice recognition has similar problems with technical terms. Dictation software learns from common speech patterns, not specialized vocabulary.

The solution parallels text autocorrect: train your voice recognition system.

For Dragon NaturallySpeaking users:

Create a custom vocabulary list. Dragon lets you import terms in bulk and even assign pronunciations. If you say “sequel” but mean “SQL,” you can teach it that relationship.

For built-in dictation (iOS, Android, Windows):

These systems learn from your typing over time. The more you manually type a technical term, the better voice recognition becomes at understanding it when you speak.

You can also speak punctuation and formatting: “capital J ava capital S cript” comes out as “JavaScript” if you articulate clearly.

Voice typing isn’t a perfect solution for technical work. I use it for rough drafts, then clean up terminology during editing. It’s faster than fighting autocorrect when you need to generate a lot of text quickly.

Frequently Asked Questions

Why does autocorrect keep changing words I’ve already added to my dictionary?

Your device might have multiple dictionaries active. Check if you’re using a third-party keyboard that maintains its own dictionary separate from your system dictionary. Also, some apps have their own spell-checking that overrides system settings—Microsoft Word is notorious for this. You need to add terms to both the system dictionary and the application’s custom dictionary.

Can I share my custom dictionary across devices?

On iOS and Mac, your dictionary syncs through iCloud if you have iCloud Keyboard enabled. Android syncs through your Google account if you’re using Gboard. Windows and Microsoft 365 sync autocorrect entries through your Microsoft account. If you work across different ecosystems (iPhone and Windows PC), you’ll need to maintain separate dictionaries or use cloud-based tools like Google Docs that sync to your account regardless of device.

Is there a way to temporarily disable autocorrect without changing settings?

Yes, on most keyboards. On iOS, when you see an autocorrect suggestion popup, tap the X next to it or tap the quoted version of your original word. This tells the system you meant what you typed. On Android with Gboard, tapping the word you actually typed (shown in quotes in the suggestion strip) does the same thing. For one-off technical passages, you can also paste text from a plain text editor where autocorrect doesn’t run.

What if I need different autocorrect settings for different projects?

Most operating systems only maintain one set of autocorrect preferences, but you can work around this. Use different applications with separate settings—Word for formal writing with autocorrect enabled, a code editor with it disabled for technical work. Some people maintain multiple user profiles on their computer, each configured differently. On mobile, you can switch between different keyboard apps depending on what you’re typing.

Fixing This Permanently

Autocorrect doesn’t need to be your enemy. I’ve spent enough time watching people battle their devices to know the real issue: nobody takes 30 minutes to configure things properly.

Your technical terms are legitimate words in your field. Treat them that way. Add them to your custom dictionary systematically, not reactively. Create text replacement shortcuts for terms you type constantly. Adjust your autocorrect sensitivity to match how you actually write.

The goal isn’t perfect autocorrect—it’s autocorrect that respects your expertise while still catching genuine mistakes. A system that helps instead of hinders.

Start with your custom dictionary today. Open your most recent technical document and add every specialized term. Then configure your most-used applications. Test everything with a few sample sentences.

You’ll spend less time fixing autocorrect mistakes and more time actually working. That’s the entire point.