Prepositions After Common Technical Verbs

By the end of this lesson, you will be able to...

• Choose a common verb-plus-preposition pattern from the relation you mean.

• Describe dependencies, responses, waiting, recovery, and outcomes in short technical sentences.

• Keep a request trace readable without translating each preposition word by word.

Idea in one sentence: After a technical verb, the preposition acts like a small interface: it tells the reader what the action is connected to, waiting for, recovering from, or producing.

Core Insight

Technical English uses many verb-plus-preposition pairings as stable units. The verb gives the action; the preposition identifies the other side of the relation:

The client connects to the edge.
The API depends on the identity service.
The worker responds to the queue event.
The worker waits for a lease.
The service recovers from a timeout.
The retry results in a duplicate request.

These are not six interchangeable ways to say “the system does something.” Each sentence answers a different operational question. Where does the client connect? What must the API have? What stimulus does the worker handle? What event is it waiting for? What failure does the service leave? What consequence follows the retry?

In Spanish, a single preposition may feel like a reasonable translation for several of these relations. In English, the pairing is part of the technical meaning. Learn the relation first, then choose the pairing that names it.

The Small Situation: One Request, Several Relations

A team is tracing a request that enters through an edge proxy, reaches an API, waits for a database connection, and may be retried after a timeout. The first trace note is too vague:

The client connects in the edge.
The API depends of the identity service.
The worker waits of a lease.
The service recovers of the timeout.

The nouns are correct, but the prepositions hide the system relations. Repair the note by asking a question at each step:

Now the trace can be read as a sequence of relations rather than a pile of translated words.

The Naive Idea: Translate the Preposition Separately

A literal translation starts with the Spanish word and searches for an English equivalent. That works for a few simple location phrases, but it breaks when the verb has a conventional partner:

depender de -> depend of       # literal, but wrong
esperar por -> wait by         # literal, but wrong
responder a -> respond at      # literal, but wrong
recuperarse de -> recover of    # literal, but wrong

The better workflow is to identify the relation and retrieve the whole English chunk:

dependency -> depend on
expected event -> wait for
stimulus or request -> respond to
previous failure or state -> recover from

This is not blind memorization. The relation gives the pairing a useful shape, and repeated system traces make the shape easier to recall.

Six High-Value Pairings

1. connect to: identify an endpoint

Use connect to when a client, socket, service, or device establishes a link with an endpoint:

The browser connects to the edge proxy.
The worker connects to the message broker.
The agent connects to the control plane.

The object after to is the destination or endpoint. Do not use connect in for this relation:

The browser connects to the API.       # endpoint
The browser runs in the container.     # location

Connect with can appear when the focus is interaction or agreement between parties, but for a network endpoint, connect to is the dependable default.

2. depend on: name a required dependency

Use depend on when one component needs another component, condition, or resource:

The API depends on the identity service.
The batch job depends on a valid checkpoint.
The deployment depends on a successful migration.

The object after on is a prerequisite. This differs from location:

The API runs in the cluster.             # location
The API depends on the identity service. # prerequisite

The pairing is also useful in incident analysis. The report depends on fresh telemetry identifies a missing input; it does not say where the report runs.

3. respond to: name a request or stimulus

Use respond to when a service, handler, or person produces an action after receiving a request, event, alert, or signal:

The API responds to the client's request.
The controller responds to a failed health check.
The consumer responds to the rebalance event.

The object after to is the stimulus. Keep it visible when the response matters:

The service responded quickly.          # response, but no stimulus
The service responded to the timeout.   # stimulus is explicit

4. wait for: name an expected event or resource

Use wait for when a process pauses until an event, lock, reply, token, or resource becomes available:

The worker waits for a lease.
The client waits for the server's response.
The migration waits for the lock to be released.

The object after for is what the process expects. Do not use wait on merely because the process is “on” a server. Wait on can occur in specialized contexts, but wait for is the clear pattern for an expected event or object in a trace.

5. recover from: name the previous failure or state

Use recover from when a service, process, or team returns from an error, outage, degraded state, or interruption:

The worker recovers from a broker disconnect.
The database recovers from a failed replica.
The team recovered from the incident without data loss.

The object after from is the state left behind. Compare it with movement:

The message came from the broker.       # source of movement
The worker recovered from the broker error. # previous failure

Both sentences use from, but the verb determines whether the phrase describes movement or a return from failure.

6. result in: name a consequence

Use result in when one action, condition, or decision produces an outcome:

The retry resulted in a duplicate charge.
The missing index results in a table scan.
The timeout resulted in a 504 response.

The object after in is the consequence. It is different from result from, which names the cause:

The duplicate charge resulted from an unsafe retry. # cause
The unsafe retry resulted in a duplicate charge.   # consequence

This pair is valuable in postmortems because it lets you state direction explicitly: cause results in effect, while effect results from cause.

Build a Trace One Relation at a Time

Use the six pairings to expand a tiny request trace. Start with the actors:

browser -> edge -> API -> worker -> database

Now add one relation to each arrow or waiting point:

The browser connects to the edge proxy.
The edge forwards the request to the API.
The API depends on the identity service.
The worker waits for a database connection.
The service responds to the request.

Add the failure path:

The service recovers from a database timeout.
The retry results in a second request.

The prepositions make the trace directional. To points at an endpoint, on names a prerequisite, for identifies what is expected, from marks a previous state, and in introduces a consequence. The same system nouns become much easier to follow because every relation has a visible partner.

A Retrieval Routine for Writing

When a sentence feels uncertain, use this four-step routine:

1. Name the verb. Is the component connecting, depending, responding, waiting, recovering, or producing a result?
2. Ask the relation question. Endpoint, prerequisite, stimulus, expected object, previous failure, or consequence?
3. Retrieve the chunk. connect to, depend on, respond to, wait for, recover from, or result in.
4. Test the direction. Read the sentence and point from the verb toward the following noun. If the direction is unclear, add the missing technical object.

For example, “The deployment ___ a migration” is ambiguous until you decide whether the migration is required or caused by the deployment. The intended sentence may be:

The deployment depends on a successful migration. # prerequisite
The deployment resulted in a schema migration.     # consequence

The grammar choice exposes the operational meaning.

When the Same Noun Appears in Several Relations

One technical noun can appear after different pairings, and the pairing changes the question. Consider a database connection:

The worker connects to the database.       # endpoint
The worker depends on the database.        # prerequisite
The worker waits for a database connection. # expected resource
The worker recovers from a database timeout. # previous failure

The noun database did not tell us which preposition to choose. The verb and the intended relation did. This is useful when an incident note contains several sentences about the same component. Repeating the noun is often better than replacing it with an unclear pronoun, because each sentence can expose a different operational fact.

The same test works with an event:

The consumer responds to the rebalance event. # stimulus
The consumer waits for the rebalance event.    # expected event
The rebalance event results in a new assignment. # consequence

Do not decide from the noun alone. Decide whether the event has already arrived, is still expected, or produces a later state. Then retrieve the pairing that carries that time and direction.

This also helps when the subject changes. A team can respond to an alert, a service can recover from the outage, and a change can result in a new alert. The preposition is stable because the relation is stable, even though the subject is a person, a process, or an event.

A Compact Trace Review

Before you publish a request trace, scan each verb phrase with three questions:

1. Is the object an endpoint, prerequisite, stimulus, expected resource, previous failure, or consequence?
2. Does the preposition point toward that relation, or did a literal translation choose it?
3. Would a reader know what happened first and what happened next?

If a sentence fails the third question, add a temporal or operational boundary rather than adding decorative detail. The worker waited for the lease before retrying is useful because it orders two actions. The worker waited for the important lease in the normal system environment adds words without clarifying the trace.

This review is small enough to use in a pull request or incident channel. It also prepares the next lesson, where you will combine these pairings with from, through, across, and to to describe a complete request path.

Trade-offs and Limits

The trade-off is speed versus flexibility. Stable pairings make technical writing faster and less ambiguous, but they impose a cost: the writer must remember the conventional chunk instead of freely substituting a preposition. A short phrase such as depend on is efficient once learned; a literal translation can be slower to correct and may reverse the relation in an incident note. Accept that small memory cost because the reader gains a clear dependency, direction, or consequence.

The pairings do not replace system detail. The worker waits for the queue does not tell us how long it waits, whether the queue is healthy, or whether a timeout is safe. The service responds to the alert does not tell us whether the response fixed the cause. Add a noun, condition, or boundary when the decision depends on it:

The worker waits for a lease for 30 seconds before failing.
The service responds to the alert by disabling the new route.

Precision improves, but sentences become longer. Buy that extra length only when the omitted relation would change an operational decision.

Active Check: Choose the Relation

Check: A browser establishes a network link with an API. Complete the sentence:

The browser connects ___ the API.

Think first, then reveal.

Answer: to. Connect to identifies the endpoint.

Check: A worker pauses until a lease arrives. Which sentence is natural?

A. The worker waits on a lease.

B. The worker waits for a lease.

C. The worker waits from a lease.

Think first, then reveal.

Answer: B. Wait for names the expected object.

Check: A retry creates a duplicate request. Which direction is correct?

The retry resulted ___ a duplicate request.

Answer: in. Result in introduces the consequence; result from would introduce the cause.

Common Confusions

depend on versus run in

The API runs in the cluster.             # location
The API depends on the identity service. # prerequisite

respond to versus connect to

The client connects to the endpoint.     # establishes a link
The endpoint responds to the request.    # handles a stimulus

wait for versus recover from

The worker waits for a retry token.      # expected object
The worker recovers from a timeout.      # previous failure

result in versus result from

The timeout resulted in a 504.           # consequence
The 504 resulted from the timeout.       # cause

Pairing versus movement

The request moves from the edge to the API. # path
The API depends on the identity service.    # prerequisite

Movement prepositions describe a path. Verb pairings describe the relation selected by the verb.

Transfer Challenge: Repair an Incident Note

An incident note says:

The client connects in the edge.
The worker waits of a lease.
The retry resulted from a duplicate request.
The service recovered of the timeout.

Rewrite it so each sentence points to the intended endpoint, expected object, consequence, and previous failure. Add one boundary that would help the next engineer investigate.

Model answer:

The client connects to the edge proxy.
The worker waits for a lease.
The retry resulted in a duplicate request.
The service recovered from the timeout after 30 seconds.

The boundary (after 30 seconds) makes the recovery claim inspectable. Your nouns may differ, but the verb-plus-preposition relation must stay visible.

Daily Practice Lines

Repeat these lines during the day:

The client connects to the edge proxy.
The API depends on the identity service.
The worker waits for a lease.

For spaced review, add the failure and consequence pair:

The service recovers from a timeout, but the retry results in a duplicate request.

Resources

• [ARTICLE] Cambridge Dictionary Grammar - Reference for verb-preposition patterns and complement forms.
• [ARTICLE] MDN HTTP Overview - Technical context for clients, servers, requests, and responses.
• [ARTICLE] Microsoft Writing Style Guide - Guidance for direct, inspectable technical sentences.

Key Takeaways

• Use the relation to retrieve the whole pairing: connect to, depend on, respond to, wait for, recover from, and result in.
• Let the following noun identify the endpoint, dependency, stimulus, expected object, previous failure, or consequence.
• Do not translate each preposition separately when the verb has a stable technical partner.
• Add a time limit, workload, or other boundary when the relation affects an operational decision.