Real-world sentences rewritten in Simplified Technical English. Each pair shows the original text, the STE version and a short note on what changed.
How to use these examples
The best way to understand ASD-STE100 is to see it at work. Rules can seem abstract when you read them in a list. When you compare a normal sentence with its STE version, the purpose of each rule becomes clear: the reader finds the action faster, the meaning is fixed, and there is less to translate.
The examples on this page are our own. They are written for learning, and they follow the general principles of the standard. They are not taken from the specification, and they are not official model answers. Some wording in the STE versions may use technical names or technical verbs that your company defines. Always confirm the exact words with the dictionary in the official ASD STE 100 PDF.
Try this method. First, read the "Before" sentence and find the problems yourself. Is it passive? Is it too long? Does it use a word with many meanings? Then read the STE version and the note. After a few examples, you will start to see the same patterns in your own writing. To practise further, paste your own text into the STE checker, or follow the exercises on the ASD STE 100 skill page.
The examples are grouped by text type: procedures, descriptions, warnings and cautions, and software documentation. The rules are similar in each group, but the focus is different. Procedures need clear commands. Descriptions need clear structure. Warnings need clear risk and a clear action. Software text needs consistent names for the things on the screen.
Procedures
Procedures tell the reader what to do. In STE, each step is a command, with the verb first, and each sentence has a maximum of 20 words. One step contains one instruction, or two instructions only when the reader must do them at the same time.
Before
The four retaining screws should be removed and the access panel should then be carefully lifted away from the housing.
STE version
Remove the four screws.
Carefully lift the access panel from the housing.
Two commands replace two passive clauses. The vague word "retaining" is not necessary, because the reader can see the screws.
Before
Prior to commencing installation, ensure that all mating surfaces have been thoroughly cleaned.
STE version
Before you start the installation, clean all the contact surfaces.
"Prior to", "commence" and "ensure" are replaced with simple words. The real action, "clean", is now the main verb.
Before
Torque the bolts to 25 Nm, making sure to follow the sequence shown in Figure 3.
STE version
Tighten the bolts to 25 Nm in the sequence that Figure 3 shows.
The -ing clause is removed. The step now has one clear instruction.
Before
If the indicator fails to illuminate, the bulb may need replacing.
STE version
If the indicator does not come on, replace the bulb.
"Fails to illuminate" becomes plain words, and the uncertain "may need replacing" becomes a direct command.
Before
Following the completion of the leak test, the system can be repressurized.
STE version
After the leak test, pressurize the system again.
A long noun phrase and a passive verb become a short time clause and a command.
Descriptions
Descriptive text explains how something is built or how it works. STE allows up to 25 words per sentence here. Each paragraph has one topic, and the first sentence tells the reader what the topic is.
Before
The pump, which is driven by the accessory gearbox, is responsible for the provision of hydraulic pressure to the flight control actuators.
STE version
The accessory gearbox drives the pump. The pump supplies hydraulic pressure to the flight control actuators.
One long sentence with a relative clause becomes two short active sentences.
Before
Temperature monitoring is performed continuously by the controller, with alerts being generated when thresholds are exceeded.
STE version
The controller monitors the temperature continuously. When the temperature is more than the limit, the controller gives an alert.
Hidden actions ("monitoring", "being generated") become verbs with a clear subject.
Before
The unit features a modular design that facilitates rapid replacement of individual components.
STE version
The unit has modules. You can replace each module quickly.
Marketing words ("features", "facilitates") are replaced with facts that a reader can use.
Before
Located adjacent to the main battery is the external power receptacle.
STE version
The external power receptacle is adjacent to the main battery.
Normal word order puts the subject first. The reader finds the part name immediately.
Warnings and cautions
A warning tells the reader about a risk of injury or death. A caution tells the reader about a risk of damage to equipment. In STE, a warning or caution starts with a clear command and then gives the reason, in short and simple sentences.
Before
Caution should be exercised when handling the battery, as electrolyte leakage could potentially result in skin burns.
STE version
WARNING: BE CAREFUL WHEN YOU HOLD THE BATTERY. THE ELECTROLYTE CAN CAUSE BURNS TO YOUR SKIN.
A risk of injury needs a warning, not a caution. The command comes first, then the reason.
Before
Failure to depressurize the system prior to disconnection of the lines may lead to serious injury.
STE version
WARNING: RELEASE THE PRESSURE BEFORE YOU DISCONNECT THE LINES. PRESSURIZED FLUID CAN CAUSE INJURY.
The negative "failure to" structure becomes a positive command.
Before
Over-tightening of the plastic fitting is to be avoided since cracking may occur.
STE version
CAUTION: DO NOT TIGHTEN THE PLASTIC FITTING TOO MUCH. IF YOU DO, YOU CAN CAUSE A CRACK IN IT.
Damage to equipment needs a caution. The passive "is to be avoided" becomes "do not".
Software documentation
STE was made for hardware, but its ideas work well for help pages, user interface text and API guides. Short commands, one meaning per word and a consistent name for each screen element help readers around the world.
Before
In order to proceed with the configuration of your account settings, navigate to the Preferences section.
STE version
To change your account settings, go to Preferences.
Long verbs ("proceed with the configuration of") become one simple verb.
Before
Once the file has been successfully uploaded, a confirmation message will be displayed to the user.
STE version
When the upload is complete, the system shows a confirmation message.
The future passive becomes the simple present with a clear subject.
Before
Hit the button to kick off the sync process.
STE version
Click Sync to start the synchronization.
Idioms ("hit", "kick off") are hard for non-native readers. Use the exact label of the button.
Before
The API will return an error if the token is not valid or has expired, and you will need to obtain a new one.
STE version
If the token is not valid or is expired, the API returns an error. Get a new token.
One long sentence becomes a description and a separate command.
Patterns you can see in every example
Look back at the pairs above. Most of the changes come from a small number of patterns. When you learn to see these patterns, you can rewrite most technical text quickly.
Find the real action. Many sentences hide the action in a noun, such as "the completion of", "the provision of" or "the configuration of". Turn that noun back into a verb.
Say who does it. In procedures, the reader does the action, so use a command. In descriptions, name the part or system that does the action.
Replace complex words. Words such as "utilize", "commence", "facilitate" and "prior to" have simple alternatives. Simple words are faster to read and easier to translate.
Split long sentences. If a sentence contains "and then", "which" or "in order to", you can often split it into two sentences.
Remove uncertainty. Words such as "may", "potentially" and "should" make the reader ask: must I do this or not? Give a clear instruction.
Keep warnings separate. Do not hide a risk inside a step. Put it in a warning or caution before the step.
These patterns match the rule categories that we describe on the STE writing rules page. Use that page to understand why each change helps the reader, and use the official specification for the exact rules.
Common mistakes when you rewrite text in STE
New STE writers often make the text shorter but less precise. Clear text is not only short text. Keep all the technical information: values, units, tools, part names and limits. If the original says "tighten to 25 Nm", the STE version must also say 25 Nm.
Another common mistake is to change a technical name to make it "simpler". A technical name must match the label on the product or the name in the parts list. If you change it, the reader cannot find the part. STE controls general words, not the names that your product uses.
Finally, some writers remove every passive verb, even in descriptions. STE allows the passive voice in descriptive text when the agent is unknown or not important. The aim is clarity, not a mechanical rule. When you are not sure, ask: which version helps the reader more?
Next steps
Take one page of your own documentation and rewrite it with the patterns above. Then check it in the STE checker and compare it with the rules in the official ASD STE 100 PDF. If you want a structured path from beginner to reviewer, start with the ASD STE 100 skill page.