Term checker rules for ASD-STE100 issue 8

Archive: Term checker rules for ASD-STE100 issue 7.

ASD-STE100 issue 8 rules

The term checker is not a grammar checker. Before you use the term checker, make sure that the text is correct English. The term checker finds many ASD-STE100 errors in text that does not conform to standard English grammar, but it does not find all errors.

ASD-STE100 issue 8 rules that the term checker uses
Rule number	Summary of rule	Comment
1.1	Use approved words from the dictionary, technical names (TNs), and technical verbs (TVs).	The term checker finds unapproved terms, approved terms that possibly are used incorrectly, and unknown terms. You must add your organization's technical names and technical verbs to the term checker. The term checker gives suggestions for approved alternatives of some unknown terms, if the unknown term is an approved term that has an unapproved prefix or suffix. Example for the term 'inaccurately': `STE 8, rule 1.1. The adverb 'ACCURATELY' is approved, but 'inaccurately' (possibly is prefix+adverb) is undefined. Use the adverb.`
1.2	Use an approved dictionary word only with the approved part of speech.	Most of the part-of-speech rules are for nouns and verbs. If an approved adjective is used as a noun, the term checker does not give a warning. For example, for the sentence, "When a general tells you to ...", the term checker does not give a warning about the noun general. For problems of disambiguation, refer to Use a word only with the approved part of speech (rule 1.2).
1.3	Use an approved word only with its approved meaning.	Refer to Use a word with its approved meaning (rule 1.3).
1.4	Use only the approved forms of verbs and adjectives.
1.5	Use words that that you can include in a technical name category.	The term checker includes a set of basic TNs. You must add other technical names to disambiguation-projectterms.xml.
1.6	Use an unapproved word only if it is a technical name or part of a technical name.
1.7	Do not use a technical name as a verb.
1.8	Use technical names that agree with the approved nomenclature.	Refer to the comment for rule 1.5.
1.9	When you must select a technical name, use one which is short and easy to understand.	The term checker cannot help you to select your organization's technical names. Select the technical names and the unapproved alternatives before you start to write the technical documentation. Refer to Case study: text simplification for shipping procedures.
1.10	Do not use slang or jargon words as technical names.	The term checker finds all slang and jargon words that are not approved or are unknown.
1.11	Do not use different technical names for the same thing.	To identify this problem, you must add the unapproved alternatives to grammar-projectterms.xml. For examples, refer to rulegroup `PROJECT_RULE_1_11` in `grammar-projectterms.xml`.
1.12	Use words that that you can include in a technical verb category.	The term checker includes a set of basic TVs. You must add other technical verbs to disambiguation-projectterms.xml.
1.13	Do not use a technical verb as a noun.
1.14	Use American English spelling (unless other official directives tell you differently).	In LanguageTool, Text Language, you can select English (American) or English (British). If you select English British, you must activate rule PROJECT_APPROVED_WORD_INCORRECT_SPELLING_gray_GRAY, which is in grammar-projectterms.xml. Note: for some British English words, the suffixes ize and ization are correct. These words have the language subtag en-GB-oxendict. For example, both energise and energize are correct spellings in British English. As much as possible, the term checker uses the spellings that are approved in ASD-STE100. Thus, you will get an error message if you write energise. If you want to use the ~s spellings, delete the applicable rules that are in PROJECT_RULE_1_14 in grammar-projectterms.xml and add the terms to disambiguation-projectterms.xml.
2.1	Write noun clusters of not more than 3 nouns.
2.2	When a technical name has more than three words, write it in full. Then simplify it as follows: Give a shorter name. Use hyphens.	The term checker does not clarify noun clusters automatically. For each long noun cluster, add the approved term to disambiguation-projectterms.xml and add the unapproved term to grammar-projectterms.xml.
2.3	When applicable, use an article or a demonstrative adjective before a noun.
3.1	Use only those forms of the verb that are given in the dictionary.
3.2	Use the approved forms of the verb to make only: infinitive, imperative, simple present tense, simple past tense, past participle as an adjective, future tense.
3.3	Use the past participle as an adjective.	You can use the past participle as a verb because you can use the passive voice (rule 3.6). The structure of the passive voice is BE + PAST PARTICIPLE.
3.4	Do not use helping verbs to make complex verb structures.
3.5	Use the '-ing' form of a verb only as technical name or as a modifier in a technical name.	A verb cannot be a noun. "the '-ing' form of a verb" means "the '-ing' form of a word".
3.6	Use only the active voice in procedural writing. Use the active voice as much as possible in descriptive writing.	The term checker does not identify procedural text and descriptive text. The rule finds the passive voice in all sentences. Refer to Use only the active voice in procedural writing (rule 3.6)
3.7	Use an approved verb to describe an action (not a noun or other part of speech).	Refer to Use an approved verb to describe an action (not a noun or other part of speech) (rule 3.7).
4.1	Write short and clear sentences.
4.2	Do not omit words or use contractions to make your sentences shorter.	The term checker finds contractions such as don't and isn't, but it does not find omissions.
4.3	Use a vertical list for complex text.	Related rules for hyphens (rule 8.2) find these problems: A hyphen instead of a dash at the start of sentence A colon and a hyphen (:-) at the end of a sentence.
4.4	Use connecting words and phrases to connect sentences that contain related topics.
Section 5	Procedures
Section 6	Descriptive writing
7.1	Use an applicable word to identify the level of risk.	Rule 7.1 uses WARNING and CAUTION, but the rule tells you that other words are possible. Thus, the rule must be a project rule. Refer to rule `PROJECT_RULE_7_1` in grammar-projectterms.xml. If necessary, change the terms in the rules in this rulegroup.
7.2	Start a safety instruction with a clear and simple command or condition.
7.3	Give an explanation to show the specific risk or possible result.
8.1	Use all standard English punctuation marks except the semicolon (;).
8.2	Use hyphens (-) to connect closely related words.	The term checker ignores these hyphenated terms: Three-word adjectives that have the structure number-to-number, for example, three-to-one and four-to-three (part of rule 8.2.1). Two-word fractions and numbers such as forty-seven, ninety-ninth, and three-sixteenths (rule 8.2.2). The term checker ignores units of measurement that are adjectives if the first part of the adjective is a cardinal number, for example 5-liter. The term checker does not ignore five-liter. You must add your organization's hyphenated terms to disambiguation-projectterms.xml.
8.3	You can use parentheses.	The term checker does not have an STE rule for parentheses because rule 8.3 gives no examples of the incorrect use of parentheses. But refer to the Global English Style Guide rule 8.8.6.
8.4	In a vertical list, a colon has the same effect on word count as a full stop.
8.5	When you put text in parentheses, it counts as one word in the sentence.
8.6	Count each of these as one word:
8.7	Hyphenated words count as one word.
9.1	Use a different construction to write a sentence when a word-for-word replacement is not sufficient.	The term checker cannot tell you how to rewrite text.
9.2	Use each approved word correctly.	The term checker helps you, but it cannot make sure that you use a word correctly. The term checker has rules for parts of speech (rule 1.2) and for meanings (rule 1.3).
9.3	When you use two words together, do not make phrasal verbs.	The term checker finds many phrasal verbs if the parts of the verb are together. The term checker does not find a phrasal verb if a noun or a noun phrase is between the parts of the verb.
9.4	When you select terminology or wording, always use a consistent style
GR-1	The conjunction 'that'	The rule is available only for the verb MAKE SURE.
GR-2	The preposition 'with'
GR-3	How to use pronouns
GR-4	The pronoun 'this'
GR-5	False friends	The term checker does not have a rule for GR-5. Unknown terms that are false friends are found by rule 1.1. The specification gives the example disposition, but that term is not approved in the dictionary. If a false friend is an approved term, add a grammar rule in grammar-projectterms.xml to tell writers to use the word correctly.
GR-6	Latin abbreviations

Compare the rules in the TechScribe term checker for ASD-STE100 to the Supported Rules Within the ASD-STE100 Specification for Acrolinx.

Global English Style Guide rules

The term checker includes rules that are derived from The Global English Style Guide by John R Kohl, used with permission.

Guidelines from The Global English Style Guide that the term checker uses
Number	Guideline	Comment
3.12	Write positively	Only for approved adjectives and approved adverbs that contain a prefix of negation and that have the word not in front of the word. Examples: not unusual, not incorrect, not impossible (impossible is not-approved, but possible is approved).
8.1	Ampersands
8.8.6	Do not use (s) to form plural nouns	Although STE rule 8.3 lets you use (s), to make translation as easy as possible, do not use (s).
9.17	Eliminate wordy phrases

Refer also to

The Global English Style Guide: a review

RSS feed