5 advanced exercises — choose the right stance adverbial for incident reports, RFCs, PR reviews, and design docs. Covers hedging, emphasis, concession, and precision adverbials.
Stance adverbials by function
Hedging (signal uncertainty or debate): arguably, presumably, in principle, generally speaking, as a rule
Desirability (signal the ideal): ideally, optimally, preferably
Scope (signal breadth of claim): generally, broadly speaking, in most cases, overall
0 / 15 completed
1 / 15
An incident report reads: "The alert fired at 03:47 UTC. _____, the on-call engineer did not receive the PagerDuty notification due to a misconfigured escalation policy." Which stance adverbial best signals that the information is unexpected or counterintuitive?
Surprisingly is a style/attitude stance adverbial — it signals the writer's evaluation that the information is unexpected or contrary to what one would expect. In an incident report, it accurately frames the gap between the alert firing and the engineer not being notified as an anomaly worth highlighting. The other options don't fit the context: technically speaking and strictly speaking signal precision or qualification ("to be exact about this…") rather than unexpectedness; ideally refers to a desired outcome ("ideally, the alert would have reached the engineer") — not to what actually happened. Other attitude stance adverbials for technical writing: remarkably, notably, alarmingly, critically. Use sparingly in formal documents — one or two per section is enough.
2 / 15
A senior engineer writes in an RFC: "_____, a microservices architecture increases operational complexity significantly and requires mature DevOps tooling before the benefits outweigh the costs." Which adverbial signals a concession or counterpoint the author is acknowledging?
Admittedly is a concession stance adverbial. It signals that the writer acknowledges a point that may work against their own argument — often used when presenting a trade-off, limitation, or counter-argument before defending the main position. Typical pattern: "Admittedly, [the downside]. However, [the reason the approach is still justified]." In tech writing this is common in design decisions: "Admittedly, event sourcing adds replay complexity. However, the audit trail it provides is essential for our compliance requirements." The other options don't signal concession: notably highlights important information ("notably, the latency dropped by 60%"); crucially marks something as essential; ideally describes the preferred scenario. Concession adverbials: admittedly, granted, to be fair, it must be said that.
3 / 15
In a PR review comment, a tech lead writes: "_____, caching at the controller layer is the wrong abstraction here — the cache should sit at the service layer to remain reusable across different API endpoints." Which adverbial correctly signals a precise technical correction?
Technically speaking is a precision/qualification stance adverbial. It signals that the following claim is made from a strict technical standpoint — often used to correct a loose or informal usage, or to make a technical distinction precise. In a PR review this frames the feedback as a matter of correctness rather than personal preference. Examples: "Technically speaking, this is not a memory leak — it's unbounded cache growth." / "Technically speaking, the function is pure but the test mocks make it impure in practice." The other options change the tone: frankly = candidly, honestly (useful for direct feedback but implies personal opinion); arguably = open to debate (weakens a claim); admittedly = concession. Other precision adverbials: strictly speaking, precisely, in technical terms, by definition.
4 / 15
A design document states: "_____, the system should process all events in under 100ms end-to-end. In practice, P99 latency during peak load is currently 340ms, which suggests the queue consumer needs optimisation." Which adverbial frames the desired or best-case scenario?
Ideally is a desirability stance adverbial — it signals the writer's view of what the best or preferred outcome would be, without claiming that this outcome is currently achieved. This is a common pattern in design docs and engineering proposals: "Ideally, [the target state]. In practice/Currently, [the actual state]." More examples: "Ideally, all tests should run in under 3 minutes. However, the integration suite currently takes 18 minutes." / "Ideally, each microservice owns its own database schema." The other options shift the meaning: crucially marks something as essential ("crucially, the rate limiter must not block health checks"); arguably suggests the claim is debatable; generally speaking signals a broad generalisation with possible exceptions.
5 / 15
An engineering blog post on database indexing reads: "_____, a composite index on (user_id, created_at) will outperform two separate single-column indexes when filtering by user and sorting by date — though index maintenance cost increases with write volume." Which adverbial signals the claim is debatable but well-supported?
Arguably is a hedging stance adverbial — it signals that the claim is defensible and the writer believes it to be true, but acknowledges it is open to debate or context-dependent. This is particularly useful in technical writing when making recommendations that depend on specific conditions or where experts might disagree. Examples: "Arguably, eventual consistency is sufficient for most social media use cases." / "Arguably, the added complexity of CQRS is not justified for a team of three engineers." The sentence in the question is perfect for arguably because the claim is well-reasoned but context-dependent (depends on query patterns, write/read ratio, etc.). The "though…" clause at the end reinforces that this is not an absolute statement. Other hedging adverbials: presumably, in principle, as a rule, by and large.
6 / 15
DevOps is reporting a critical incident. 'Initially, the deployment failed due to a missing dependency,' he stated. Which stance adverbial best indicates that the initial explanation might be incomplete or require further clarification?
'Initially' suggests the starting point of an event and implies that other factors may have contributed. It subtly indicates a need for more information beyond the immediate cause. 'Consequence' or 'Subsequently' would imply a chain of events following the initial failure, while 'Furthermore' adds extra detail without questioning the core explanation. 'Primarily' suggests this was the *main* reason which is not necessarily implied by the phrasing.
7 / 15
Sarah, a junior developer, sends a Slack message to her team: 'Despite our best efforts to optimize the database queries, we're still seeing slow response times.' Which stance adverbial most accurately reflects Sarah's frustration and acknowledges potential roadblocks?
'Despite' signals a contrast between expectations (optimizing queries) and reality (slow response times). It highlights that the efforts weren't entirely successful. 'However' is the most appropriate stance adverbial in this context to express a contradiction or unexpected outcome. The other options don't convey the same level of opposition or frustration.
8 / 15
A code review comment reads: 'Given that this API endpoint handles a high volume of requests, implementing rate limiting is crucial to prevent overload.' Which stance adverbial best indicates a justification or reasoning for the proposed action?
'Given' establishes a condition or premise that supports the recommendation. It's used to explain *why* rate limiting is necessary due to the endpoint's high volume. 'Because' is too simplistic; 'Instead' suggests an alternative action, and 'While' presents a contrasting situation without justification.
9 / 15
In a PR description, you write: 'Although the new feature is fully functional, its performance during peak load requires further investigation.' Which stance adverbial best indicates a potential problem or area needing attention, even if the feature itself works correctly?
'Although' introduces a qualification – despite the functional aspect, there's an underlying concern about performance. This is a common and useful way to frame a situation where something works but isn't optimal under certain conditions. 'Thus' implies a logical consequence; 'Hence' is redundant; 'As such' doesn't provide that contrast.
10 / 15
During a standup meeting, Mark says: 'Considering the recent changes to the authentication service, user login times have increased.' Which stance adverbial best indicates that Mark is linking the increased login times to a specific factor?
'Considering' signals that the authentication changes are being presented as the cause or reason for the longer login times. 'Due to' is a more direct causal link than 'considering,' which is appropriate here. 'In spite of' suggests a contradiction and 'Regardless of' implies no connection.
11 / 15
DevOps is reporting a critical incident. 'Initially, the deployment failed due to a missing dependency,' he stated. Which stance adverbial best indicates that the initial explanation might be incomplete or require further clarification?
'Initially' suggests the starting point of an event and implies that other factors may have contributed. It subtly indicates a need for more information beyond the immediate cause. 'Consequence' or 'Subsequently' would imply a chain of events following the initial failure, while 'Furthermore' adds extra detail without questioning the core explanation. 'Primarily' suggests this was the *main* reason which is not necessarily implied by the phrasing.
12 / 15
Sarah, a junior developer, sends a Slack message to her team: 'Despite our best efforts to optimize the database queries, we're still seeing slow response times.' Which stance adverbial most accurately reflects Sarah's frustration and acknowledges potential roadblocks?
'Despite' signals a contrast between expectations (optimizing queries) and reality (slow response times). It highlights that the efforts weren't entirely successful. 'However' is the most appropriate stance adverbial in this context to express a contradiction or unexpected outcome. The other options don't convey the same level of opposition or frustration.
13 / 15
A code review comment reads: 'Given that this API endpoint handles a high volume of requests, implementing rate limiting is crucial to prevent overload.' Which stance adverbial best indicates a justification or reasoning for the proposed action?
'Given' establishes a condition or premise that supports the recommendation. It's used to explain *why* rate limiting is necessary due to the endpoint's high volume. 'Because' is too simplistic; 'Instead' suggests an alternative action, and 'While' presents a contrasting situation without justification.
14 / 15
In a PR description, you write: 'Although the new feature is fully functional, its performance during peak load requires further investigation.' Which stance adverbial best indicates a potential problem or area needing attention, even if the feature itself works correctly?
'Although' introduces a qualification – despite the functional aspect, there's an underlying concern about performance. This is a common and useful way to frame a situation where something works but isn't optimal under certain conditions. 'Thus' implies a logical consequence; 'Hence' is redundant; 'As such' doesn't provide that contrast.
15 / 15
During a standup meeting, Mark says: 'Considering the recent changes to the authentication service, user login times have increased.' Which stance adverbial best indicates that Mark is linking the increased login times to a specific factor?
'Considering' signals that the authentication changes are being presented as the cause or reason for the longer login times. 'Due to' is a more direct causal link than 'considering,' which is appropriate here. 'In spite of' suggests a contradiction and 'Regardless of' implies no connection.
What will I practise in "Stance Adverbials in Technical Writing — IT English Grammar Exercise"?
Practice stance adverbials in technical writing: surprisingly, admittedly, ideally, arguably, technically speaking, and more.
How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.