dashboard: do not mention bug in the email template

Not all reports are real bugs, so let's use softer wording.

4 files changed, 30 insertions, 30 deletions

diff --git a/dashboard/app/asset_storage_test.go b/dashboard/app/asset_storage_test.go
index 80d71105d..803642675 100644
--- a/dashboard/app/asset_storage_test.go
+++ b/dashboard/app/asset_storage_test.go
@@ -101,14 +101,14 @@ syzbot engineers can be reached at syzkaller@googlegroups.com.
 syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
@@ -393,14 +393,14 @@ syzbot engineers can be reached at syzkaller@googlegroups.com.
 syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
diff --git a/dashboard/app/bisect_test.go b/dashboard/app/bisect_test.go
index 5e10d5a7d..a88d20956 100644
--- a/dashboard/app/bisect_test.go
+++ b/dashboard/app/bisect_test.go
@@ -237,18 +237,18 @@ syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 For information about bisection process see: https://goo.gl/tpsmEJ#bisection
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
 If you want syzbot to run the reproducer, reply with:
 #syz test: git://repo/address.git branch-or-commit-hash
 If you attach or paste a git patch, syzbot will apply it before testing.
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
@@ -556,18 +556,18 @@ syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 For information about bisection process see: https://goo.gl/tpsmEJ#bisection
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
 If you want syzbot to run the reproducer, reply with:
 #syz test: git://repo/address.git branch-or-commit-hash
 If you attach or paste a git patch, syzbot will apply it before testing.
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
@@ -840,18 +840,18 @@ syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 For information about bisection process see: https://goo.gl/tpsmEJ#bisection
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
 If you want syzbot to run the reproducer, reply with:
 #syz test: git://repo/address.git branch-or-commit-hash
 If you attach or paste a git patch, syzbot will apply it before testing.
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
diff --git a/dashboard/app/email_test.go b/dashboard/app/email_test.go
index d005bd229..50da765eb 100644
--- a/dashboard/app/email_test.go
+++ b/dashboard/app/email_test.go
@@ -74,14 +74,14 @@ syzbot engineers can be reached at syzkaller@googlegroups.com.
 syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
@@ -253,18 +253,18 @@ syzbot engineers can be reached at syzkaller@googlegroups.com.
 syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
 If you want syzbot to run the reproducer, reply with:
 #syz test: git://repo/address.git branch-or-commit-hash
 If you attach or paste a git patch, syzbot will apply it before testing.
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
@@ -702,14 +702,14 @@ syzbot engineers can be reached at syzkaller@googlegroups.com.
 syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
@@ -872,14 +872,14 @@ syzbot engineers can be reached at syzkaller@googlegroups.com.
 syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with:
diff --git a/dashboard/app/mail_bug.txt b/dashboard/app/mail_bug.txt
index d4d83316f..1d32238ff 100644
--- a/dashboard/app/mail_bug.txt
+++ b/dashboard/app/mail_bug.txt
@@ -56,7 +56,7 @@ syzbot will keep track of this issue. See:
 https://goo.gl/tpsmEJ#status for how to communicate with syzbot.{{if .BisectCause}}
 For information about bisection process see: https://goo.gl/tpsmEJ#bisection{{end}}
 
-If the bug is already fixed, let syzbot know by replying with:
+If the report is already addressed, let syzbot know by replying with:
 #syz fix: exact-commit-title
 
 {{- if or .ReproCLink .ReproSyzLink}}
@@ -66,11 +66,11 @@ If you want syzbot to run the reproducer, reply with:
 If you attach or paste a git patch, syzbot will apply it before testing.
 {{- end}}
 
-If you want to overwrite bug's subsystems, reply with:
+If you want to overwrite report's subsystems, reply with:
 #syz set subsystems: new-subsystem
 (See the list of subsystem names on the web dashboard)
 
-If the bug is a duplicate of another bug, reply with:
+If the report is a duplicate of another one, reply with:
 #syz dup: exact-subject-of-another-report
 
 If you want to undo deduplication, reply with: