t

Akemi · Apr 20, 2024 · fe34860 · fe34860
1 parent 989f816
commit fe34860
Showing 1 changed file with 10 additions and 10 deletions.
diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_macos.yml b/.github/ISSUE_TEMPLATE/2_bug_report_macos.yml
@@ -16,19 +16,19 @@ body:
           Releases are listed [here](https://github.com/mpv-player/mpv/releases).
       value: >
           - mpv version:
-           - macOS version:
-           - source:
-           - introduced in version:
+          - macOS version:
+          - source:
+          - introduced in version:
 - type: textarea
   attributes:
       label: "Reproduction steps"
       description: >
-          Try to reproduce your issue with --no-config first. If it isn't reproducible
-          with --no-config try to first find out which option or script causes your issue.
+          Try to reproduce your issue with `--no-config` first. If it isn't reproducible
+          with `--no-config` try to first find out which option or script causes your issue.
 
-          If the issue is performance-related, try to reproduce it with --no-config
-          --profile=fast, which is designed to work on lower-end mobile devices.
-          Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
+          If the issue is performance-related, try to reproduce it with `--no-config`
+          `--profile=fast`, which is designed to work on lower-end mobile devices.
+          Additionally, enable hardware decoding with `--hwdec=yes` or the `Ctrl+h` shortcut.
 
           Describe the reproduction steps as precise as possible. It's very likely that
           the bug you experience wasn't reproduced by the developer because the workflow
@@ -49,11 +49,11 @@ body:
   attributes:
       label: "Log file"
       description: >
-          Make a log file made with -v -v or --log-file=output.txt, attach it to
+          Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to
           the issue, and replace this text with a link to it.
 
           If you use the Bundle, a default log is created for your last run at
-          ~/Library/Logs/mpv.log. You can jump to that file via the
+          `~/Library/Logs/mpv.log`. You can jump to that file via the
           Help > Show log File… menu.
 
           Without the log file, this issue will be closed for ignoring the issue template.