Hacker News new | past | comments | ask | show | jobs | submit login

The wording "might" really triggers me because it stands for something that /could/ happen. It is one of the ways to express the conjunctive mood (possibilities, wishes, ambiguity), which has absolutely no right to exist in a technical documentation.

~~There is only one place where this makes sense: in a best-practices section explaining consequences. But also there I want to see clear facts instead of unclear statements making me chase ghosts.~~

Edit: No, just plain facts please.




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

Search: