├── LICENSE
├── README.org
├── rules.xml
└── wordlist.txt


/LICENSE:
--------------------------------------------------------------------------------
 1 | BSD 3-Clause License
 2 | 
 3 | Copyright (c) 2022, Joey Eremondi
 4 | All rights reserved.
 5 | 
 6 | Redistribution and use in source and binary forms, with or without
 7 | modification, are permitted provided that the following conditions are met:
 8 | 
 9 | 1. Redistributions of source code must retain the above copyright notice, this
10 |    list of conditions and the following disclaimer.
11 | 
12 | 2. Redistributions in binary form must reproduce the above copyright notice,
13 |    this list of conditions and the following disclaimer in the documentation
14 |    and/or other materials provided with the distribution.
15 | 
16 | 3. Neither the name of the copyright holder nor the names of its
17 |    contributors may be used to endorse or promote products derived from
18 |    this software without specific prior written permission.
19 | 
20 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
21 | AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 | IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
23 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
24 | FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 | DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
26 | SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
27 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
28 | OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
29 | OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
30 | 


--------------------------------------------------------------------------------
/README.org:
--------------------------------------------------------------------------------
1 | Migrated to https://codeberg.org/JoeyEremondi/pl-lt-rules
2 | 


--------------------------------------------------------------------------------
/rules.xml:
--------------------------------------------------------------------------------
  1 | <!-- [[file:README.org::*Avoid contractions][Avoid contractions:1]] -->
  2 | <!-- English rule, 2022-02-16 -->
  3 | <rule id="NO_CONTRACTIONS" name="No Contractions">
  4 |  <pattern>
  5 |   <token regexp='yes'>'m|'re|'ve|'d|'ll|'t</token>
  6 |  </pattern>
  7 |  <message>Do not use contractions in formal writing</message>
  8 |  <short>No contractions</short>
  9 |  <example correction=''>let<marker>'s</marker></example>
 10 |  <example>let us</example>
 11 | </rule>
 12 | <!-- Avoid contractions:1 ends here -->
 13 | 
 14 | <!-- [[file:README.org::*Have to handle 's specially since it's also the possessive][Have to handle 's specially since it's also the possessive:1]] -->
 15 | <!-- English rule, 2022-02-16 -->
 16 | <rule id="S_CONTACTION" name="S_CONTACTION">
 17 |  <pattern>
 18 |   <token postag='PRP|VBZ' postag_regexp='yes'>'s</token>
 19 |  </pattern>
 20 |  <message>In formal writing, 's should only be used for possessives, not as a contraction for "is".</message>
 21 |  <short>Don't use 's as a contraction.</short>
 22 |  <example correction=''>That<marker>'s</marker> the problem, so let's look at the car's engine. Let's look at the car's engine. That's the problem with the car's engine.</example>
 23 |  <example>That is the problem, so let us look at the car's engine.</example>
 24 |  <example correction=''>Let's look at the car's engine.</example>
 25 |  <example>Let us look at the car's engine.</example>
 26 |  <example correction=''>That's the problem with the car's engine.</example>
 27 |  <example>That is the problem with the car's engine.</example>
 28 | </rule>
 29 | <!-- Have to handle 's specially since it's also the possessive:1 ends here -->
 30 | 
 31 | <!-- [[file:README.org::*Avoid all gendered pronouns][Avoid all gendered pronouns:1]] -->
 32 | <!-- English rule, 2022-02-16 -->
 33 | <rule id="NO_GENDERED_PRONOUNS" name="no gendered pronouns">
 34 |  <pattern>
 35 |   <token inflected='yes' regexp='yes'>he|she|his|her</token>
 36 |  </pattern>
 37 |  <message>There are very few cases where gendered pronouns are appropriate in a formal paper. You can never go wrong with "they"</message>
 38 |  <short>"they"</short>
 39 |  <example correction=''><marker>He</marker> proves this She proves this It is her proof It is his proof The proof is hers The proof is his</example>
 40 |  <example>They prove this</example>
 41 |  <example correction=''>She proves this</example>
 42 |  <example>They prove this</example>
 43 |  <example correction=''>It is her proof</example>
 44 |  <example>It is their proof</example>
 45 |  <example correction=''>It is his proof</example>
 46 |  <example>It is their proof</example>
 47 |  <example correction=''>The proof is hers</example>
 48 |  <example>The proof is theirs</example>
 49 |  <example correction=''>The proof is his</example>
 50 |  <example>The proof is theirs</example>
 51 | </rule>
 52 | <!-- Avoid all gendered pronouns:1 ends here -->
 53 | 
 54 | <!-- [[file:README.org::*"We have"]["We have":1]] -->
 55 | <!-- English rule, 2022-02-16 -->
 56 | <rule id="WE_HAVE" name="We have">
 57 |  <pattern>
 58 |   <token>we</token>
 59 |   <token postag='VBP|VBN|VB' postag_regexp='yes'>have</token>
 60 |   <token postag='VBN' postag_regexp='yes' negate_pos='yes'></token>
 61 |  </pattern>
 62 |  <message>Joey uses "we have" too much in his writing</message>
 63 |  <short>Don't say "we have"</short>
 64 |  <example correction=''><marker>We have a</marker> problem.</example>
 65 |  <example>There is a problem.</example>
 66 |  <example>We have seen it.</example>
 67 | </rule>
 68 | <!-- "We have":1 ends here -->
 69 | 
 70 | <!-- [[file:README.org::*Our Language][Our Language:1]] -->
 71 | <rule id="OUR_LANGUAGE" name="OUR_LANGUAGE">
 72 |   <pattern>
 73 |     <token>our</token>
 74 |     <token>language</token>
 75 |   </pattern>
 76 |   <message>
 77 |     Joey writes
 78 |     <suggestion>our language</suggestion>
 79 |     too much
 80 |   </message>
 81 |   <example correction=''>
 82 |     <marker>our language</marker>
 83 |   </example>
 84 |   <example>\lang</example>
 85 | </rule>
 86 | <!-- Our Language:1 ends here -->
 87 | 
 88 | <!-- [[file:README.org::*I don't do performance, so I never need to use "runtime"][I don't do performance, so I never need to use "runtime":1]] -->
 89 | <!-- English rule, 2022-02-02 -->
 90 | <rule id="RUNTIME" name="RUNTIME">
 91 |   <pattern>
 92 |     <token>runtime</token>
 93 |   </pattern>
 94 |   <message>Unless you are talking about how long a program takes to run, use "run-time" as an adjective or run time as a noun.</message>
 95 |   <example correction=''>
 96 |     <marker>runtime</marker>
 97 |   </example>
 98 |   <example>run-time or run time</example>
 99 | </rule>
100 | <!-- I don't do performance, so I never need to use "runtime":1 ends here -->
101 | 
102 | <!-- [[file:README.org::*Don't use "run time" as an adjective][Don't use "run time" as an adjective:1]] -->
103 | <!-- English rule, 2022-02-16, taken from the CAPRA guide -->
104 | <rule id="RUN_TIME_ADJECTIVE" name="Run time adjective">
105 |  <pattern>
106 |   <token>run</token>
107 |   <token>time</token>
108 |   <token postag='N.*' postag_regexp='yes'></token>
109 |  </pattern>
110 |  <message>Use run-time as as a description of a noun.</message>
111 |  <short>Use run-time for adjective</short>
112 |  <example correction=''>There was a <marker>run time error</marker>.</example>
113 |  <example>There was a run-time error.</example>
114 |  <example>There was an error at run time.</example>
115 | </rule>
116 | <!-- Don't use "run time" as an adjective:1 ends here -->
117 | 
118 | <!-- [[file:README.org::*Don't use "run-time" as a noun][Don't use "run-time" as a noun:1]] -->
119 | <!-- English rule, 2022-02-16, CAPRA style guide -->
120 | <rule id="RUNTIME_AS_NOUN" name="Run-time as noun">
121 |  <pattern>
122 |   <token chunk_re='E-NP.*'>run-time</token>
123 |  </pattern>
124 |  <message>Use "run time" for the noun form</message>
125 |  <short>Noun form is "run time"</short>
126 |  <example correction=''>There was an error at <marker>run-time</marker> in the program This will cause problems at run-time.</example>
127 |  <example>There was an error at run time in the program</example>
128 |  <example>There was a run-time error in the program</example>
129 |  <example>This is a problem during run-time checks</example>
130 |  <example correction=''>This will cause problems at run-time.</example>
131 |  <example>This will cause problems during run-time analysis.</example>
132 | </rule>
133 | <!-- Don't use "run-time" as a noun:1 ends here -->
134 | 
135 | <!-- [[file:README.org::*Don't use "run-time" as a noun][Don't use "run-time" as a noun:2]] -->
136 | <!-- English rule, 2022-02-16, taken from CAPRA guide -->
137 | <rule id="RUNTIME_SENTENCE_END" name="Run-time sentence end">
138 |  <pattern>
139 |   <token postag='SENT_END'>run-time</token>
140 |  </pattern>
141 |  <message>Use "run time" for the noun</message>
142 |  <short>Noun form is "run time"</short>
143 |  <example correction=''>There was an error at <marker>run-time</marker></example>
144 |  <example>There was an error at run time</example>
145 |  <example>There was a run-time error</example>
146 | </rule>
147 | <!-- Don't use "run-time" as a noun:2 ends here -->
148 | 
149 | <!-- [[file:README.org::*Type check vs typecheck vs type-check][Type check vs typecheck vs type-check:1]] -->
150 | <!-- English rule, 2022-02-02 -->
151 | <rule id="TYPECHECK" name="Typecheck">
152 |   <pattern>
153 |     <token regexp='yes'>type-?check(er|ers|ing|s|ed)?</token>
154 |   </pattern>
155 |   <message>Use "type check" for consistency</message>
156 |   <example correction=''>
157 |     <marker>typecheck</marker>
158 |     typechecking type-check type-checking type-checks type-checker typechecks typechecker
159 |   </example>
160 |   <example>type check</example>
161 |   <example correction=''>typechecking</example>
162 |   <example>type checking</example>
163 |   <example correction=''>type-check</example>
164 |   <example correction=''>type-checking</example>
165 |   <example correction=''>type-checks</example>
166 |   <example correction=''>type-checker</example>
167 |   <example correction=''>typechecks</example>
168 |   <example correction=''>typechecker</example>
169 | </rule>
170 | <!-- Type check vs typecheck vs type-check:1 ends here -->
171 | 
172 | <!-- [[file:README.org::*Cast-calculus vs cast calculus][Cast-calculus vs cast calculus:1]] -->
173 | <!-- English rule, 2022-02-02 -->
174 | <rule id="CASTCALCULUS" name="CASTCALCULUS">
175 |   <pattern>
176 |     <token>cast</token>
177 |     <token>calculus</token>
178 |   </pattern>
179 |   <message>"cast calculus" should have a hyphen</message>
180 |   <example correction=''>
181 |     <marker>cast calculus</marker>
182 |   </example>
183 |   <example>cast-calculus</example>
184 | </rule>
185 | <!-- Cast-calculus vs cast calculus:1 ends here -->
186 | 
187 | <!-- [[file:README.org::*"Tradeoff" vs "trade-off", choose one for consistency]["Tradeoff" vs "trade-off", choose one for consistency:1]] -->
188 | <!-- English rule, 2022-02-16 -->
189 | <rule id="TRADEOFF" name="tradeoff">
190 |  <pattern>
191 |   <token inflected='yes'>tradeoff</token>
192 |  </pattern>
193 |  <message>use "trade-off" for consistency</message>
194 |  <short>"trade-off"</short>
195 |  <example correction=''><marker>tradeoff</marker> tradeoffs</example>
196 |  <example>trade-off</example>
197 |  <example correction=''>tradeoffs</example>
198 |  <example>trade-offs</example>
199 | </rule>
200 | <!-- "Tradeoff" vs "trade-off", choose one for consistency:1 ends here -->
201 | 
202 | <!-- [[file:README.org::*Use "Judgment" instead of "Judgement"][Use "Judgment" instead of "Judgement":1]] -->
203 | <!-- English rule, 2022-02-16 -->
204 | <rule id="JUDGEMENT" name="judgement">
205 |  <pattern>
206 |   <token inflected='yes' regexp='yes'>judgement(al)?</token>
207 |  </pattern>
208 |  <message>For consistency, use "judgment"</message>
209 |  <short>"judgment"</short>
210 |  <example correction=''><marker>judgement</marker> judgements judgemental</example>
211 |  <example>judgment</example>
212 |  <example correction=''>judgements</example>
213 |  <example>judgments</example>
214 |  <example correction=''>judgemental</example>
215 |  <example>judgmental</example>
216 | </rule>
217 | <!-- Use "Judgment" instead of "Judgement":1 ends here -->
218 | 
219 | <!-- [[file:README.org::*Don't use a hyphen in either][Don't use a hyphen in either:1]] -->
220 | <!-- English rule, 2022-02-23 -->
221 | <rule id="DEPENDENT_TYPE" name="Dependent type">
222 |  <pattern>
223 |   <token regexp='yes'>dependent(ly)?-type[sd]?</token>
224 |  </pattern>
225 |  <message>No hyphen in  "dependent type"</message>
226 |  <short>No hyphen</short>
227 |  <example correction=''>The constructor builds a <marker>dependent-type</marker> The language supports dependent-types This is hard in dependently-typed programming languages</example>
228 |  <example>The constructor builds a dependent type</example>
229 |  <example correction=''>The language supports dependent-types</example>
230 |  <example>The language supports dependent types</example>
231 |  <example correction=''>This is hard in dependently-typed programming languages</example>
232 |  <example>This is hard in dependently typed programming languages</example>
233 | </rule>
234 | <!-- Don't use a hyphen in either:1 ends here -->
235 | 
236 | <!-- [[file:README.org::*Related: don't use "dependent language". Use "dependently-typed language".][Related: don't use "dependent language". Use "dependently-typed language".:1]] -->
237 | <!-- English rule, 2022-02-23 -->
238 | <rule id="DEPENDENT_LANGUAGE" name="Dependent language">
239 |  <pattern>
240 |   <token>dependent</token>
241 |   <token>language</token>
242 |  </pattern>
243 |  <message>Use the full "dependently typed"</message>
244 |  <short>"dependently typed language"</short>
245 |  <example correction=''>This is a <marker>dependent language</marker></example>
246 |  <example>This is a dependently typed language</example>
247 | </rule>
248 | <!-- Related: don't use "dependent language". Use "dependently-typed language".:1 ends here -->
249 | 
250 | <!-- [[file:README.org::*"This" as the subject of a sentence]["This" as the subject of a sentence:1]] -->
251 | <!-- English rule, 2022-02-16, from CAPRA -->
252 | <rule id="THIS_AS_SUBJECT" name="This as subject">
253 |  <pattern>
254 |   <token inflected='yes' regexp='yes' postag='DT'>this|these</token>
255 |   <token postag='VB.*' postag_regexp='yes' chunk_re='.*VP.*'></token>
256 |  </pattern>
257 |  <message>Be specific: don't use "this" as the subject of a sentence</message>
258 |  <short>Don't use this as the subject of a sentence</short>
259 |  <example correction=''><marker>This is</marker> problematic. These are problematic These are problematic</example>
260 |  <example>The problem is problematic.</example>
261 |  <example>This problem is problematic.</example>
262 |  <example correction=''>These are problematic</example>
263 |  <example>These problems are problematic</example>
264 |  <example>They are problematic</example>
265 |  <example>In this section we see the problem</example>
266 | </rule>
267 | <!-- "This" as the subject of a sentence:1 ends here -->
268 | 
269 | <!-- [[file:README.org::*"We can see that" can be omitted]["We can see that" can be omitted:1]] -->
270 | <!-- English rule, 2022-02-16 -->
271 | <rule id="WE_CAN_SEE_THAT" name="we can see that">
272 |  <pattern>
273 |   <token>we</token>
274 |   <token min='0'>can</token>
275 |   <token>see</token>
276 |   <token>that</token>
277 |  </pattern>
278 |  <message>"we can see that" adds nothing and eats your precious page budget</message>
279 |  <short>redundant</short>
280 |  <example correction=''><marker>we can see that</marker> this happens we see that this happens</example>
281 |  <example>this happens</example>
282 |  <example correction=''>we see that this happens</example>
283 | </rule>
284 | <!-- "We can see that" can be omitted:1 ends here -->
285 | 
286 | <!-- [[file:README.org::*Don't use "clearly" or "obviously"][Don't use "clearly" or "obviously":1]] -->
287 | <!-- English rule, 2022-02-16 -->
288 | <rule id="CLEARLY_OBVIOUSLY" name="clearly obviously">
289 |  <pattern>
290 |   <token regexp='yes'>clearly|obviously</token>
291 |  </pattern>
292 |  <message>Just eliminate these words, don't assume what is easy to the reader</message>
293 |  <short>redundant</short>
294 |  <example correction=''><marker>Clearly</marker> this is true Obviously this is true</example>
295 |  <example>this is true</example>
296 |  <example correction=''>Obviously this is true</example>
297 | </rule>
298 | <!-- Don't use "clearly" or "obviously":1 ends here -->
299 | 
300 | <!-- [[file:README.org::*Don't say something is "easy to see"][Don't say something is "easy to see":1]] -->
301 | <!-- English rule, 2022-02-16 -->
302 | <rule id="EASY_TO_SEE" name="easy to see">
303 |  <pattern>
304 |   <token>it</token>
305 |   <token>is</token>
306 |   <token>easy</token>
307 |   <token>to</token>
308 |   <token>see</token>
309 |  </pattern>
310 |  <message>Don<suggestion>t assume what</suggestion>s easy to the reader</message>
311 |  <short>redundant</short>
312 |  <example correction=''><marker>it is easy to see</marker> that this is true it is easy to see this is true</example>
313 |  <example>this is true</example>
314 |  <example correction=''>it is easy to see this is true</example>
315 |  <example>this is true</example>
316 | </rule>
317 | <!-- Don't say something is "easy to see":1 ends here -->
318 | 
319 | <!-- [[file:README.org::*Only use "simply" when referring to the STLC][Only use "simply" when referring to the STLC:1]] -->
320 | <!-- English rule, 2022-02-16 -->
321 | <rule id="SIMPLY" name="simply">
322 |  <pattern>
323 |   <token>simply</token>
324 |   <token negate='yes'>typed</token>
325 |  </pattern>
326 |  <message>You should only use simply to refer to the STLC</message>
327 |  <short>redundant</short>
328 |  <example correction=''>the result is <marker>simply three</marker></example>
329 |  <example>the result is three</example>
330 |  <example>this is the simply typed lambda calculus</example>
331 | </rule>
332 | <!-- Only use "simply" when referring to the STLC:1 ends here -->
333 | 
334 | <!-- [[file:README.org::*"Note that" can be omitted]["Note that" can be omitted:1]] -->
335 | <!-- English rule, 2022-02-16, CAPRA -->
336 | <rule id="NOTE_THAT" name="Note that">
337 |  <pattern>
338 |   <token regexp='yes'>note|notice</token>
339 |   <token>that</token>
340 |  </pattern>
341 |  <message>"Note that" or "notice that" adds nothing</message>
342 |  <short>Don't say "note that"</short>
343 |  <example correction=''><marker>note that</marker> this happens notice that this happens</example>
344 |  <example>this happens</example>
345 |  <example correction=''>notice that this happens</example>
346 | </rule>
347 | <!-- "Note that" can be omitted:1 ends here -->
348 | 
349 | <!-- [[file:README.org::*"See how" can be omitted]["See how" can be omitted:1]] -->
350 | <!-- English rule, 2022-02-16, CAPRA -->
351 | <rule id="SEE_HOW" name="see how">
352 |  <pattern>
353 |   <token>see</token>
354 |   <token>how</token>
355 |  </pattern>
356 |  <message>"see how" is redundant and adds nothing</message>
357 |  <short>Don't use "see how"</short>
358 |  <example correction=''><marker>see how</marker> it happens</example>
359 |  <example>it happens</example>
360 | </rule>
361 | <!-- "See how" can be omitted:1 ends here -->
362 | 
363 | <!-- [[file:README.org::*"It is worth noting that" can be omitted]["It is worth noting that" can be omitted:1]] -->
364 | <!-- English rule, 2022-02-16, CAPRA -->
365 | <rule id="IT_IS_WORTH_NOTING_THAT" name="it is worth noting that">
366 |  <pattern>
367 |   <token>it</token>
368 |   <token>is</token>
369 |   <token>worth</token>
370 |   <token>noting</token>
371 |   <token>that</token>
372 |  </pattern>
373 |  <message>"it is worth nothing that" takes up your valuable space budget and adds nothing</message>
374 |  <short>redundant</short>
375 |  <example correction=''><marker>it is worth noting that</marker> this happens</example>
376 |  <example>this happens</example>
377 | </rule>
378 | <!-- "It is worth noting that" can be omitted:1 ends here -->
379 | 
380 | <!-- [[file:README.org::*Long lists of written-out numbers][Long lists of written-out numbers:1]] -->
381 | <!-- English rule, 2022-02-16, taken from CAPRA guide -->
382 | <rule id="LONG_LIST_NUMBERS" name="Long List Numbers">
383 |  <pattern>
384 |   <token regexp='yes'>firstly|secondly|thirdly</token>
385 |   <token>,</token>
386 |  </pattern>
387 |  <message>Use (1) and (2) instead of firstly, secondly, etc.</message>
388 |  <short>Don's use firstly, secondly, thirdly</short>
389 |  <example correction=''>Firstly, this is the problem.</example>
390 |  <example>(1)</example>
391 |  <example correction=''>Secondly,</example>
392 |  <example>(2)</example>
393 |  <example correction=''>Thirdly,</example>
394 |  <example>(3)</example>
395 | </rule>
396 | <!-- Long lists of written-out numbers:1 ends here -->
397 | 
398 | <!-- [[file:README.org::*"Allows X to " should be "lets X"]["Allows X to " should be "lets X":1]] -->
399 | <!-- English rule, 2022-02-16 -->
400 | <rule id="ALLOWS_TO" name="Allows to">
401 |  <pattern>
402 |   <token inflected='yes'>allow</token>
403 |   <token chunk_re='B-NP.*'></token>
404 |   <token min='0' chunk_re='I-NP.*'></token>
405 |   <token min='0' chunk_re='E-NP.*'></token>
406 |   <token>to</token>
407 |  </pattern>
408 |  <message>Use "lets" instead</message>
409 |  <short>Use "lets"</short>
410 |  <example correction=''>This <marker>allows the program to</marker> run</example>
411 |  <example>This lets the program run</example>
412 |  <example correction=''>The check allows our gradual language to execute safely.</example>
413 |  <example>The check lets our gradual language execute safely.</example>
414 |  <example correction=''>The check allows it to run safely.</example>
415 |  <example>The check lets it run safely.</example>
416 |  <example correction=''>These allow the program to run</example>
417 |  <example>These let the program run</example>
418 |  <example correction=''>These check allow our gradual language to execute safely.</example>
419 |  <example>These checks let our gradual language execute safely.</example>
420 |  <example correction=''>The checks allows them to run safely.</example>
421 |  <example>The check let them run safely.</example>
422 |  <example correction=''>This allows all the programs to run</example>
423 |  <example>This lets all the programs run</example>
424 | </rule>
425 | <!-- "Allows X to " should be "lets X":1 ends here -->
426 | 
427 | <!-- [[file:README.org::*"Gives X the ability to" should be "Lets X"]["Gives X the ability to" should be "Lets X":1]] -->
428 | <!-- English rule, 2022-02-16 -->
429 | <rule id="GIVE_ABILITY_TO" name="Gives ability to">
430 |  <pattern>
431 |   <token inflected='yes'>give</token>
432 |   <token chunk_re='B-NP.*'></token>
433 |   <token min='0' chunk_re='I-NP.*'></token>
434 |   <token min='0' chunk_re='E-NP.*'></token>
435 | <token>the</token>
436 | <token>ability</token>
437 | <token>to</token>
438 |  </pattern>
439 |  <message>Use "lets" instead</message>
440 |  <short>Use "lets"</short>
441 |  <example correction=''>This gives the program the ability to run</example>
442 |  <example>This lets the program language run</example>
443 |  <example correction=''>The check gives our gradual language the ability to execute safely.</example>
444 |  <example>The check lets our gradual language execute safely.</example>
445 |  <example correction=''>The check gives it the ability to run safely.</example>
446 |  <example>The check lets it run safely.</example>
447 |  <!-- <example correction=''>These give all the programs the ability to run</example> -->
448 |  <!-- <example>These let all the programs run</example> -->
449 |  <example correction=''>These give them the ability to run</example>
450 |  <example>This lets them ruin</example>
451 |  <example correction=''>These give it the ability to run</example>
452 |  <example>These let it run</example>
453 | </rule>
454 | <!-- "Gives X the ability to" should be "Lets X":1 ends here -->
455 | 
456 | <!-- [[file:README.org::*"In order to" should be "to"]["In order to" should be "to":1]] -->
457 | <!-- English rule, 2022-02-16, CAPRA -->
458 | <rule id="IN_ORDER_TO" name="In order to">
459 |  <pattern>
460 |   <token>in</token>
461 |   <token>order</token>
462 |   <token>to</token>
463 |  </pattern>
464 |  <message>Use the simpler "to"</message>
465 |  <short>Use "to"</short>
466 |  <example correction=''><marker>in order to</marker></example>
467 |  <example>to</example>
468 | </rule>
469 | <!-- "In order to" should be "to":1 ends here -->
470 | 
471 | <!-- [[file:README.org::*"So as to" should be "to"]["So as to" should be "to":1]] -->
472 | <!-- English rule, 2022-02-16, CAPRA -->
473 | <rule id="SO_AS_TO" name="So as to">
474 |  <pattern>
475 |   <token>so</token>
476 |   <token>as</token>
477 |   <token>to</token>
478 |  </pattern>
479 |  <message>Use the simpler "to"</message>
480 |  <short>"to"</short>
481 |  <example correction=''><marker>so as to</marker></example>
482 |  <example>to</example>
483 | </rule>
484 | <!-- "So as to" should be "to":1 ends here -->
485 | 
486 | <!-- [[file:README.org::*"Is built on" should be "builds on"]["Is built on" should be "builds on":1]] -->
487 | <!-- English rule, 2022-02-16, CAPRA -->
488 | <rule id="IS_BUILT_ON" name="Is built on">
489 |  <pattern>
490 |   <token inflected='yes'>be</token>
491 |   <token>built</token>
492 |   <token>on</token>
493 |  </pattern>
494 |  <message>Use "builds on" instead of "is built on" when describing systems/languages</message>
495 |  <short>"builds on"</short>
496 |  <example correction=''><marker>is built on</marker> are built on was built on were built on</example>
497 |  <example>builds on</example>
498 |  <example correction=''>are built on</example>
499 |  <example>build on</example>
500 |  <example correction=''>was built on</example>
501 |  <example>built on</example>
502 |  <example correction=''>were built on</example>
503 |  <example>built on</example>
504 | </rule>
505 | <!-- "Is built on" should be "builds on":1 ends here -->
506 | 
507 | <!-- [[file:README.org::*"Has potential" can be "could"]["Has potential" can be "could":1]] -->
508 | <!-- English rule, 2022-02-16, CAPRA -->
509 | <rule id="HAS_POTENTIAL" name="has potential">
510 |  <pattern>
511 |   <token inflected='yes'>have</token>
512 |   <token>the</token>
513 |   <token>potential</token>
514 |   <token>to</token>
515 |  </pattern>
516 |  <message>Use the simpler "could"</message>
517 |  <short>"could"</short>
518 |  <example correction=''><marker>has the potential to</marker> have the potential to</example>
519 |  <example>could</example>
520 |  <example correction=''>have the potential to</example>
521 |  <example>could</example>
522 | </rule>
523 | <!-- "Has potential" can be "could":1 ends here -->
524 | 
525 | <!-- [[file:README.org::*"Sufficient amount" should be "enough"]["Sufficient amount" should be "enough":1]] -->
526 | <!-- English rule, 2022-02-16, CAPRA -->
527 | <rule id="SUFFICIENT_AMOUNT" name="sufficient amount">
528 |  <pattern>
529 |   <token>a</token>
530 |   <token>sufficient</token>
531 |   <token>amount</token>
532 |   <token>of</token>
533 |  </pattern>
534 |  <message>Use the simpler "enough"</message>
535 |  <short>"enough"</short>
536 |  <example correction=''><marker>a sufficient amount of</marker></example>
537 |  <example>enough</example>
538 | </rule>
539 | <!-- "Sufficient amount" should be "enough":1 ends here -->
540 | 
541 | <!-- [[file:README.org::*"Utilize" should be "use"]["Utilize" should be "use":1]] -->
542 | <!-- English rule, 2022-02-16, CAPRA -->
543 | <rule id="UTILIZE" name="utilize">
544 |  <pattern>
545 |   <token inflected='yes'>utilize</token>
546 |  </pattern>
547 |  <message>Use the simpler "use"</message>
548 |  <short>"use"</short>
549 |  <example correction=''><marker>utilize</marker> utilized utilizes</example>
550 |  <example>use</example>
551 |  <example correction=''>utilized</example>
552 |  <example>used</example>
553 |  <example correction=''>utilizes</example>
554 |  <example>uses</example>
555 | </rule>
556 | <!-- "Utilize" should be "use":1 ends here -->
557 | 
558 | <!-- [[file:README.org::*"Make use of" should be "Use"]["Make use of" should be "Use":1]] -->
559 | <!-- English rule, 2022-02-16, CAPRA -->
560 | <rule id="MAKE_USE_OF" name="make use of">
561 |  <pattern>
562 |   <token inflected='yes'>make</token>
563 |   <token>use</token>
564 |   <token>of</token>
565 |  </pattern>
566 |  <message>Use the simpler "use"</message>
567 |  <short>"use"</short>
568 |  <example correction=''><marker>make use of</marker> made use of makes use of making use of</example>
569 |  <example>use</example>
570 |  <example correction=''>made use of</example>
571 |  <example>used</example>
572 |  <example correction=''>makes use of</example>
573 |  <example>uses</example>
574 |  <example correction=''>making use of</example>
575 |  <example>using</example>
576 | </rule>
577 | <!-- "Make use of" should be "Use":1 ends here -->
578 | 
579 | <!-- [[file:README.org::*"Which means that"]["Which means that":1]] -->
580 | <!-- English rule, 2022-02-16, CAPRA-->
581 | <rule id="WHICH_MEANS_THAT" name="which means that">
582 |  <pattern>
583 |   <token>which</token>
584 |   <token>means</token>
585 |   <token>that</token>
586 |  </pattern>
587 |  <message>Use "so" instead</message>
588 |  <short>Use "so" instead</short>
589 |  <example correction='so'><marker>which means that</marker></example>
590 |  <example>so</example>
591 | </rule>
592 | <!-- "Which means that":1 ends here -->
593 | 
594 | <!-- [[file:README.org::*"Desiderata"]["Desiderata":1]] -->
595 | <!-- English rule, 2022-02-23 -->
596 | <rule id="DESIDERATA" name="Desiderata">
597 |  <pattern>
598 |   <token inflected='yes'>desideratum</token>
599 |  </pattern>
600 |  <message>Use "goals", "criteria" or something similar</message>
601 |  <short>Overused</short>
602 |  <example correction=''><marker>desideratum</marker> desiderata</example>
603 |  <example>goal</example>
604 |  <example correction=''>desiderata</example>
605 |  <example>goals</example>
606 | </rule>
607 | <!-- "Desiderata":1 ends here -->
608 | 
609 | <!-- [[file:README.org::*"There is/are"]["There is/are":1]] -->
610 | <!-- English rule, 2022-02-23 -->
611 | <rule id="THERE_IS_ARE" name="There is are">
612 |  <pattern>
613 |   <token>there</token>
614 |   <token regexp='yes'>is|are|were</token>
615 |  </pattern>
616 |  <message>Might be correct, but often it's stronger to use a more direct verb.</message>
617 |  <short>Use a direct verb?</short>
618 |  <example correction=''><marker>There is</marker> a cat There are some cats</example>
619 |  <example>A cat is sitting there</example>
620 |  <example correction=''>There are some cats</example>
621 |  <example>Some cats are sitting there</example>
622 | </rule>
623 | <!-- "There is/are":1 ends here -->
624 | 
625 | <!-- [[file:README.org::*Will][Will:1]] -->
626 | <!-- English rule, 2022-02-23 -->
627 | <rule id="WILL_FUTURE_TENSE" name="Will (future tense)">
628 |  <pattern>
629 |   <token postag='MD'>will</token>
630 |  </pattern>
631 |  <message>In academic writing, you very seldom want the future tense.</message>
632 |  <short>Use present tense</short>
633 |  <example correction=''>The term <marker>will</marker> reduce It will be a problem It will be a problem Will the term reduce?</example>
634 |  <example>The term reduces</example>
635 |  <example>I have a strong will.</example>
636 |  <example>I tried to will them to arrive.</example>
637 |  <example correction=''>It will be a problem</example>
638 |  <example>It is a problem</example>
639 |  <example correction=''>Will the term reduce?</example>
640 |  <example>Does the term reduce?</example>
641 | </rule>
642 | <!-- Will:1 ends here -->
643 | 


--------------------------------------------------------------------------------
/wordlist.txt:
--------------------------------------------------------------------------------
1 | GADT
2 | 


--------------------------------------------------------------------------------