diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 252681ab..5fbd35bc 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -26,12 +26,12 @@ A short description of what the issue is, and possibly some steps to reproduce i
 **Debug log**
 Please also include a debug log if possible. If you are reporting an issue with yabridgectl, then you can omit this section.
 
-1. First make sure that there are no left over Wine processes left running in
-   the background using `wineserver -k`.
+1. First make sure that there are no leftover Wine processes left running in the
+   background using `wineserver -k`.
 2. Launch your host from a terminal using
    `env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2 <host>`,
    e.g. `env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2 bitwig-studio`.
-3. Try to scan or load the plugin that has issues.
+3. Try to scan or load the plugin that's causing issues.
 4. `/tmp/yabridge.log` should now contain a debug log. You can either attach
    this log directly to the issue by dragging the file onto this text box, or
-   you could upload the contents to a website like GitHub gists or Hastebin.
+   you could upload the contents to a website like GitHub's Gists or Hastebin.
diff --git a/.github/ISSUE_TEMPLATE/setup_help.md b/.github/ISSUE_TEMPLATE/setup_help.md
index 494afa3d..d0e9946d 100644
--- a/.github/ISSUE_TEMPLATE/setup_help.md
+++ b/.github/ISSUE_TEMPLATE/setup_help.md
@@ -20,12 +20,12 @@ A short description of the current situation.
 **Debug log**
 Please also include a debug log if possible. If you are having issues with yabridgectl, then you can omit this section.
 
-1. First make sure that there are no left over Wine processes left running in
-   the background using `wineserver -k`.
+1. First make sure that there are no leftover Wine processes left running in the
+   background using `wineserver -k`.
 2. Launch your host from a terminal using
    `env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2 <host>`,
    e.g. `env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=2 bitwig-studio`.
-3. Try to scan or load the plugin that has issues.
+3. Try to scan or load the plugin that's causing issues.
 4. `/tmp/yabridge.log` should now contain a debug log. You can either attach
    this log directly to the issue by dragging the file onto this text box, or
-   you could upload the contents to a website like GitHub gists or Hastebin.
+   you could upload the contents to a website like GitHub's Gists or Hastebin.