MAP Language Usage common mistakes
MAP Language Usage · Understand the traps and how to avoid them.
Choosing a word that fits the sentence's general topic but ignores the grammar of the surrounding clause, such as picking a noun form where the blank needs a verb or adjective (e.g., selecting 'success' to fill a slot that requires 'succeed').
Candidates read for meaning first and stop once a word 'sounds right' topically, without checking what part of speech the sentence structure demands at that position.
What to do instead
Before looking at the answer choices, label the blank's required part of speech by finding the subject and main verb of the clause. Then eliminate any option whose form does not match, and only afterward compare remaining options for meaning.
Treating a passage-based editing question as a standalone sentence question, revising the underlined sentence without rereading the sentence before and after it.
It is faster to read only the marked portion, and the sentence often makes sense in isolation, so the candidate never notices that the revision breaks a pronoun reference or contradicts an adjacent sentence.
What to do instead
Always read at least one full sentence before and after the target. For each proposed revision, check pronoun antecedents, transition logic, and verb tense against those neighboring sentences before selecting.
Answering a main-idea question with a true detail from the passage rather than the overarching point, because the detail is memorable and explicitly stated.
Details are easier to verify in the text than an abstract summary, so candidates gravitate to the option they can point to directly.
What to do instead
For main-idea items, test each option by asking whether it covers the whole passage or only one paragraph. Eliminate options that are too narrow (single detail), too broad, or off-topic, then confirm the survivor against the first and last paragraphs.
Selecting an inference answer that is plausible in real life but not supported by the passage, instead of the modest conclusion the text actually licenses.
Candidates import outside knowledge and confuse 'could be true' with 'must be true given the text.'
What to do instead
For every inference option, locate the specific sentence or pair of sentences that forces the conclusion. If you cannot point to textual evidence that makes the option necessarily true, eliminate it even if it seems reasonable.
Computing an answer and then selecting the choice without re-reading what the question asked, answering for the wrong quantity (e.g., giving the discounted price when the question asks for the amount saved).
Under time pressure, candidates latch onto the first number they calculate and pattern-match it to an answer choice.
What to do instead
Underline or mentally restate the final question before computing, and after computing, write a one-line label for your result (e.g., 'this is the savings, not the price'). Check that the label matches the question before choosing.
Applying a procedure from a similar-looking problem without checking the conditions, such as cross-multiplying in an inequality or distributing a negative sign incorrectly across parentheses.
Recognizing a familiar problem type triggers automatic recall of a procedure, and the candidate skips the step of verifying that the procedure's preconditions hold.
What to do instead
Before executing a remembered method, state its precondition in one sentence (e.g., 'cross-multiplication requires a positive denominator'). If the condition fails, switch methods. For sign-sensitive work, substitute one test value to verify the result.
Reading a data table or graph by its axis labels alone and reporting a value from the wrong series, unit, or scale interval.
Charts compress a lot of information, and candidates scan for the nearest number matching their expectation rather than tracing the correct series and unit.
What to do instead
Before answering, explicitly name the series, unit, and axis you need. Trace the value with a finger or cursor from the correct axis, and sanity-check the magnitude against the axis range.
Mixing up similar science terms that sound alike but mean different things, such as mass versus weight, or conduction versus convection, and choosing the familiar-sounding term.
Everyday usage blurs these distinctions, so the colloquial meaning overrides the precise scientific definition under time pressure.
What to do instead
Maintain a short personal list of confusable term pairs with a one-line definition and a concrete example for each. Before answering, state the defining criterion (e.g., 'weight depends on gravity; mass does not') and test the scenario against it.
Ignoring the setup conditions in a science scenario (temperature, state of matter, whether a system is open or closed) and choosing the answer that is true in general but false for the described case.
Candidates focus on the phenomenon being described and skip the qualifiers that determine which principle applies.
What to do instead
Circle or note every condition stated in the prompt (temperature, phase, container, time frame). Evaluate each option against those conditions specifically, and reject any option that requires a condition the prompt does not grant.
Rushing the final questions or leaving blanks when time runs short, even though there is no penalty for guessing and easy items may remain later in the section.
Candidates assume difficulty increases steadily and spend too long on one hard item early, then run out of time before reaching easier items.
What to do instead
Set a per-question time budget, mark and skip any item exceeding it, and return later. In the last minute, fill every remaining blank with a reasoned elimination guess rather than leaving it empty.