diff --git a/.github/ISSUE_TEMPLATE/possible-bug.md b/.github/ISSUE_TEMPLATE/possible-bug.md
index 3d05f2244..c7e130e17 100644
--- a/.github/ISSUE_TEMPLATE/possible-bug.md
+++ b/.github/ISSUE_TEMPLATE/possible-bug.md
@@ -35,7 +35,7 @@ If you are using another package which depends on a version of `sharp` that is n
 ### Does this problem relate to file caching?
 
 The default behaviour of libvips is to cache input files, which can lead to `EBUSY` or `EPERM` errors on Windows.
-Use `[sharp.cache(false)](https://sharp.pixelplumbing.com/api-utility#cache)` to switch this feature off.
+Use [`sharp.cache(false)`](https://sharp.pixelplumbing.com/api-utility#cache) to switch this feature off.
 
 - [ ] Adding `sharp.cache(false)` does not fix this problem.
 
@@ -43,8 +43,8 @@ Use `[sharp.cache(false)](https://sharp.pixelplumbing.com/api-utility#cache)` to
 
 Images that contain EXIF Orientation metadata are not auto-oriented. By default, EXIF metadata is removed.
 
-- To auto-orient pixel values use the parameter-less `[rotate()](https://sharp.pixelplumbing.com/api-operation#rotate)` operation.
-- To retain EXIF Orientation use `[keepExif()](https://sharp.pixelplumbing.com/api-output#keepexif)`.
+- To auto-orient pixel values use the parameter-less [`rotate()`](https://sharp.pixelplumbing.com/api-operation#rotate) operation.
+- To retain EXIF Orientation use [`keepExif()`](https://sharp.pixelplumbing.com/api-output#keepexif).
 
 - [ ] Using `rotate()` or `keepExif()` does not fix this problem.