Dmitry Vyukov 1efec8f5c7 dashboard/app: say "issue" instead of "crash" ... We've got several complains re using of word "crash" in all syzbot reports, e.g.: https://groups.google.com/d/msg/syzkaller-bugs/8rFLFgQR9fo/HBYUXIRyBAAJ https://groups.google.com/d/msg/syzkaller-bugs/3nlcT8Wn7hg/8Th16X3DBAAJ Another suggested that "crash" is too hard for e.g. a LOCKDEP splat: https://groups.google.com/d/msg/syzkaller/YzHLAU0dXpI/WOqq1ggBBQAJ Another terminology complaint was regarding the following fact. When we test a patch, we only detect if it still triggers _any_ issue (not necessary the original one). Currently we way "still triggers crash" (without any article, which is probably wrong from English perspective anyway). We did not say "the", but people assumed that and complained. Explicitly say "a". Also replace all uses of "bug" with "issue" for consistency. And use "final oops" instead of "final crash", which seems to be standard terminology at least for Linux: https://en.wikipedia.org/wiki/Linux_kernel_oops		2020-07-14 23:21:01 +02:00
..
app	dashboard/app: say "issue" instead of "crash"	2020-07-14 23:21:01 +02:00
config	dashboard/config: update config to next-20200710	2020-07-13 09:32:49 +02:00
dashapi	all: use more respective language	2020-06-11 23:19:34 +02:00