Rewrite

You are an expert technical writer rewriting text to comply with the ASD-STE100 Simplified Technical English (STE) standard.

Rewrite the ENTIRE TEXT below so it complies with every rule listed under RULES. Preserve technical meaning, safety information, and structure (numbered steps, warnings/cautions, formatting).

RULES:
### Rule 1.1 — Use approved words only (default severity: error)
Statement: Every word in the text must be either an approved word from the STE dictionary, a technical noun that fits one of the 22 approved technical-noun categories (rule 1.5), or a technical verb that fits one of the 4 approved technical-verb categories (rule 1.12).
Rewrite guidance: Replace any non-approved, non-technical word with the closest approved STE dictionary synonym, or restructure the sentence so only approved words, technical nouns, and technical verbs remain.
Rewrite constraints:
- Do not change the technical meaning of the sentence when substituting a synonym.
Example — Non-STE: "The technician is utilizing a new tool to examine the engine." -> STE: "The technician uses a new tool to examine the engine."

### Rule 1.2 — Use approved words as the specified part of speech (default severity: error)
Statement: Use an approved dictionary word only as the part of speech (noun, verb, adjective, etc.) that the dictionary specifies for it; do not convert it to a different part of speech.
Rewrite guidance: Reconstruct the sentence so the word is used only in its approved part of speech — often this means turning a verb usage into a noun phrase ('do the leak test of the system' instead of 'test the system') or finding an approved verb with the same meaning ('make sure the valve can operate' instead of 'make sure the valve is operable').
Rewrite constraints:
- Preserve the original instruction's meaning exactly.
- If the straightforward replacement changes meaning, use a different word or sentence construction instead.
Example — Non-STE: "Test the system for leaks." -> STE: "Do the leak test of the system."

### Rule 1.3 — Use approved words with their approved meanings only (default severity: error)
Statement: Use each approved dictionary word only with the approved meaning or meanings the STE dictionary assigns it, even where standard English allows broader or different meanings. Some approved words have more than one approved meaning; use any of those, but never a standard-English sense the dictionary does not list.
Rewrite guidance: Replace the misused word with the STE word whose approved meaning actually matches the intended sense (e.g. 'obey' for compliance with instructions, keeping 'follow' only for physical or sequential succession).
Rewrite constraints:
- Do not introduce a replacement word whose own approved meaning also fails to match the intended sense.
Example — Non-STE: "Follow the safety instructions." -> STE: "Obey the safety instructions."

### Rule 1.4 — Use only the approved forms of verbs and adjectives (default severity: warning)
Statement: Use each approved verb only in the specific forms the dictionary lists for it (typically infinitive/imperative, simple present, simple past, and past participle — e.g. REMOVE, REMOVES, REMOVED, REMOVED) and each approved adjective only in its dictionary-given base, comparative, and superlative forms (e.g. SLOW, SLOWER, SLOWEST). Adjectives that regularly form comparatives/superlatives with 'more'/'most' are not given separate dictionary forms, since 'more' and 'most' are themselves approved words — except where a more specific rule (e.g. rule 1.5, category 17 colors) bans comparison for that word outright.
Rewrite guidance: Replace the non-dictionary form with the correct dictionary-listed form for that verb, or use the correct base/comparative/superlative adjective form (including a regular 'more'/'most' construction where applicable, subject to category-specific bans such as rule 1.5's colors).
Rewrite constraints:
- Keep the sentence's tense and meaning intact.
- Do not use this rule to police passive voice or participle-as-adjective clarity (see rules 3.3/3.4) or color comparatives (see rule 1.5) — those are governed elsewhere.
Example — Non-STE: "The technician removeed the panel." -> STE: "The technician removed the panel."

### Rule 1.5 — You can use technical nouns from approved categories (default severity: info)
Statement: A word not in the STE dictionary may be used as a technical noun only if it fits one of the 22 approved technical-noun categories listed in technicalNounCategories (each with its official definition, examples, and source page). Category membership does not by itself override the requirement to use the approved company/industry/subject-field term when one exists (rule 1.8). For category 17 (colors): colors are technical nouns even though they behave grammatically as adjectives, and comparative or superlative color forms (e.g. 'blacker', 'the reddest') are never permitted in STE — there is no compliant 'more'/'most' workaround for a color comparison.
Rewrite guidance: If the word does not fit a technical-noun category, replace it with an approved dictionary word or the approved company/industry/subject-field technical term. If it does fit a category and no more specific approved term exists, leave it unchanged. For a color comparison, restructure the sentence to avoid a comparative/superlative color form entirely — do not propose a 'more'/'most' color construction.
Rewrite constraints:
- Do not substitute a differently-specific technical noun (e.g. a more generic or more specific term) purely for brevity or familiarity when the original term is itself valid and used elsewhere in the text (see rule 1.11).
Example — Non-STE: "Retract the main landing gear." -> STE: "Retract the main landing gear."

### Rule 1.6 — Use non-approved words only as technical nouns (default severity: error)
Statement: A word may be used as a technical noun (or as part of one) — never with its ordinary, non-technical meaning — in two cases: (a) the dictionary explicitly marks it not approved, or (b) the word is absent from the dictionary entirely. Both cases require a genuine, valid technical-noun use under rule 1.5.
Rewrite guidance: Replace the disapproved word with the specific alternative the STE dictionary entry gives for it (e.g. 'base' -> 'bottom', 'main' -> 'primary' are illustrative, not a fixed universal pairing — verify against the dictionary entry for the word in context), or the approved domain term when the word is part of a technical noun; leave it unchanged when it is genuinely part of an established technical noun.
Rewrite constraints:
- Never replace a disapproved word inside an established technical noun (e.g. do not turn 'main landing gear' into 'primary landing gear').
Example — Non-STE: "Make sure that the two spigots at the base of the unit engage." -> STE: "Make sure that the two spigots at the bottom of the unit engage."

### Rule 1.7 — Do not use technical nouns as verbs (default severity: error)
Statement: Use a technical noun only as a noun (or as an adjective inside a different technical noun) — never convert it into a verb.
Rewrite guidance: Restructure the sentence so the technical noun is used only as a noun, typically with an approved verb such as 'apply', 'use', or 'put' (e.g. 'oil the surfaces' -> 'apply oil to the surfaces').
Rewrite constraints:
- Keep the instruction's meaning and required action identical.
Example — Non-STE: "Oil the steel surfaces." -> STE: "Apply oil to the steel surfaces."

### Rule 1.8 — Use only approved technical nouns (default severity: warning)
Statement: When your company, industry, or subject field has an approved technical noun for something, use that exact term rather than an invented, generic, or overly obscure alternative.
Rewrite guidance: Replace the non-standard term with the specific, approved technical noun used in the relevant company/industry/subject field.
Rewrite constraints:
- Keep the level of specificity the passage requires — do not over-generalize into a vaguer term.
- Do not substitute a term without verifying it against the applicable glossary/terminology database; if no verification is possible, flag for manual review instead of asserting a specific replacement.
Example — Non-STE: "The front panel of the phone has a touch-sensitive display and a home key." -> STE: "The front panel of the phone has a touchscreen and a home button."

### Rule 1.9 — Use short and easy to understand technical nouns (default severity: info)
Statement: When no technical noun is approved in your company, industry, or subject field, select one that is short (not more than three words) and easy to understand, relying on illustrations or index numbers for extra specificity rather than a long descriptive noun phrase.
Rewrite guidance: Shorten the noun phrase to its essential term (2-3 words), removing descriptive material that duplicates what an accompanying index number or illustration already provides.
Rewrite constraints:
- Do not remove index/reference numbers or the parts they identify.
- Only shorten if the essential identifying information is preserved.
Example — Non-STE: "Disconnect the braided stainless steel flexible hydraulic supply hose (30) from the anodized aluminium manifold body (35)." -> STE: "Disconnect the hydraulic supply hose (30) from the manifold (35)."

### Rule 1.10 — Do not use regional, slang, or jargon words as technical nouns (default severity: warning)
Statement: Do not use technical nouns that are only understood by people in a specific region, or that are slang or narrow jargon understood by only a small group — always use well-known, widely understood terms.
Rewrite guidance: Replace the regional/slang/jargon term with the equivalent widely-understood technical noun or a plain-language description of the same thing.
Rewrite constraints:
- Preserve the precise technical meaning of the original term.
Example — Non-STE: "During logging operations, attach a choker to the heavy machinery to hold the logs in their position." -> STE: "During logging operations, attach a cable to the heavy machinery to hold the logs in their position."

### Rule 1.11 — Use the same technical noun for the same item throughout (default severity: error)
Statement: Once you select the approved technical noun for an item, use that exact same term every time you refer to that item in the text — never switch to a synonym or a different technical noun for it.
Rewrite guidance: Pick the single approved technical noun for the item (usually its first or most standard mention) and replace every other reference to that same item with that exact term.
Rewrite constraints:
- Do not merge references to genuinely different items into one term.
Example — Non-STE: "Make sure that the servo control unit is in the open position. Do the operational test of the actuator. Disconnect the control unit from the test rig." -> STE: "Make sure that the actuator is in the open position. Do the operational test of the actuator. Disconnect the actuator from the test rig."

### Rule 1.12 — You can use technical verbs from approved categories (default severity: warning)
Statement: A word not in the STE dictionary may be used as a technical verb only if it fits one of the 4 approved technical-verb categories listed in technicalVerbCategories (each with its official definition, subcategories, examples, and source page) — and only when no approved dictionary verb already expresses the same instruction clearly.
Rewrite guidance: If an approved dictionary verb expresses the same instruction, use it instead of the technical verb. If a technical verb is genuinely needed, use the specific correct one for the process, not a vague substitute.
Rewrite constraints:
- Do not lose precision about which physical process is being instructed.
Example — Non-STE: "If you detect broken wires, repair them." -> STE: "If you find broken wires, repair them."

### Rule 1.13 — Do not use technical verbs as nouns (default severity: error)
Statement: Use a technical verb only as a verb — never convert it into a noun. Its past-participle form may still be used as an adjective.
Rewrite guidance: Rewrite the sentence so the technical verb is used as a verb in an imperative or active-voice instruction, instead of as a noun.
Rewrite constraints:
- Keep the instruction's meaning identical.
- Do not invent an unstated object or agent when rewriting (e.g. do not add 'the system' if the source text does not name it).
Example — Non-STE: "Do the reaming of the hole." -> STE: "Ream the hole."

### Rule 1.14 — Use American English spelling (default severity: error)
Statement: Use American English spelling as given in the STE dictionary, unless an applicable official directive specifically requires a different spelling; leave quoted text (e.g. text shown on a screen or label) unchanged even if it uses non-American spelling.
Rewrite guidance: Replace the British/Commonwealth spelling with its American English equivalent, leaving any quoted/reproduced text exactly as-is.
Rewrite constraints:
- Never alter the spelling inside directly quoted text (screen text, labels, placards).
Example — Non-STE: "The door is made of carbon fibre reinforced plastic." -> STE: "The door is made of carbon-fiber-reinforced plastic."

### Rule 2.1 — Write multi-word nouns of no more than three words (default severity: warning)
Statement: A multi-word noun is a string of nouns and/or adjectives (with no article or preposition breaking it up) that together modify a head noun and function as one part of speech. Keep every multi-word noun to a maximum of three words; if a concept needs more, restructure the phrase (for example with prepositions such as 'of,' 'on,' 'in,' or 'for') instead of stacking more than three words together.
Rewrite guidance: Break the long noun string apart using prepositions (of, on, in, for) or a relative clause so that no single unbroken noun string exceeds three words; do not simply delete words or technical content to shorten it.
Rewrite constraints:
- Preserve all technical information from the original phrase — restructure the wording, don't remove meaning.
- If the long string is itself an approved technical noun from official documentation that cannot be restructured, apply rule 2.2 instead of forcing a rewrite here.
Example — Non-STE: "Runway light connection resistance calibration." -> STE: "Calibration of the resistance of the runway light connection."

### Rule 2.2 — Write long technical nouns in full, then shorten or hyphenate them (default severity: warning)
Statement: When an approved technical noun (from official company, engineering, or parts-catalog documentation) itself has more than three words and cannot be shortened in meaning, write it out in full the first time it occurs in the text. After that first occurrence, if possible, you can either (a) switch to a shorter form or an approved abbreviation for the rest of the document, or (b) use hyphens between words that function together as one unit so the phrase reads as three words or fewer. Abbreviating or hyphenating is not necessary for an approved technical noun that already has three words or fewer, and you must never alter hyphens or abbreviations that are already fixed parts of an official approved technical noun.
Rewrite guidance: On first occurrence, spell out the long technical noun in full (with a brief parenthetical explanation if helpful), then use an approved abbreviation or a shorter form for later occurrences. Alternatively, hyphenate only the words that truly function as one unit so the phrase reads as three words or fewer. Remove any hyphenation or abbreviation applied to technical nouns that are already three words or fewer.
Rewrite constraints:
- Never change hyphens or word forms that are already part of an official/approved technical noun.
- Do not string hyphens across more than three word-units just to disguise the word count.
Example — Non-STE: "The primary parts of the valve are: - The DA (8) - The PVA (15) - The BA (17) - The VB (20)." -> STE: "The primary parts of the valve are: - The diaphragm assembly (8) - The poppet valve assembly (15) - The bush assembly (17) - The valve body (20)."

### Rule 3.1 — Use only the verb forms that are given in the dictionary (default severity: error)
Statement: For each approved verb, use only the specific inflected forms listed for it in the STE dictionary (typically the base/infinitive, the simple present, the simple past, and the past participle). Do not use, invent, or regularize any form of an approved verb that is not one of the forms the dictionary gives for it, even if that form would be grammatically valid in general English.
Rewrite guidance: Replace the non-dictionary verb form with the closest dictionary-listed form for that verb (base, present, past, or past participle) that fits the intended meaning, restructuring the sentence if needed.
Rewrite constraints:
- Do not substitute a different verb altogether if the intended verb is approved — only correct the form.
Example — Non-STE: "The technician gived the tool to the mechanic." -> STE: "The technician gave the tool to the mechanic."

### Rule 3.2 — Use only approved verb forms and tenses (default severity: error)
Statement: Use verbs only in one of these forms or tenses: the infinitive form, the imperative (command) form, the simple present tense, the simple past tense, the simple future tense, or the past participle used as an adjective. Do not use other tenses or constructions such as the present/past perfect, the present/past progressive, or any other complex (multi-auxiliary) verb construction.
Rewrite guidance: Rewrite using one of the six approved forms — most often by converting a perfect or progressive construction to the simple past or simple present tense, or to the imperative for procedural instructions. If a mechanical tense substitution would change the intended time relationship (e.g. an action that is genuinely ongoing, future, or still relevant now), restructure the sentence instead — for example by splitting it into two sentences or adding a time reference — rather than forcing it into simple past. Caution: a sentence originally in the past/present progressive or perfect can carry an overlap, ongoing, or still-relevant-now meaning that a mechanical switch to simple past/present can silently drop (e.g. 'was checking ... when the alarm activated' describes an action in progress when a second event interrupted it, which 'checked ... when the alarm activated' does not preserve) — for those cases, restructure the sentence (e.g. split into two sentences, or add an explicit time reference) instead of substituting the tense.
Rewrite constraints:
- Preserve the intended time relationship of the original sentence (do not turn future or ongoing information into simple past unless that changes no meaning).
- Verify the rewritten sentence still expresses the same aspect/time meaning as the original before accepting it; do not perform a blind tense substitution.
Example — Non-STE: "The system has failed twice this month." -> STE: "The system failed twice this month."

### Rule 3.3 — Use the past participle form as an adjective (default severity: warning)
Statement: A verb's past participle form may be used as an adjective — either directly before the noun it modifies, or after a form of 'to be,' 'to become,' or 'to stay' — to show the condition of something; this is not passive voice. Only use a past participle as an adjective if it (or its adjective sense) is listed in the dictionary, including approved adjectives such as 'permitted' or 'damaged' whose underlying verb is not itself approved.
Rewrite guidance: If a past participle correctly shows condition (before a noun, or after to be/become/stay) but is not an approved adjective, replace it with an approved adjective or restructure the description. If it is instead part of a disallowed perfect or passive verb construction, fix it per rule 3.2, 3.4, or 3.6 instead.
Example — Non-STE: "Do not put more than the weight that is permitted on the trolley." -> STE: "Do not put more than the permitted weight on the trolley."

### Rule 3.4 — Do not use auxiliary verbs to make complex verb constructions (default severity: error)
Statement: Do not build complex verb constructions with auxiliary verbs used as the main verb of a perfect tense or a passive/modal construction — for example 'have/has' plus a past participle to form a perfect tense, or 'is/are/can/must/will' plus a past participle to form a modal or passive construction where the participle functions as the action verb, not as an adjective. This does not cover a past participle used purely as an adjective (rule 3.3) or the narrow permitted descriptive passive with a genuinely unknown agent (rule 3.6) — those are separate, permitted constructions that happen to share the same surface 'be + past participle' form. These disallowed constructions produce non-approved tenses and passive-voice sentences. Instead, identify the true agent of the action and use it as the subject of an approved simple tense (see rule 3.2), or use the imperative for procedural instructions.
Rewrite guidance: First identify whether the actual agent is stated or clearly implied by context (e.g. an operator, a robot, a named system) and, if so, make that agent the grammatical subject in a simple approved tense. Use 'you' only when the reader is genuinely the agent, and 'we' only when the writer's organization genuinely is. If no agent is supported by the context, do not fabricate one — convert to the imperative for procedural instructions, or, for descriptive text with a truly unknown agent, use an allowed descriptive passive (rule 3.6) instead of inventing 'you'/'we'.
Rewrite constraints:
- Do not invent an agent that is not supported by the context.
- Never default to 'you'/'we' as a fallback when the agent is unknown — prefer an allowed descriptive passive in that case.
Example — Non-STE: "The operator has adjusted the linkage." -> STE: "The operator adjusted the linkage."

### Rule 3.5 — Use the "-ing" form of a verb only as a technical noun or noun modifier (default severity: error)
Statement: Do not use a word with an '-ing' form as part of a verb phrase (a progressive tense) or to build long modifying clauses attached to a noun. The '-ing' form may be used in two separate, independent ways: (1) as a valid technical noun (for example in a procedure title or heading) or as a functional modifier within a technical noun describing the function of a system, component, part, tool, or material — this path does not require the specific '-ing' word to also appear in the small dictionary-approved general list; or (2) as one of the small number of dictionary-approved general '-ing' words. A word only needs to satisfy one of these two paths, not both.
Rewrite guidance: Rewrite the sentence so the action is expressed with a finite verb in an approved tense (rule 3.2) — typically converting 'while X is -ing' to 'while X verb-s,' and breaking long '-ing'-headed modifier clauses into separate short sentences or a numbered list.
Rewrite constraints:
- Keep '-ing' words that are approved technical nouns or noun-modifiers (headings, component names) unchanged.
Example — Non-STE: "When you are doing this procedure, obey all the safety precautions." -> STE: "When you do this procedure, obey all the safety precautions."

### Rule 3.6 — Use the active voice (default severity: error)
Statement: Always write in the active voice, where the grammatical subject performs the action of the sentence. In descriptive writing only, the passive voice is permitted when the agent (the person or thing that does the action) is genuinely unknown; procedural (instructional) writing must always use the active voice.
Rewrite guidance: Convert to active voice using one of: (1) move the named agent (often in a 'by' phrase) to the subject position, (2) replace a passive infinitive construction with a direct active verb, (3) use the imperative for procedural instructions, or (4) use 'you' only with positive evidence the reader is the agent, or 'we' only with positive evidence the writer's organization is the agent — never as a default for an unstated agent.
Rewrite constraints:
- For descriptive sentences with a genuinely unknown agent, keep the passive voice (or use 'something' as agent) rather than fabricating a false agent.
- Do not select 'you' or 'we' merely because the sentence does not name an agent — confirm the reader or the writer's organization is actually the one performing the action first.
Example — Non-STE: "The circuits are connected by a switching relay." -> STE: "A switching relay connects the circuits."

### Rule 3.7 — Use an approved verb to describe an action, not a noun or other part of speech (default severity: warning)
Statement: When an approved verb exists that describes the action you mean, use that verb directly rather than a nominalized construction (e.g. 'give an indication of,' 'before the removal of') or another part of speech. If a word is not approved as a verb in the dictionary, do not use it as a verb — restructure the sentence instead, for example with a 'do a/an <noun> of' construction.
Rewrite guidance: If an approved verb exists for the action, replace the nominalized or indirect phrase with that verb directly. If the word is not approved as a verb, keep or convert to a 'do a/an <noun> of' construction instead of using the word as a verb.
Example — Non-STE: "The ohmmeter gives an indication of 450 ohms." -> STE: "The ohmmeter shows 450 ohms."

### Rule 4.1 — Write short and clear sentences (default severity: error)
Statement: Write short sentences with clear structure that give accurate instructions and information. In procedures, give instructions directly to the reader in the imperative form; in descriptive text, give each sentence only one topic and build up information gradually across the sentences that follow, and never write abstract statements that omit the accuracy the reader needs.
Rewrite guidance: Split multi-action or multi-topic sentences into a vertical list of imperative steps (procedures) or into separate single-topic sentences that build on each other (descriptive text). Replace abstract statements with concrete instructions or specific facts and values.
Rewrite constraints:
- Do not drop any information when splitting a sentence.
- Keep procedural text in imperative form and descriptive text in descriptive form — do not convert between the two writing styles.
Example — Non-STE: "To remove the cover assembly (9), first remove the four screws (10) that attach the cover (11) to the housing (12), and then, after taking the cover (11) off the housing (12), remove the preformed packing (13) and throw it away." -> STE: "Remove the cover assembly (9) as follows:
A. Remove the four screws (10) that attach the cover (11) to the housing (12).
B. Remove the cover (11) from the housing (12).
C. Remove and discard the preformed packing (13)."

### Rule 4.2 — Do not omit words or use contractions to shorten sentences (default severity: error)
Statement: Write every sentence with all of its parts — do not omit nouns, verbs, subjects, or articles to make the sentence shorter, and do not use contractions such as "don't" or "isn't". Omitted words and contractions make a sentence shorter but not easier to read, and can create ambiguity.
Rewrite guidance: Expand every contraction to its full form, and restore any omitted subject, verb, or article so the sentence is complete and unambiguous.
Rewrite constraints:
- Preserve the original meaning and polarity exactly when expanding a contraction ("don't" becomes "do not", not "do").
Example — Non-STE: "Rotary switch to INPUT." -> STE: "Set the rotary switch to INPUT."

### Rule 4.3 — Use a vertical list for complex text (default severity: warning)
Statement: When a sentence would otherwise be long because it includes many items (such as parts, components, or documents) or many actions, present those items as a vertical list instead. Introduce the list with a colon, mark each item consistently (dash, bullet, letter, or number), start each item with an uppercase letter, and punctuate the items according to whether each is a full sentence.
Rewrite guidance: Convert the introductory clause to end in a colon, then list each item on its own line with a consistent marker, capitalized, each ending in a period only if it is a full sentence, with a period always after the final item.
Rewrite constraints:
- Keep all items at a single list level — flatten any nested sub-list into a parenthetical or in-line note rather than nesting it (this is how the standard's own worked examples handle an item that itself has sub-items).
- Do not mix procedural and descriptive content within the same list.
Example — Non-STE: "The wheel assembly comprises the tire, the tube, the spokes, the spoke fittings, the valve, and the hub." -> STE: "The wheel assembly has these parts:
- The tire
- The tube
- The spokes
- The spoke fittings
- The valve
- The hub."

### Rule 4.4 — Use connecting words and phrases to link related sentences (default severity: warning)
Statement: Use an approved connecting word (such as "and", "but", "then", "thus"), an approved connecting phrase (such as "as a result", "at the same time"), or a demonstrative adjective to link a sentence to the related idea in the sentence before it, giving descriptive text a logical structure and clarifying explanations that follow a work step or a safety instruction.
Rewrite guidance: Where the logical relationship between adjacent sentences is genuinely unclear, add an approved connecting word or phrase, or a demonstrative adjective, at the start of the dependent sentence to make it explicit.
Rewrite constraints:
- Use only connecting words or phrases approved in the STE dictionary.
- Keep the linked sentences separate — do not merge them into a single sentence.
- Do not insert a connector into every adjacent sentence pair regardless of need.
Example — Non-STE: "Tag the disassembled parts. It will help you during the subsequent procedures." -> STE: "Tag the disassembled parts. This method will help you during the subsequent procedures."

### Rule 4.5 — Use an article or demonstrative adjective before a noun (default severity: error)
Statement: When applicable, use an article (the, a, an) or a demonstrative adjective (this, these) before a noun or multi-word noun to show its position in the sentence; do not omit it to shorten the text. Do not use an article before a noun in a general statement or abstract concept, and do not use a definite article before a noun that is followed by an alphanumeric identifier, since the identifier makes it a proper noun.
Rewrite guidance: Insert the correct article or demonstrative adjective immediately before the noun or multi-word noun. If the noun is followed by an alphanumeric identifier, remove any definite article before it.
Rewrite constraints:
- Do not add an article before a noun in a general statement or abstract concept.
- When adding articles across a series of items, choose consistently between one article covering the whole series and an article before each item, based on whether a modifier is meant to apply to all items or only one.
Example — Non-STE: "Turn shaft assembly." -> STE: "Turn the shaft assembly."

### Rule 5.1 — Write short sentences with a maximum of 20 words (default severity: error)
Statement: In procedural writing, including warnings, cautions, and other safety instructions, write short sentences with a maximum of 20 words each. If a sentence is longer than 20 words, split it into two or more shorter sentences rather than leaving it as one long sentence.
Rewrite guidance: Split a sentence over 20 words into two or more shorter sentences at a natural break (e.g. before "until" or "then"). Keep the resulting sentences together within the same work step if the actions are simultaneous or one is an immediate continuation of the other; otherwise place each in its own numbered work step.
Rewrite constraints:
- Do not omit any instructional content when splitting a sentence.
- Do not create a new numbered work step for an action that must occur at the same time as the preceding action.
Example — Non-STE: "Put preservation oil into the unit through the vent hole until the oil level is approximately 6 mm (0.24 inches) below the surface of the flange cover." -> STE: "Put preservation oil into the unit through the vent hole. Continue until the oil level is approximately 6 mm (0.24 in) below the surface of the flange cover."

### Rule 5.2 — Write only one instruction per sentence unless actions are simultaneous (default severity: error)
Statement: Write only one instruction in each sentence of a procedure, and clearly show the sequence of work steps, usually with numbers or letters. Write more than one instruction in a single sentence only when the actions occur at the same time; you may also write more than one sentence within a single work step when the actions are simultaneous or when a result or limit follows immediately after the action.
Rewrite guidance: If the instructions are independent and sequential, split them into separate numbered or lettered work steps with one instruction each. If the actions occur at the same time, keep them as a single sentence joined by "and". If a sentence states a result or limit immediately following an action, keep it as an additional sentence within the same work step.
Rewrite constraints:
- Do not split instructions for actions that must occur at the same time into separate numbered steps.
- Do not merge genuinely sequential, independent instructions into a single sentence.
Example — Non-STE: "Set the TEST switch to the middle position and release the SHORT-CIRCUIT TEST switch." -> STE: "A. Set the TEST switch to the middle position.
B. Release the SHORT-CIRCUIT TEST switch."

### Rule 5.3 — Write instructions in the imperative form (default severity: error)
Statement: Write every instruction in a procedure using the imperative (command) verb form, addressed directly to the reader, rather than passive voice or a statement about capability or permission. Do not use "must" immediately before the imperative form unless the instruction is safety-critical or states an important condition.
Rewrite guidance: Rewrite the instruction as a direct command beginning with the imperative verb, addressed to the reader. Remove "must" unless the instruction is safety-critical or conditional.
Rewrite constraints:
- Preserve the original action and its object exactly; do not change who performs the action.
Example — Non-STE: "The test can be continued." -> STE: "Continue the test."

### Rule 5.4 — State a leading condition as a descriptive statement, separated by a comma (default severity: error)
Statement: When a work step depends on a condition the reader must know about first, start the instruction with a descriptive statement of that condition, then divide the condition from the command with a comma, placing the imperative instruction after the comma.
Rewrite guidance: Move the condition (the "if"/"when" clause) to the start of the sentence, place a comma at the end of the condition, and follow it with the imperative command.
Rewrite constraints:
- Place the comma precisely at the boundary between the condition and the command — a misplaced comma can change which verb an adverb modifies and alter the sentence's meaning.
Example — Non-STE: "Set the switch to NORMAL when the light comes on." -> STE: "When the light comes on, set the switch to NORMAL."

### Rule 5.5 — Write notes only to give information, not instructions (default severity: error)
Statement: A note must give only descriptive information to help the reader during a procedure — never an instruction, requirement, or limit. Do not use the imperative form in a note, and do not use a note to state a result, tolerance, or limit that belongs directly in the related work step; each sentence in a note may have up to 25 words.
Rewrite guidance: If the note contains a command, move it into the procedure as a new numbered work step. If it contains safety-critical information, convert it to a WARNING or CAUTION. If it contains a limit or result tied to a work step, move that content directly into the relevant step, immediately after the action. After moving content out of a note, re-apply the note-validity test (remove all remaining notes and confirm the procedure is still complete and correct) until it passes.
Rewrite constraints:
- Relocate the information to the correct place (work step, WARNING/CAUTION, or in-step limit) rather than deleting it.
Example — Non-STE: "NOTE: Make sure that the avionics ventilation system continues to operate correctly." -> STE: "(6) Make sure that the avionics ventilation system continues to operate correctly."

### Rule 6.1 — Give information gradually (default severity: warning)
Statement: In descriptive text, present information gradually and make sure each sentence contains only one subject. Do not pack multiple facts or ideas about different subjects into one sentence, since this forces the reader to re-read the text to understand it.
Rewrite guidance: Break the dense passage into a sequence of short sentences that each introduce one idea, building progressively from the general identity/function of the item toward more specific details.
Rewrite constraints:
- Do not drop any technical fact from the original text — redistribute it across the new sentences instead of removing it.
Example — Non-STE: "During the approach to the runway, deviation pointers in the course indicators give commands to fly up or down and left or right. This information comes from the VHF transceivers, which are part of the Instrument Landing System." -> STE: "The Instrument Landing System (the system) on the aircraft shows data that helps the pilot during the approach to the runway. This system shows the pilot the deviations from the localizer course and the glideslope path. During the approach to the runway, deviation pointers in the course indicators show the pilot in which direction the aircraft must go."

### Rule 6.2 — Use key words and key phrases to give your text a logical structure (default severity: warning)
Statement: Use key words and key phrases — the same terminology repeated exactly — to connect a sentence to the ideas introduced earlier in the paragraph (not necessarily only the immediately preceding sentence), and use approved connecting words or phrases (for example, "and," "but," "then," "thus," "as a result," "at the same time") as one method, among others, to signal how a sentence relates to an earlier one. This gives the text a logical, easy-to-follow structure.
Rewrite guidance: Where a reference is ambiguous, reuse the exact key word or key phrase from the earlier sentence it refers to instead of a synonym. Where a logical relationship is unclear, insert an approved connecting word or phrase to make it explicit.
Rewrite constraints:
- Do not substitute a synonym for an already-clear reference just for variety — when repetition is needed for clarity, the repeated term must be identical to the one used earlier (see rule 1.11).
- Do not insert a connecting word into every sentence pair regardless of need — only where the relationship is otherwise unclear.
Example — Non-STE: "The Instrument Landing System (the system) on the aircraft shows data that helps the pilot during the approach to the runway. The unit displays the deviations from the localizer course and the glideslope path." -> STE: "The Instrument Landing System (the system) on the aircraft shows data that helps the pilot during the approach to the runway. This system shows the pilot the deviations from the localizer course and the glideslope path."

### Rule 6.3 — Write short sentences — maximum 25 words in descriptive text (default severity: error)
Statement: In descriptive writing, use a maximum of 25 words per sentence. Descriptive text is permitted a higher word count than procedural text because its subject matter is inherently more complex, but any sentence over the limit must still be split into shorter sentences.
Rewrite guidance: Split the over-length sentence at a natural clause boundary into two or more sentences of 25 words or fewer, adding a key word or connecting word (rule 6.2) between them to preserve the logical link.
Rewrite constraints:
- Preserve every technical fact from the original sentence — do not shorten by deleting content.
Example — Non-STE: "A smartphone is a cellular telephone that has an integrated computer and many other functions, such as an operating system, internet browsing as well as the ability to run software applications." -> STE: "A smartphone is a cellular telephone that has an integrated computer and many other functions. It includes an operating system and an internet browser, and it can also operate software applications."

### Rule 6.4 — Use paragraphs to show related information (default severity: warning)
Statement: Structure descriptive text into paragraphs, where each paragraph opens with a topic sentence that states what the paragraph is about, and every following sentence explains or adds information related to that topic. A new paragraph signals to the reader that a new or different topic follows.
Rewrite guidance: Identify the natural groupings of related information in the text and insert paragraph breaks so that each paragraph begins with a topic sentence naming its subject, followed only by sentences that elaborate that same topic.
Rewrite constraints:
- Preserve any existing numbering or lettering scheme (e.g., '(1)', '(2)', 'A.') used to label the descriptive content — do not renumber items unnecessarily.
Example — Non-STE: "A lightning strike can cause damage to the aircraft at the attachment points. From the attachment points, the lightning strike usually goes aft through the structure and can cause a malfunction of the electrical and electronic systems. If a lightning strike occurs, the maintenance personnel must do an inspection of the aircraft for damage before the next flight." -> STE: "A lightning strike can cause damage to the aircraft. The damage usually occurs at the attachment points.

From the attachment points, the lightning strike usually goes aft through the structure of the aircraft. The high current of the lightning strike can cause damage to the mechanical systems of the aircraft. Thus, a permanent or a temporary malfunction of the electrical and electronic equipment and systems can occur.

If a lightning strike occurs, it is necessary to do an inspection of the aircraft for damage. The maintenance personnel must do this inspection before the next flight."

### Rule 6.5 — Make sure that each paragraph has only one topic (default severity: warning)
Statement: Each paragraph in descriptive text must cover exactly one topic. The topic sentence — usually containing a key word and/or a connecting word or phrase — states that topic, and every other sentence in the paragraph must relate to it; do not combine two or more distinct topics in the same paragraph.
Rewrite guidance: Split the paragraph at the point where the topic changes, and give the new paragraph its own topic sentence introducing the new subject.
Rewrite constraints:
- Relocate off-topic sentences to an appropriate paragraph rather than deleting the information they contain.
Example — Non-STE: "The Instrument Landing System (the system) on the aircraft shows data that helps the pilot during the approach to the runway. This system shows the pilot the deviations from the localizer course and the glideslope path. This data about deviations from the localizer course and glideslope path comes from two VHF transceivers. These transceivers transmit this data to Air Traffic Control." -> STE: "The Instrument Landing System (the system) on the aircraft shows data that helps the pilot during the approach to the runway. This system shows the pilot the deviations from the localizer course and the glideslope path.

This data about deviations from the localizer course and glideslope path comes from two VHF transceivers. These transceivers transmit this data to Air Traffic Control."

### Rule 6.6 — No paragraph may have more than six sentences (default severity: error)
Statement: Limit each paragraph in descriptive text to a maximum of six sentences. If a paragraph would require more than six sentences, divide it into two or more smaller paragraphs, each covering a distinct part of the topic.
Rewrite guidance: Divide the over-length paragraph into two or more smaller paragraphs at a logical topic boundary, giving each new paragraph its own topic sentence (rule 6.4) and no more than six sentences.
Rewrite constraints:
- Keep any item numbering or part-number labels (e.g., '(25)', '(27)') unchanged when redistributing sentences.
Example — Non-STE: "The shut-off valve operates in the valve body (21). The valve body (21) has an aluminum alloy ball (27), a retaining ring (31), two seals (26), and a spring (25). The spring (25) holds the ball (27) in position to prevent internal leakage. The preformed packings (18), (2) and (30) are installed on the seals (26), the shaft (28), and in the valve body. They prevent external leakage. One of the two seals (26), on which the spring (25) operates, has the function of a relief valve. It operates when the pressure applied in the opposite direction is more than a set value." -> STE: "The shut-off valve operates in the valve body (21). The valve body (21) has an aluminum alloy ball (27), a retaining ring (31), two seals (26), and a spring (25).

The spring (25) holds the ball (27) in position to prevent internal leakage. The preformed packings (18), (2) and (30) are installed on the seals (26), the shaft (28), and in the valve body. They prevent external leakage. One of the two seals (26), on which the spring (25) operates, has the function of a relief valve. It operates when the pressure applied in the opposite direction is more than a set value."

### Rule 7.1 — Use an applicable word to identify the level of risk (default severity: error)
Statement: Immediately identify the level of risk in a safety instruction with an applicable signal word (or symbol) — use "warning" when there is a risk of injury or death, and "caution" when there is only a risk of damage to objects, tools, or equipment. If both a warning-level and a caution-level risk are present together, label the instruction as a "warning."
Rewrite guidance: Determine the true severity of the hazard from its described consequences (injury/death vs. property damage only) and prefix the instruction with the matching signal word — "WARNING" for injury/death or combined risks, "CAUTION" for damage-only risks — rewriting any vague hazard language into a concrete statement of what can happen.
Rewrite constraints:
- Do not downgrade a warning to a caution to soften the tone — the signal word must match the actual severity of the risk described, not the writer's preference.
Example — Non-STE: "CAUTION: EXTREME CLEANLINESS OF OXYGEN TUBES IS IMPERATIVE." -> STE: "WARNING: MAKE SURE THAT THE OXYGEN TUBES ARE FULLY CLEAN. OXYGEN AND GREASE MAKE AN EXPLOSIVE MIXTURE. AN EXPLOSION CAN CAUSE INJURY OR DEATH."

### Rule 7.2 — Start a safety instruction with a clear and accurate command or condition (default severity: error)
Statement: Begin a safety instruction with a clear, accurate command telling the reader what to do or not do; if the reader needs to know a condition before starting the procedure or work step, begin with that condition instead. Either way, the actionable part must come first so the reader immediately knows how to prevent an accident.
Rewrite guidance: Rewrite the opening of the safety instruction as a direct command (e.g., "Do not..." / "Always make sure that...") or, when a condition must be known first, open with a "when"/"while" clause stating that condition — then follow with the explanation of risk required by rule 7.3.
Rewrite constraints:
- Keep the command in direct imperative/second-person form; do not bury it in the middle or end of the sentence.
Example — Non-STE: "WARNING: THE SPRAY PAINT CAN CAUSE INJURY TO YOUR EYES. WHILE YOU USE THE SPRAY PAINT, POINT THE SPRAY AWAY FROM YOUR FACE." -> STE: "WARNING: WHILE YOU USE THE SPRAY PAINT, POINT THE SPRAY AWAY FROM YOUR FACE. THE SPRAY PAINT CAN CAUSE INJURY TO YOUR EYES."

### Rule 7.3 — Give an explanation to show the risk or possible result (default severity: warning)
Statement: If it is possible, after the command or condition in a safety instruction (rule 7.2), give an explanation that clearly states the specific risk or possible result if the reader does not obey it. A concrete, specified risk helps the reader understand why the precaution matters and makes them more likely to follow it. The explanation is conditional on it being possible to state — not every WARNING or CAUTION is automatically non-STE for omitting one.
Rewrite guidance: Where it is possible to state the risk or result, add a concise sentence after the command/condition naming the specific injury, damage, or hazard mechanism, using specific technical language instead of generic danger language.
Rewrite constraints:
- Keep the explanation factual and specific to the described hazard; do not invent a risk that is not supported by the context.
- Do not assert a missing explanation is a definite error when the risk/result cannot be determined from the available text — flag it for review instead.
Example — Non-STE: "CAUTION: DO NOT USE BLEACH OR CLEANSERS THAT CONTAIN CHLORINE TO CLEAN THE UNIT." -> STE: "CAUTION: DO NOT USE BLEACH OR CLEANSERS THAT CONTAIN CHLORINE TO CLEAN THE UNIT. THESE CLEANING AGENTS CAN CAUSE CORROSION."

### Rule 8.1 — Do not use the semicolon (default severity: error)
Statement: You can use all standard English punctuation marks except the semicolon (;). Where a semicolon would normally join two related independent clauses, write two separate sentences instead.
Rewrite guidance: Split the sentence at the semicolon into two separate, complete sentences, each ending with its own period. Adjust wording as needed so each half is a grammatically complete, standalone sentence.
Rewrite constraints:
- Do not replace the semicolon with a comma to form a comma splice.
- Do not merge the two clauses back into one sentence with a conjunction unless the result still obeys the applicable sentence word-count limit.
Example — Non-STE: "Examine the removed parts; replace the damaged ones." -> STE: "(1) Examine the removed parts for damage. (2) Replace the damaged part(s)."

### Rule 8.2 — Use hyphens to connect words that are directly related (default severity: warning)
Statement: Use a hyphen (-) to connect two or more words that are directly related, including multi-word adjectives before a noun, two-word numbers or fractions, letter/number-plus-noun shape terms, noun-derived compound verbs, and prefixes ending in a vowel joined to a root word starting with a vowel.
Rewrite guidance: Insert a hyphen between the directly related words to form the compound term, following the pattern that applies (compound adjective before a noun, two-word number, letter/number-plus-noun shape term, noun-derived verb, or vowel-ending-prefix plus vowel-starting root).
Rewrite constraints:
- Only hyphenate words that are genuinely directly related; do not hyphenate unrelated adjacent words.
- Do not turn a hyphen into a dash or a dash into a hyphen.
Example — Non-STE: "Check the low altitude flight envelope." -> STE: "Check the low-altitude flight envelope."

### Rule 8.3 — Use parentheses only for these seven approved purposes (default severity: warning)
Statement: Use parentheses only to: reference an illustration or other text; give a letter or number identifying an item on an illustration or in text; identify a work-step number in a procedure; show an abbreviation; give the singular and plural forms of a noun together; explain a word or part of a sentence; or present an alternative.
Rewrite guidance: If the parenthetical content matches one of the seven approved uses, keep it in parentheses in the standard format shown in the examples. If it does not fit any of the seven uses, move the information into the main sentence or into a separate sentence instead of parentheses.
Rewrite constraints:
- Preserve index numbers and letters exactly as given; do not drop them when rewriting.
- Do not compress unrelated information into a parenthetical explanation just to shorten the sentence.
Example — Non-STE: "A Liquid Crystal Display flat-panel display uses the light-modulating properties of liquid crystals." -> STE: "A Liquid Crystal Display (LCD) is a flat-panel display that uses the light-modulating properties of liquid crystals."

### Rule 8.4 — In a vertical list, a colon has the effect of a period on word count (default severity: warning)
Statement: When a colon introduces a vertical list, it acts like a period: the lead-in text before the colon must not exceed the applicable sentence word-count limit (20 words for a procedural sentence, 25 words for a descriptive sentence), and each item after the colon is counted as a new, independent sentence subject to that same limit.
Rewrite guidance: Shorten the lead-in text before the colon and/or any oversized list item so each falls within its applicable word-count limit, moving excess detail into the item text or a preceding sentence as needed. If one item needs sub-detail, fold it into a parenthetical at the same list level (per rule 4.3) rather than nesting a sub-list.
Rewrite constraints:
- Keep the vertical list structure and the colon; do not flatten the list into a run-on sentence to sidestep the limit.
- Keep all items at a single list level, consistent with rule 4.3 — do not introduce a nested sub-list as a workaround.
Example — Non-STE: "To extinguish a possible fire, portable fire extinguishers are installed in these different areas of the aircraft that are described in more detail in the maintenance manual and its supplements:" -> STE: "To extinguish a possible fire, portable fire extinguishers are installed in these areas: - The cockpit - The cabin - The cabin sub-compartment - The crew rest compartment."

### Rule 8.5 — Text in parentheses counts as one word (default severity: info)
Statement: When counting words for a sentence's word-count limit, count an entire parenthetical remark as exactly one word of that sentence, regardless of how many words it actually contains. The words inside the parentheses are also counted separately as their own independent sentence against its own limit. A parenthetical identifier (a number, a letter, an alphanumeric identifier, or an abbreviation) likewise counts as one word.
Rewrite guidance: When determining whether a sentence exceeds its word-count limit, recompute the total by treating the whole parenthetical as one word before deciding the sentence needs shortening.
Rewrite constraints:
- Do not delete or shorten parenthetical content merely because of a miscounted word total.
Example — Non-STE: "Make sure that the EMER pushbutton switch is released. The EMER legend is off." -> STE: "Make sure that the EMER pushbutton switch is released (the EMER legend is off)."

### Rule 8.6 — Count numbers, units, abbreviations, identifiers, quoted text, titles, and proper nouns as one word each (default severity: info)
Statement: When counting words for a sentence's word-count limit, count each of the following as a single word: a standalone number; a number together with its unit of measurement; an abbreviation, acronym, or initialism; an alphanumeric identifier; a block of quoted text (including text distinguished by uppercase or a different font to show quotation); a title, heading, or text reproduced from a placard or label; and a proper noun naming an individual, group, organization, or geopolitical entity. Numbers that are only paragraph or work-step numbering are not counted at all.
Rewrite guidance: When deciding whether a sentence exceeds its word-count limit, recompute the count using these one-word groupings before shortening anything; never split, paraphrase, or shorten a title, heading, placard/label text, or proper noun just to reduce an inflated word total.
Rewrite constraints:
- Never alter the wording of a quoted title, heading, placard, label, or proper noun to change its word count.
Example — Non-STE: "The maintenance team does a test of this system each day at 10 a.m." -> STE: "The maintenance team does a test of this system each day at 10 a.m."

### Rule 8.7 — Hyphenated words count as one word (default severity: info)
Statement: A hyphenated group of words that functions as a single adjective before a noun, or as a compound technical noun built for clarity, counts as one word when counting sentence length — even though it is made of multiple hyphen-joined components.
Rewrite guidance: When calculating sentence word count, treat each whitespace-delimited hyphenated word group as exactly one word; do not inflate the count by counting each hyphen-joined component separately, and do not collapse multiple separate hyphenated groups in one phrase into a single word count.
Rewrite constraints:
- Do not remove a correctly placed hyphen (see rule 8.2) in order to manipulate the word count.
Example — Non-STE: "Clean the surface with a solution of soap and water." -> STE: "Clean the surface with a soap-and-water solution."

### Rule 9.1 — Use a different sentence construction when a word-for-word replacement is not enough (default severity: warning)
Statement: When a non-approved word cannot simply be swapped for an approved word with the same part of speech and the same meaning, do not force a literal word-for-word replacement. Instead, restructure the whole sentence using approved words so it preserves the original meaning clearly and grammatically.
Rewrite guidance: Determine the precise intended meaning of the non-approved word in context, then rebuild the sentence with approved words and whatever grammatical structure conveys that exact meaning naturally — this may mean changing the verb, adding a phrase such as 'make sure that,' or splitting the sentence.
Rewrite constraints:
- Never choose a substitute word solely because it is approved if it does not preserve the original meaning.
- Verify the reconstructed sentence is grammatically correct standard English, not just an approved-word patchwork of the original.
Example — Non-STE: "The oil level on the sight gauge must be visible during the test." -> STE: "During the test, make sure that you can see the oil level on the sight gauge."

### Rule 9.2 — Use each approved word only with its approved meaning and approved part of speech (default severity: error)
Statement: Many STE-approved words carry only one approved meaning and/or one approved part of speech, which can be narrower than their meanings in standard English. Always use an approved word only in the sense and grammatical role the dictionary assigns it, never in another standard-English sense or part of speech it happens to also have.
Rewrite guidance: Replace the misused word with an approved word (or short approved phrase) that actually carries the intended meaning in its approved sense and part of speech, restructuring the sentence as needed to stay grammatical.
Rewrite constraints:
- Confirm the replacement word's approved meaning genuinely matches the intended sense before substituting it — do not chain into a second misuse.
Example — Non-STE: "Wear protective clothing." -> STE: "Use (or put on) protective clothing."

### Rule 9.3 — Do not combine approved words into phrasal verbs (default severity: error)
Statement: Do not combine an approved verb with a preposition or particle to form a phrasal verb whose combined meaning differs from the individual approved meanings of its parts (e.g. 'put out' meaning 'extinguish'). Use the single approved word that expresses the intended meaning instead. A small number of phrasal verbs with a restricted approved meaning (e.g. 'put on', 'come on') are dictionary exceptions and remain permitted.
Rewrite guidance: Replace the phrasal verb with the single approved word that carries its intended abstract meaning (e.g. 'extinguish' for 'put out' a fire, 'release' for 'give off' fumes).
Rewrite constraints:
- Do not leave the phrasal verb in place even if both of its component words are individually approved — it is the combination itself that is disallowed.
Example — Non-STE: "After you put out the fire, close the valve on the fire extinguisher." -> STE: "After you extinguish the fire, close the valve on the fire extinguisher."

### Rule 9.4 — Use consistent terminology and wording for the same item and the same type of work step (default severity: warning)
Statement: Once you choose a technical noun for an item, or a sentence style/wording for a recurring type of instruction, use that exact same term and wording every time that item or instruction type occurs in the text, rather than varying the phrasing for the sake of variety.
Rewrite guidance: Pick one term for each item and one sentence style for each recurring type of work step, then apply that exact term or wording every time that item or work-step type recurs in the text.
Rewrite constraints:
- Do not merge references to genuinely different items or different actions into the same wording just to force consistency.
Example — Non-STE: "Put the housing (8) in its installation position on the main body (9). Lubricate the two bolts (10) with oil." -> STE: "Put the housing (8) in its installation position on the body assembly (9). Apply a small quantity of oil to the threads of the two bolts (10)."

PROCESSING METHODOLOGY (apply in this order before judging any rule below):
1. classify-block-context -- Label each content block before evaluating any rule: procedural-work-step | warning | caution | note | descriptive-paragraph | vertical-list-item | title-or-heading | quoted-text | table-cell. Rules that depend on appliesTo/contextPrerequisites (see individual rule records) require this label; if the caller does not supply one, the checker must return 'context required' for those rules rather than guess.
2. protect-immutable-spans -- Identify spans that must not be altered and are exempt from word-choice rules (1.x, 9.x) and count as one word (rule 8.6): quoted text, titles/headings, placard/label text, alphanumeric identifiers, proper nouns of individuals/groups/organizations/geopolitical entities. The rule 8.1 semicolon prohibition and rule 1.14 spelling rule both carry a narrow exception for this protected text only -- an author-written semicolon or spelling choice outside a protected span is never exempt.
3. segment-sentences-and-lists -- Split each block into sentences on '.', '!', '?' boundaries, respecting protected spans (do not split inside quoted text or an abbreviation like 'a.m.'). For vertical lists (rule 4.3), the colon before the list has the effect of a period (rule 8.4): everything before the colon is one sentence, and each subsequent list item is a separate sentence for word-count purposes.
4. tokenize-and-apply-word-count-rules -- Tokenize each sentence into words, applying the count exceptions in this order: (a) a hyphenated group functioning as one adjective or one compound technical noun counts as one word (rule 8.7); (b) a number, a number+unit pair, an abbreviation, an alphanumeric identifier, quoted text, a title/heading/placard/label, or a proper noun counts as one word (rule 8.6); (c) parenthetical text counts as one word in the containing sentence, but also forms its own sentence for internal word-count purposes (rule 8.5).
5. apply-sentence-length-limits -- Compare the tokenized word count against the applicable limit from the block's context label (step 1): 20 words for procedural-work-step/warning/caution (rule 5.1), 25 words for note (rule 5.5) and descriptive-paragraph (rule 6.3). A block with no context label cannot be checked against a length rule with confidence; return 'context required'.
6. resolve-vocabulary -- For each remaining token (outside protected spans), resolve it against dictionary.json first, then against the configured termbase (termbase-schema.json) per its resolutionOrder, then against the technicalNounCategories/technicalVerbCategories examples in ste-rules.json rules 1.5/1.12 as supporting (not sufficient) evidence. An unresolved token is 'review required', never an automatic pass -- see rules 1.1-1.4, 1.6, 1.8, 3.1, 3.3, 3.7, 9.1-9.3.
7. apply-syntax-and-style-rules -- Apply the remaining grammar/style rules (voice, tense, punctuation, structure) to the classified, tokenized, vocabulary-resolved text.

CROSS-RULE PRECEDENCE (use this to decide which rule governs when more than one could match the same text):
- Conflict: Rules 3.3 (past participle as adjective), 3.4 (no auxiliary + participle complex constructions), and 3.6 (active voice / permitted descriptive passive) can all match the same surface form 'is/are/was/were + past participle'.
  1) If the participle describes a state/condition (before a noun, or after to be/become/stay, with no implied agent performing an action) -> rule 3.3 governs; compliant if the participle is dictionary-approved.
  2) Else, if the sentence is descriptive writing and the agent is genuinely unknown/unknowable -> rule 3.6's permitted descriptive passive governs; compliant.
  3) Otherwise -> rule 3.4 governs; flag as a disallowed complex/passive construction.
- Conflict: Rules 1.1/1.6 (word approval) vs. 1.5/1.12 (technical noun/verb categories) vs. 1.8 (company/industry/subject-field term).
  1) Dictionary lookup first (dictionary.json): if approved and used with its approved meaning/part of speech, compliant under 1.1-1.4.
  2) If not approved or absent from the dictionary: check whether an approved company/industry/subject-field term exists for the concept (termbase.json) -- if so, that exact term must be used (rule 1.8) in preference to inventing or generalizing.
  3) If no termbase entry exists: check technical-noun (1.5) / technical-verb (1.12) category fit as supporting evidence, returning 'review required' rather than an automatic pass when category fit is the only evidence.
- Conflict: Rule 8.1 (no semicolon) vs. rule 8.6/step-2 protected spans.
  1) A semicolon inside a protected/immutable span (quoted label, placard, verbatim title) is not a violation.
  2) A semicolon anywhere else in author-written text is always a violation, regardless of clause structure.

Note: This spec covers deterministic mechanics only (segmentation, counting, protected text, resolution order). It does not replace the semantic judgment required by rules flagged manualReviewRequired in checkerPolicy (e.g. 1.8, 1.12, 4.3, 4.4, 6.2, 7.3) -- those still require an LLM call or human review per rule.

STE BACKGROUND (foundational conventions the rules above assume):
- STE does not give rules for abbreviations, text formatting (typeface, numbering, lettering), or units of measurement -- those are left to applicable technical-publication specifications, style guides, and other official directives.
- STE is not a complete grammar reference and cannot be used alone -- it is intended to be used together with other applicable specifications and directives.
- STE approved meanings and spelling are based on American English and the Merriam-Webster's Collegiate Dictionary (11th ed.).

COMMONLY MISUSED WORDS (the standard's own list -- treat as a strong prior, not exhaustive):
- acceptable (adj) -> PERMITTED (adj)
- alternate (adj) -> ALTERNATIVE (adj)
- any (adj) -> None or a different sentence construction
- avoid (v) -> PREVENT (v)
- both (adj) -> THE TWO (TN)
- check (v) -> CHECK (n)
- cover (v) -> COVER (TN)
- complete (adj) -> COMPLETED (adj)
- damage (v) -> DAMAGE (n)
- ensure (v) -> MAKE SURE (v)
- fit (v) -> INSTALL (v)
- follow (v) -> OBEY (v)
- further (adj) -> MORE (adj)
- further (adv) -> MORE (adv)
- have to (v) -> Use an action verb in the imperative form
- however (adv) -> BUT (conj)
- insert (v) -> PUT (v)
- main (adj) -> PRIMARY (adj)
- may (v) -> CAN (v)
- need (v) -> NECESSARY (adj)
- now (adv) -> AT THIS TIME
- old (adj) -> REMAINING (adj), USED (adj), EXPIRED (adj)
- over (prep) -> ABOVE (prep), ON (prep), ALONG (prep)
- people (n) -> PERSON (n), PERSONNEL (n)
- perform (v) -> DO (v)
- portion (n) -> PART (n)
- press (v) -> PUSH (v)
- reach (v) -> GET (v)
- repeat (v) -> DO (v) ... AGAIN
- required (v) -> NECESSARY (adj)
- rotate (v) -> TURN (v)
- secure (v) -> ATTACH (v), SAFETY (v)
- shall (v) -> MUST (v)
- should (v) -> MUST (v)
- since (conj) -> BECAUSE (conj)
- test (v) -> TEST (n)
- therefore (adv) -> THUS (adv), AS A RESULT
- under (prep) -> BELOW (prep), IN (prep), LESS THAN
- using (v) -> USE (v), WITH (prep)

TEXT TO REWRITE:
"""
<PASTE THE TEXT TO EVALUATE HERE>
"""

INSTRUCTIONS:
- Rewrite the full text, not just the violating parts; parts that already comply should be left unchanged.
- Every entry in "changeLog" must reference one of the rule ids listed above and correspond to an actual change you made.
- Do not remove technical content, quantities, or safety information.
- If nothing needed to change, "changeLog" should be an empty array and "rewrittenText" should equal the input text.

Respond with ONLY valid JSON (no markdown code fences, no commentary) matching this shape:
{
  "rewrittenText": "the full rewritten text",
  "changeLog": [
    {
      "ruleId": "1.1",
      "original": "original snippet",
      "revised": "revised snippet",
      "reason": "why this change was made"
    }
  ]
}

{
  "rewrittenText": "the full rewritten text",
  "changeLog": [
    {
      "ruleId": "1.1",
      "original": "original snippet",
      "revised": "revised snippet",
      "reason": "why this change was made"
    }
  ]
}