Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sure, here are two, but I have hundreds. The second one triggers quite often for me.

The art is trying to writing a rule without too much false positives. False positives are myriad. Probably 60% of warnings are false positives, so you don't want to add too much more to that. On a typical document, I can get ten pages of errors, fortunately, going through it goes quite fast.

<rule id="" name=""> <pattern> <token>comprise</token> <token>be</token> </pattern> <message>comprise be</message> <example correction=''>The thingy may <marker>comprise be</marker> configured to do things.</example> <example >The thingy may be configured to do things.</example> </rule>

<rule id="" name=""> <pattern> <token regexp='yes'>arranged|configured</token> <token>to</token> <token postag='VBG'></token> </pattern> <message>You followed <suggestion>arranged to</suggestion> or <suggestion>configured to </suggestion> with a gerund.</message> <example correction=''>The thing is <marker>arranged to replacing</marker> the other thing.</example> <example>The thing is arranged to replace the other thing.</example> </rule>



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: