Pronunciation for Tech Professionals: Words You Must Say Correctly<\/h1>\n
In today\u2019s global tech industry, English is the default language of communication. Whether you are speaking in a daily stand-up, presenting to a client, joining a global Zoom call, or explaining a bug to a colleague, your pronunciation directly affects how clearly your message is understood.<\/p>\n
You may have strong technical skills. You may write excellent code. But if people frequently ask you to repeat yourself, misunderstand key terms, or look confused during meetings, pronunciation may be the hidden problem.<\/p>\n
The good news? You do not need a \u201cnative\u201d accent. You only need clear, correct pronunciation of important technical words.<\/p>\n
This guide will help you understand:<\/p>\n
- \n
- \n
Why pronunciation matters in tech<\/p>\n<\/li>\n
- \n
The most commonly mispronounced IT words<\/p>\n<\/li>\n
- \n
How to pronounce them correctly<\/p>\n<\/li>\n
- \n
Practical strategies to improve your clarity<\/p>\n<\/li>\n<\/ul>\n
Let\u2019s begin.<\/p>\n
Why Pronunciation Matters in the Tech Industry<\/h2>\n
In tech, precision matters. A small difference in sound can create a big misunderstanding.<\/p>\n
Consider these examples:<\/p>\n
- \n
- \n
\u201ccache\u201d vs \u201ccash\u201d<\/p>\n<\/li>\n
- \n
\u201cqueue\u201d vs \u201ccue\u201d<\/p>\n<\/li>\n
- \n
\u201cdaemon\u201d vs \u201cdemon\u201d<\/p>\n<\/li>\n
- \n
\u201cdata\u201d vs \u201cdate\u201d<\/p>\n<\/li>\n<\/ul>\n
If your pronunciation is unclear, your listener may misunderstand the technical meaning. In a casual conversation, this might not be serious. But in professional settings, it can cause confusion, delays, or loss of credibility.<\/p>\n
Clear pronunciation helps you:<\/p>\n
- \n
- \n
Sound more confident<\/p>\n<\/li>\n
- \n
Reduce repetition<\/p>\n<\/li>\n
- \n
Improve meeting efficiency<\/p>\n<\/li>\n
- \n
Communicate better with global teams<\/p>\n<\/li>\n
- \n
Build professional trust<\/p>\n<\/li>\n<\/ul>\n
Remember: clarity is more important than accent.<\/p>\n
The Most Commonly Mispronounced Tech Words<\/h2>\n
Let\u2019s look at technical words that IT professionals often mispronounce.<\/p>\n
Cache<\/h3>\n
Correct pronunciation: \/k\u00e6\u0283\/ (sounds like \u201ccash\u201d)<\/p>\n
Common mistake: Saying \u201cka-shay\u201d or \u201cka-che\u201d<\/p>\n
\u201cCache\u201d comes from French, but in English, it is pronounced exactly like \u201ccash.\u201d<\/p>\n
Example:<\/p>\n
- \n
- \n
Incorrect: \u201cClear the ka-shay.\u201d<\/p>\n<\/li>\n
- \n
Correct: \u201cClear the cache (cash).\u201d<\/p>\n<\/li>\n<\/ul>\n
Queue<\/h3>\n
Correct pronunciation: \/kju\u02d0\/ (sounds like \u201ccue\u201d)<\/p>\n
Common mistake: Pronouncing every letter (\u201ckwe-ue\u201d)<\/p>\n
Even though it has five letters, \u201cqueue\u201d is pronounced as one simple sound: \u201ccue.\u201d<\/p>\n
Example:<\/p>\n
- \n
- \n
\u201cThe task is in the queue.\u201d<\/p>\n<\/li>\n<\/ul>\n
Data<\/h3>\n
Two acceptable pronunciations:<\/p>\n
- \n
- \n
\/\u02c8de\u026at\u0259\/ (\u201cday-ta\u201d)<\/p>\n<\/li>\n
- \n
\/\u02c8d\u00e6t\u0259\/ (\u201cda-ta\u201d)<\/p>\n<\/li>\n<\/ul>\n
Both are correct. American English often uses \u201cday-ta.\u201d British English often uses \u201cda-ta.\u201d<\/p>\n
The important thing is consistency. Choose one and use it consistently in professional communication.<\/p>\n
SQL<\/h3>\n
There are two correct pronunciations:<\/p>\n
- \n
- \n
\u201cS-Q-L\u201d<\/p>\n<\/li>\n
- \n
\u201csequel\u201d<\/p>\n<\/li>\n<\/ul>\n
Both are widely accepted. However, you should follow your company culture. Many enterprise environments prefer \u201cS-Q-L.\u201d<\/p>\n
Linux<\/h3>\n
Correct pronunciation: \/\u02c8l\u026an\u028aks\/ (\u201cLIH-nuks\u201d)<\/p>\n
Common mistake: \u201cLie-nux\u201d<\/p>\n
The first syllable sounds like \u201clin\u201d in \u201climit,\u201d not \u201cline.\u201d<\/p>\n
GIF<\/h3>\n
Two common pronunciations:<\/p>\n
- \n
- \n
\u201cgif\u201d (hard G, like \u201cgift\u201d)<\/p>\n<\/li>\n
- \n
\u201cjif\u201d (soft G)<\/p>\n<\/li>\n<\/ul>\n
This topic is debated. The creator of GIF says it should be \u201cjif.\u201d However, many professionals say \u201cgif\u201d with a hard G.<\/p>\n
In professional settings, both are understood. Choose one and be consistent.<\/p>\n
API<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\u201cA-P-I\u201d (most common)<\/p>\n<\/li>\n
- \n
Sometimes \u201capi\u201d (\u201cay-pee-eye\u201d combined smoothly)<\/p>\n<\/li>\n<\/ul>\n
Avoid pronouncing it as a single word like \u201cappy.\u201d<\/p>\n
GUI<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\u201cG-U-I\u201d (most common)<\/p>\n<\/li>\n
- \n
Some say \u201cgooey\u201d (informal)<\/p>\n<\/li>\n<\/ul>\n
In formal meetings, \u201cG-U-I\u201d is safer.<\/p>\n
JSON<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\u201cJay-sawn\u201d (\/\u02c8d\u0292e\u026as\u0252n\/ or \/\u02c8d\u0292e\u026as\u0259n\/)<\/p>\n<\/li>\n<\/ul>\n
Avoid:<\/p>\n
- \n
- \n
\u201cJuh-son\u201d<\/p>\n<\/li>\n
- \n
\u201cJays-on\u201d<\/p>\n<\/li>\n<\/ul>\n
Algorithm<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\/\u02c8\u00e6l\u0261\u0259\u02ccr\u026a\u00f0\u0259m\/ (\u201cAL-guh-ri-thum\u201d)<\/p>\n<\/li>\n<\/ul>\n
Common mistake:<\/p>\n
- \n
- \n
\u201cAl-go-rith-ME\u201d<\/p>\n<\/li>\n<\/ul>\n
The stress is on the first syllable: AL.<\/p>\n
Infrastructure<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\/\u02c8\u026anfr\u0259\u02ccstr\u028ckt\u0283\u0259r\/<\/p>\n<\/li>\n<\/ul>\n
Common mistake:<\/p>\n
- \n
- \n
Stressing \u201cSTRUCTURE\u201d too strongly<\/p>\n<\/li>\n
- \n
Breaking it incorrectly: \u201cinfra-STRUCT-ure\u201d<\/p>\n<\/li>\n<\/ul>\n
The stress is on IN.<\/p>\n
Business-Tech Words That Must Be Clear<\/h2>\n
Technical meetings include both engineering and business vocabulary. Mispronouncing these can weaken your professional image.<\/p>\n
Agile<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\/\u02c8\u00e6d\u0292a\u026al\/ (\u201cAJ-ile\u201d)<\/p>\n<\/li>\n<\/ul>\n
Common mistake:<\/p>\n
- \n
- \n
\u201cAh-jee-lee\u201d<\/p>\n<\/li>\n
- \n
\u201cAg-ill\u201d<\/p>\n<\/li>\n<\/ul>\n
Repository<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\/r\u026a\u02c8p\u0251\u02d0z\u0259\u02cct\u0254\u02d0ri\/<\/p>\n<\/li>\n<\/ul>\n
Stress is on \u201cPOS.\u201d<\/p>\n
Not:<\/p>\n
- \n
- \n
\u201crepo-sitory\u201d with equal stress on every syllable<\/p>\n<\/li>\n<\/ul>\n
Deployment<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\/d\u026a\u02c8pl\u0254\u026am\u0259nt\/<\/p>\n<\/li>\n<\/ul>\n
Stress on \u201cploy.\u201d<\/p>\n
Architecture<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\/\u02c8\u0251\u02d0rk\u026a\u02cct\u025bkt\u0283\u0259r\/<\/p>\n<\/li>\n<\/ul>\n
Common mistake:<\/p>\n
- \n
- \n
\u201cArchi-TECH-ture\u201d (overstressing TECH)<\/p>\n<\/li>\n<\/ul>\n
Vulnerable<\/h3>\n
Correct pronunciation:<\/p>\n
- \n
- \n
\/\u02c8v\u028cln\u0259r\u0259b\u0259l\/<\/p>\n<\/li>\n<\/ul>\n
Common mistake:<\/p>\n
- \n
- \n
\u201cvul-ner-A-ble\u201d<\/p>\n<\/li>\n<\/ul>\n
It has three syllables, not four.<\/p>\n
Words That Cause Confusion in Global Teams<\/h2>\n
Because tech teams are global, pronunciation differences can create confusion.<\/p>\n
Focus on Word Stress<\/h3>\n
English is stress-timed. That means one syllable in a word is stronger.<\/p>\n
Example:<\/p>\n
- \n
- \n
DEVeloper (not deVELoper)<\/p>\n<\/li>\n
- \n
MANagement (not manaGEment)<\/p>\n<\/li>\n
- \n
PREsent (noun) vs preSENT (verb)<\/p>\n<\/li>\n<\/ul>\n
Incorrect stress makes a word harder to understand, even if individual sounds are correct.<\/p>\n
Short vs Long Vowels<\/h3>\n
\u201cShip\u201d vs \u201cSheep\u201d
\n\u201cLive\u201d vs \u201cLeave\u201d
\n\u201cBit\u201d vs \u201cBeat\u201d<\/p>\nIn tech conversations, this matters:<\/p>\n
- \n
- \n
\u201cbit\u201d vs \u201cbeat\u201d<\/p>\n<\/li>\n
- \n
\u201clive server\u201d vs \u201cleave server\u201d<\/p>\n<\/li>\n<\/ul>\n
Practice distinguishing short and long vowel sounds.<\/p>\n
How to Practice Correct Tech Pronunciation<\/h2>\n
Improving pronunciation is not about talent. It is about training your ear and mouth.<\/p>\n
1. Use Online Dictionaries with Audio<\/h3>\n
Use trusted dictionaries that provide audio:<\/p>\n
- \n
- \n
Cambridge Dictionary<\/p>\n<\/li>\n
- \n
Oxford Learner\u2019s Dictionary<\/p>\n<\/li>\n
- \n
Merriam-Webster<\/p>\n<\/li>\n<\/ul>\n
Search the word and listen to both US and UK versions.<\/p>\n
Repeat immediately after hearing it.<\/p>\n
2. Record Yourself<\/h3>\n
This is uncomfortable but powerful.<\/p>\n
- \n
- \n
Record yourself explaining a technical concept.<\/p>\n<\/li>\n
- \n
Listen to it.<\/p>\n<\/li>\n
- \n
Compare with native pronunciation.<\/p>\n<\/li>\n<\/ul>\n
You will quickly notice unclear words.<\/p>\n
3. Shadowing Technique<\/h3>\n
Shadowing means listening and speaking at the same time.<\/p>\n
Steps:<\/p>\n
- \n
- \n
Find a tech talk or conference video.<\/p>\n<\/li>\n
- \n
Listen to one sentence.<\/p>\n<\/li>\n
- \n
Replay and speak with the speaker.<\/p>\n<\/li>\n
- \n
Match rhythm and stress.<\/p>\n<\/li>\n<\/ol>\n
Do this for 10 minutes daily.<\/p>\n
4. Focus on High-Frequency Words<\/h3>\n
You do not need to master every English word.<\/p>\n
Focus on:<\/p>\n
- \n
- \n
Words you say in meetings<\/p>\n<\/li>\n
- \n
Words in your presentations<\/p>\n<\/li>\n
- \n
Words related to your specialty<\/p>\n<\/li>\n<\/ul>\n
If you are a backend engineer, master:<\/p>\n
- \n
- \n
database<\/p>\n<\/li>\n
- \n
server<\/p>\n<\/li>\n
- \n
query<\/p>\n<\/li>\n
- \n
cache<\/p>\n<\/li>\n
- \n
authentication<\/p>\n<\/li>\n
- \n
authorization<\/p>\n<\/li>\n<\/ul>\n
If you are in DevOps, master:<\/p>\n
- \n
- \n
pipeline<\/p>\n<\/li>\n
- \n
deployment<\/p>\n<\/li>\n
- \n
container<\/p>\n<\/li>\n
- \n
Kubernetes<\/p>\n<\/li>\n
- \n
infrastructure<\/p>\n<\/li>\n<\/ul>\n
Prioritize relevance.<\/p>\n
Accent vs Pronunciation: Understand the Difference<\/h2>\n
Accent is natural. Pronunciation is clarity.<\/p>\n
You can keep your accent. The goal is not to sound American or British.<\/p>\n
The goal is:<\/p>\n
- \n
- \n
Clear vowel sounds<\/p>\n<\/li>\n
- \n
Correct stress<\/p>\n<\/li>\n
- \n
Correct technical terms<\/p>\n<\/li>\n<\/ul>\n
Many successful global tech leaders speak with strong accents. But their pronunciation is clear and consistent.<\/p>\n
That is the key difference.<\/p>\n
Common Pronunciation Habits to Avoid<\/h2>\n
Here are patterns that often reduce clarity:<\/p>\n
Adding Extra Vowels<\/h3>\n
Example:<\/p>\n
- \n
- \n
\u201cfilum\u201d instead of \u201cfilm\u201d<\/p>\n<\/li>\n
- \n
\u201ces-pes-ially\u201d instead of \u201cespecially\u201d<\/p>\n<\/li>\n<\/ul>\n
Practice consonant clusters:<\/p>\n
- \n
- \n
script<\/p>\n<\/li>\n
- \n
string<\/p>\n<\/li>\n
- \n
sprint<\/p>\n<\/li>\n
- \n
platform<\/p>\n<\/li>\n<\/ul>\n
Dropping Final Consonants<\/h3>\n
Example:<\/p>\n
- \n
- \n
\u201cdeplomen\u201d instead of \u201cdeployment\u201d<\/p>\n<\/li>\n
- \n
\u201cprojec\u201d instead of \u201cproject\u201d<\/p>\n<\/li>\n<\/ul>\n
Final consonants are important in English.<\/p>\n
Speaking Too Fast<\/h3>\n
When nervous, many professionals speak faster.<\/p>\n
Slow down slightly.<\/p>\n
Clear > Fast.<\/p>\n
How Correct Pronunciation Improves Career Growth<\/h2>\n
You may not realize how strongly pronunciation influences perception.<\/p>\n
Clear pronunciation makes you sound:<\/p>\n
- \n
- \n
More confident<\/p>\n<\/li>\n
- \n
More senior<\/p>\n<\/li>\n
- \n
More leadership-ready<\/p>\n<\/li>\n
- \n
More client-facing capable<\/p>\n<\/li>\n<\/ul>\n
If you want to:<\/p>\n
- \n
- \n
Lead meetings<\/p>\n<\/li>\n
- \n
Present architecture<\/p>\n<\/li>\n
- \n
Talk to international clients<\/p>\n<\/li>\n
- \n
Move into management<\/p>\n<\/li>\n<\/ul>\n
Clear pronunciation becomes a competitive advantage.<\/p>\n
It reduces friction in communication.<\/p>\n
And in global tech, reduced friction equals increased opportunity.<\/p>\n
Practical Weekly Plan for Improvement<\/h2>\n
Here is a simple 4-week improvement structure.<\/p>\n
Week 1: Awareness<\/h3>\n
- \n
- \n
Identify 20 technical words you use daily.<\/p>\n<\/li>\n
- \n
Check their correct pronunciation.<\/p>\n<\/li>\n
- \n
Write phonetic hints for yourself.<\/p>\n<\/li>\n<\/ul>\n
Week 2: Recording Practice<\/h3>\n
- \n
- \n
Record 3 short technical explanations.<\/p>\n<\/li>\n
- \n
Focus on stress and clarity.<\/p>\n<\/li>\n
- \n
Correct 5 repeated mistakes.<\/p>\n<\/li>\n<\/ul>\n
Week 3: Shadowing<\/h3>\n
- \n
- \n
Choose one tech conference talk.<\/p>\n<\/li>\n
- \n
Practice shadowing 10 minutes per day.<\/p>\n<\/li>\n
- \n
Focus on rhythm and natural stress.<\/p>\n<\/li>\n<\/ul>\n
Week 4: Real Meeting Application<\/h3>\n
- \n
- \n
Consciously pronounce key words clearly.<\/p>\n<\/li>\n
- \n
Slow down slightly.<\/p>\n<\/li>\n
- \n
Notice if people ask you to repeat less.<\/p>\n<\/li>\n<\/ul>\n
Track improvement.<\/p>\n
Small daily practice leads to big long-term clarity.<\/p>\n
Final Thoughts: Clarity Is a Professional Skill<\/h2>\n
In the tech industry, communication is as important as technical knowledge.<\/p>\n
Correct pronunciation of key technical words:<\/p>\n
- \n
- \n
Reduces misunderstanding<\/p>\n<\/li>\n
- \n
Increases confidence<\/p>\n<\/li>\n
- \n
Improves global collaboration<\/p>\n<\/li>\n
- \n
Strengthens professional presence<\/p>\n<\/li>\n<\/ul>\n
You do not need to eliminate your accent.<\/p>\n
You only need to ensure that the important words \u2014 the words that define your expertise \u2014 are pronounced clearly and correctly.<\/p>\n
Start with the words you say every day.<\/p>\n
Master them.<\/p>\n
Because in global tech communication, how you say something can be just as important as what you say.<\/p>\n
FAQs (Frequently Asked Questions)<\/h2>\n
Do I need a native accent to sound professional in tech?<\/h2>\n
No. You do not need a native accent to sound professional. In global tech teams, accents are normal and expected. What matters is clarity: correct pronunciation of key terms, consistent word stress, and speaking at a pace that listeners can follow. If people understand you the first time, your pronunciation is doing its job. Many senior engineers, managers, and founders speak with noticeable accents but communicate clearly because they pronounce important words consistently and use simple, well-structured sentences.<\/p>\n
Which tech words should I prioritize first?<\/h2>\n
Start with words you say every week in meetings, demos, or tickets. For most IT professionals, that list includes terms like \u201ccache,\u201d \u201cqueue,\u201d \u201cLinux,\u201d \u201calgorithm,\u201d \u201crepository,\u201d \u201cdeployment,\u201d \u201cAPI,\u201d \u201cJSON,\u201d and \u201carchitecture.\u201d If you work in DevOps, focus more on \u201ccontainer,\u201d \u201cKubernetes,\u201d \u201cpipeline,\u201d \u201cinfrastructure,\u201d and \u201cmonitoring.\u201d If you work in data roles, prioritize \u201cdataset,\u201d \u201cschema,\u201d \u201cquery,\u201d \u201cETL,\u201d and \u201canalytics.\u201d Practical priority beats trying to memorize hundreds of words you rarely say.<\/p>\n
Is \u201cdata\u201d pronounced \u201cday-ta\u201d or \u201cda-ta\u201d?<\/h2>\n
Both pronunciations are correct and widely used. \u201cDay-ta\u201d is common in American English, while \u201cda-ta\u201d is common in British English, but you will hear both in international teams. The best approach is consistency: choose one and use it regularly so your teammates recognize your pattern. If your company or team strongly prefers one version, match the local style to reduce friction during conversations.<\/p>\n
Should I say \u201cS-Q-L\u201d or \u201csequel\u201d?<\/h2>\n
Both are acceptable, and usage depends on context. Some teams say \u201csequel\u201d when talking about the language generally, while others prefer spelling it out (\u201cS-Q-L\u201d), especially in formal presentations or enterprise settings. If you are unsure, listen to how your senior engineers and stakeholders say it and follow the local norm. The goal is smooth communication, not winning a pronunciation debate.<\/p>\n
How should I pronounce \u201cJSON\u201d and \u201cAPI\u201d in meetings?<\/h2>\n
\u201cJSON\u201d is commonly pronounced \u201cJAY-sawn,\u201d and \u201cAPI\u201d is typically said letter by letter: \u201cA-P-I.\u201d In most professional settings, spelling out acronyms is safest because it avoids confusion with similar-sounding words. That said, fast speech can blur letters, so practice saying acronyms at a steady pace. Clear spacing between letters (\u201cA\u2026P\u2026I\u201d) can improve intelligibility on calls with weak audio or mixed accents.<\/p>\n
Is it \u201cgif\u201d or \u201cjif\u201d?<\/h2>\n
Both pronunciations exist in the tech world. The creator of the format has said \u201cjif,\u201d but many professionals prefer a hard \u201cg\u201d (\u201cgif,\u201d like \u201cgift\u201d). In practice, listeners usually understand either one, especially if the context is obvious. If your team consistently uses one pronunciation, follow the group. If not, choose the version you can say confidently and consistently.<\/p>\n
Why do people misunderstand me even when I know the correct words?<\/h2>\n
Misunderstandings often come from stress, rhythm, and speed rather than vocabulary. English relies heavily on word stress (one syllable is stronger), and incorrect stress can make familiar words sound unfamiliar. Another common issue is dropping final consonants (\u201cdeploymen\u201d instead of \u201cdeployment\u201d) or adding extra vowels (\u201car-chi-tec-ture\u201d with too many syllables). Also, speaking too quickly\u2014especially on Zoom\u2014reduces clarity. Slowing down slightly and stressing key words usually fixes many problems immediately.<\/p>\n
How can I learn the correct pronunciation quickly without wasting time?<\/h2>\n
Use a simple three-step routine. First, check a reliable dictionary with audio (US and UK options if available). Second, repeat the word out loud 10 times, focusing on stress and vowel length. Third, use it in a sentence you would actually say at work, such as \u201cClear the cache,\u201d \u201cPush to the repository,\u201d or \u201cDeploy to staging.\u201d This makes pronunciation practical and memorable. Keep a short list of \u201cmeeting words\u201d and review it before important calls.<\/p>\n
What is the fastest way to improve pronunciation for real meetings?<\/h2>\n
Record yourself explaining a technical topic for 60 seconds, then listen and identify unclear words. Next, practice shadowing: choose a short clip from a tech talk, replay one sentence, and speak along with the speaker to match rhythm and stress. Do this for 10 minutes a day. Finally, apply one improvement goal per meeting\u2014for example, \u201cToday I will pronounce \u2018queue\u2019 and \u2018cache\u2019 clearly.\u201d Small targeted changes create noticeable results.<\/p>\n
How do I handle correction if someone laughs or interrupts my pronunciation?<\/h2>\n
Stay calm and treat it as a communication moment, not a personal attack. You can respond professionally with a quick correction: \u201cThanks\u2014yes, I mean the cache,\u201d or \u201cRight, it\u2019s in the queue.\u201d Then continue your point. If the environment feels rude, focus on clarity and confidence rather than apologizing repeatedly. Over time, consistent pronunciation and steady delivery reduce interruptions. If you want, you can privately ask a trusted colleague how your pronunciation sounds on calls and which words cause confusion.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/article>\n<\/div>\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n