Practice writing clear help centre articles, FAQs, and user-facing documentation for technical products.
0 / 8 completed
1 / 8
What is the most important quality of a help centre article?
Help centre articles succeed when they deflect support tickets by answering the user's actual question. The best articles are written with a specific user question in mind and optimized to answer that question efficiently.
2 / 8
Which sentence is the better opening for a help centre article about password reset?
Help articles should open by addressing the user's situation directly ('if you have forgotten your password') and stating the outcome ('regain access'). Technical or passive openings increase cognitive load before the user even starts.
3 / 8
What does 'task-based writing' mean in documentation?
Task-based writing matches how users think: they have a goal, not an interest in features. 'Configure email notifications' is task-based. 'Notification settings' is feature-based. Task-based docs are found more easily and followed more successfully.
4 / 8
What is the 'inverted pyramid' structure in help content writing?
Inverted pyramid: answer first, details second. Users scanning a help article want the answer immediately. If they need more context, it is available below. This reduces frustration for users who just need the quick answer.
5 / 8
What is a 'scannability' technique in help centre writing?
Most users scan, not read. Headers let them jump to relevant sections; numbered steps make procedures followable; bold terms highlight key concepts. A wall of text in a help article means most users will not find their answer.
6 / 8
How should you document a known limitation in a help centre article?
Documenting limitations proactively builds trust and prevents frustrated users from creating support tickets. Including a workaround or roadmap acknowledgement turns a limitation note into a helpful resource.
7 / 8
Which is an example of good FAQ question phrasing?
FAQ questions should mirror the exact language users use when they have a problem. 'Why was I charged twice this month?' is specific, searchable, and matches real user intent. Vague headings like 'Billing' or 'Payment issues' do not answer anything.
8 / 8
What is 'progressive disclosure' in help documentation?
Progressive disclosure matches user expertise: beginners see the simple version first; advanced users can expand sections or click to deeper guides. This prevents overwhelming new users while serving expert users' need for detail.
This exercise, "Help Centre and Documentation Writing (English)", tests your understanding of technical support vocabulary and phrasing through 8 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 8 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Support exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical support topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Support exercises?
Browse the full Technical Support exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.