Natural Alternatives to Textbook English

Learning outcomes

You learned to greet people with “How do you do?”, to ask for things with “I would like to request that you”, and to thank them with “Thank you very much indeed.” Then you joined a real team, opened Slack, and noticed that nobody talks like that. Your messages were correct, but they stood out, the way a tuxedo stands out at a barbecue. The problem was never your grammar. It was that the textbook taught you one phrase per function and never told you it was the formal one. This page gives you the everyday alternatives, organized by what you are trying to do, so you can match the phrase to the situation instead of always reaching for the stiff one.

After studying this page, you can:

• Explain why textbook phrases are mis-registered rather than wrong, and when each one is still the right choice.
• Swap the stiff textbook version for a natural alternative across nine common functions: greeting, requesting, thanking, agreeing, giving an opinion, adding a point, apologizing, checking understanding, and closing.
• Keep two or three alternatives per function on hand, so you are not stuck with a single phrase.
• Choose how casual to go by reading your audience and your channel.
• Recognize a few American and British differences (Cheers, You alright?) and avoid the most common over-formality mistakes.

Before we dive in

Picture two messages sent to the same teammate, five minutes apart. The first reads: “Dear Sam, I would like to request that you review my pull request at your earliest convenience. Thank you very much indeed.” The second reads: “Hey Sam, could you take a look at my PR when you get a sec? Thanks!” Both are polite. Both are grammatical. But the first one makes Sam wonder if something is wrong, because that much formality between equals signals distance, or stiffness, or even quiet annoyance. The second sounds like a normal human being asking a normal favor.

The textbook handed you the first one. Not because it is bad English, but because textbooks teach the safe, formal, written version of each function and rarely flag it as formal. You were given “Furthermore” but not “Also,” “I sincerely apologize” but not “Sorry about that,” “Do you understand?” but not “Does that make sense?” So when you reach for the only phrase you were taught, you reach for the formal one every time, even in chat, even with a friend, even when the moment called for something light.

This page is a phrasebook in reverse. Instead of teaching you the impressive phrase, it teaches you the everyday alternatives that natives actually use, sorted by function: greeting someone, asking for something, saying thanks, agreeing, giving an opinion, and so on. The point is not to abandon formal English. It is to give you a small set of options for each job, so you can pick the one that fits. To do that well, you need the idea in the next section first.

Mental Model: mis-registered, not wrong

The instinct is to file textbook phrases under “wrong” once you discover natives do not use them. That model is itself wrong, and it will lead you to over-correct, scrubbing all formality out of your English and sounding too casual in serious moments. The better model is that these phrases are mis-registered, not mistaken.

Register is the level of formality and the setting a phrase belongs to (the foundations page register and tone, the real axes gives the full picture). Every phrase carries a register the way a word carries a meaning. “I would like to request that you” is not broken English; it is high-register English, perfectly at home in a formal letter, a legal notice, or a message to a senior person you have never met. It only sounds wrong when you drop it into a casual chat, where its register clashes with the setting, like wearing hiking boots to a wedding. The boots are fine. The occasion is not.

This reframes the whole page. You are not replacing bad phrases with good ones. You are widening your range, from one phrase per function to several, each tagged with where it fits. Once you hold the formal and the casual versions side by side, choosing between them becomes a quick read of the situation rather than a guess.

Breaking it down

1. The swap table, organized by function

The fastest way to see the pattern is all at once. Each row below takes one communicative function, shows the textbook version you were probably taught, gives two or three natural alternatives, and names the register each alternative fits. Read it as a menu, not a set of corrections: the textbook column is not a list of mistakes, it is the formal end of each row.

Two things to notice as you scan. First, every textbook phrase has a clear home: it is the version you would still use in a formal letter, a cover note, or a first message to someone senior. It was never wrong; it was just narrow. Second, most functions have more than one natural alternative, and they are not interchangeable. “Could you” and “My bad” are both natural, but one is neutral and one is very casual. The rest of this section walks through the rows in groups, so you can hear the difference and learn the boundaries.

2. Greetings, requests, and thanks

Start with the three functions you use most. Greetings first. “How do you do?” is not a question about your day; it is a formal ritual opener, and in everyday speech it has almost vanished. Natives open with “Hi” (safe everywhere, in writing or speech), “Hey” (warmer, casual, for people you know), or a light “How’s it going?” or “How are you doing?”, which are greetings, not real questions, so the expected reply is a quick “Good, you?” rather than an actual status report.

Requests are where over-formality hurts most, because “I would like to request that you” is so heavy that it can sound cold or even passive-aggressive between equals. The natural ladder runs from casual to polite: “Can you send me the file?” (casual, direct), “Could you send me the file?” (the neutral default, slightly softer), “Would you mind sending me the file?” (more polite, good for bigger asks), and “Do you think you could send me the file?” (softest, for a real imposition). Note that the softer the request, the more the verb form shifts: “Would you mind” takes the “-ing” form (“sending”), not the base form.

Thanks scale the same way. “Thank you very much indeed” is correct but belongs to formal writing; in speech it can sound theatrical. Everyday thanks run “Thanks!” (light), “Thanks so much” (warm, very common), “Thanks a lot” (warm, but watch your tone, because said flatly it can read as sarcastic), and “Thanks, appreciate it” (warm and slightly more grateful). British speakers add “Cheers” as a casual thank-you, which we return to in the American and British notes below.

3. Agreeing, opinions, and additions

Agreeing is a function the textbook barely covers, so learners often fall back on the full sentence “You are completely right,” which is correct but lands as heavy and a little formal for a quick exchange. Natives agree in short bursts: “Exactly” (you have hit the precise point), “Good point” (acknowledging the other person’s contribution), “Totally” and “For sure” (casual, enthusiastic), and “Makes sense” (calm agreement that you have understood and accept it). These are not lazy shorthand; they are the normal currency of conversation, and using the full sentence every time sounds stilted.

Opinions show the same gap. “In my opinion” is fine in an essay but stiff in speech and chat, where it can sound like you are giving a formal verdict. The natural openers are “I think” (the neutral workhorse), “I’d say” (slightly softer, more tentative), “Honestly” (signals frankness, that you are about to be candid), and “If you ask me” (casual, a touch opinionated). Reach for “I think” as your default and you will rarely sound off.

Additions are a classic textbook trap. You were taught “Furthermore” and “Moreover” to add a point, and they are genuinely good in formal writing. But in speech and chat they sound like you are reading from a report. The everyday versions are “Also” (neutral, fits anywhere), “Plus” (casual), “On top of that” (casual, adds emphasis), and the very informal “And another thing” (usually when listing complaints). The lesson is not to delete “Furthermore” but to keep it in essays and use “Also” when you talk.

4. Apologizing, checking, and closing

Apologies carry real register weight, because the wrong level can make a small slip sound like a crisis or a real failure sound flippant. “I sincerely apologize” is the formal version, right for a written apology to a customer or after a serious mistake. For everyday slips, natives say “Sorry about that” (neutral, warm, the safe everyday choice) or, among peers only, the very casual “My bad” (acknowledging a small error you caused). Use “My bad” with a manager or a client and it reads as too breezy for the setting.

Checking understanding is a place where the textbook phrase can quietly offend. “Do you understand?” sounds like you doubt the other person’s intelligence, because it puts the burden on them. Natives flip it onto themselves: “Does that make sense?” asks whether you explained it well, not whether they are capable of following. The casual versions are “Make sense?” and “Following me?”. The shift is subtle but important, because the polite version protects the listener’s face.

Closings round out a message. “I am looking forward to hearing from you” is the formal email sign-off, still correct in a job application or a first contact with a client. The lighter versions are “Looking forward to it” (warm, semi-formal), “Talk soon” (casual, friendly), and “Let me know” (casual, when you want a reply or a decision). Match the closing to how you opened: a “Hey” at the top and a formal “I am looking forward to hearing from you” at the bottom is a register mismatch within a single message.

5. Choosing how casual to go

You now have several alternatives per function. The remaining skill is choosing among them, and that choice is driven mainly by two things: who you are talking to and which channel you are using. The flowchart below gives a first pass. Read who your audience is, then let the channel nudge the setting, and you land on a register.

The flowchart carries one lesson worth saying plainly: the most casual options (Hey, My bad, Talk soon) are safe mainly in one corner, a peer in a chat. As you move toward seniority, external contacts, or a permanent written record, you slide toward the neutral middle, not all the way to the textbook formal version. The textbook phrasing comes back only at the far end, a first contact, a sensitive topic, a formal document. Most workplace messages live in the neutral middle, which is why “Could you,” “Thanks so much,” and “Does that make sense?” are such reliable defaults: they fit almost everywhere. For the deeper logic of reading a situation, see register and tone, the real axes.

Now test the read on a concrete case.

6. American and British notes

A few of these alternatives split along American and British lines, and knowing which is which keeps you from sounding misplaced. “Cheers” is the clearest case. In British English it is a casual, friendly thank-you (“Cheers for the help!”) and also a casual sign-off at the end of a message. American speakers mostly use “Cheers” only as a toast with drinks, so a British “Cheers, mate” as a thank-you can briefly confuse an American reader.

Greetings differ too. The British “You alright?” (often written “Y’alright?”) is a casual greeting, the equivalent of “How’s it going?”, and it does not mean the speaker thinks something is wrong with you. An American hearing “You alright?” may take it as genuine concern, as if they looked upset. The reverse holds for the American “What’s up?”, which is a casual greeting, not a real question, where a literal answer (“Up? Nothing.”) misses the point.

Common mistakes

The first mistake is the one this whole page targets: using formal textbook openers in casual settings. Greeting a teammate in chat with “How do you do?”, asking a peer with “I would like to request that you,” or thanking a friend with “Thank you very much indeed” is not wrong English, but it is mis-registered, and it makes you sound stiff or distant when you meant to be friendly. The fix is to keep the everyday alternatives ready and reach for them by default in casual channels.

The second mistake is the opposite, and it is what happens when you over-learn this page: scrubbing all formality out and going too casual everywhere. “My bad” to a client, “Hey” in a job application, or “Talk soon” at the end of a formal proposal swings the register too far the other way. Textbook English is mis-registered, not wrong, which means the formal versions are still the right choice in formal settings. The goal is range, not a permanent switch to casual.

The third mistake is learning only one phrase per function. If “Thanks so much” is the only thank-you you know, you are as stuck as you were with “Thank you very much indeed,” just stuck in a different spot. The whole value of the swap table is having two or three options per function, each tagged with its register, so you can fit the phrase to the moment. Collect alternatives the way you collect collocations, as small sets with their settings attached.

The fourth mistake is ignoring the channel. The same phrasing that is right in a document is too stiff in chat, and the same phrasing that is right in chat is too loose in a signed document. Let the channel pull the register: looser in a quick message, tighter in a permanent written record, even with the same person.

Mastery Questions