A to be verb expresses existence or a state rather than a specific action. In technical writing, highlighting these verbs can reveal unclear or bulky sentences that need revision. section 5.3.2
Use this quick revision pattern:
- Target the most important or clunkiest sentences, especially introductions and findings paragraphs. section 5.3.2
- Highlight to be verbs alongside prepositions; clusters can signal too many ideas or unnecessary dead weight. section 5.3.2
- Rewrite toward a clearer subject and action, but do not mechanically apply the process to every sentence. section 5.3.2
Turn a state-heavy sentence into an action
Before: “In the end, it was decided that the best solution was implementing it by means of a link to an existing Rust implementation.” After: “Ultimately, we implemented that encryption layer by linking to RustyEncryption.” The revision makes the actor and action easier to find. section 5.3.2
Table 5.3 Original vs. revised sentences (view table figure)
| Before |
After |
|---|---|
| An additional drawback with Zig is the young state of the ecosystem, though we hope that this is not going to continue over the long term. |
Another drawback: Zig’s young ecosystem complicates adoption. But this could change soon given the surging interest in Zig. [Star History image] |
| In the end, it was decided that the best solution was implementing it by means of a link to an existing Rust implementation. |
Ultimately, we implemented that encryption layer by linking to RustyEncryption. |
Compare original and revised technical sentences to see how reducing to be constructions can clarify responsibility and action. section 5.3.2
