Update bug_report.md

Okay this should be it

.github/ISSUE_TEMPLATE/bug_report.md

@@ -20,7 +20,7 @@ Carefully read and work through this check list in order to prevent the most com
 - [ ] I've searched the issues (closed or open) for similar bug reports, not just here on Tubeup, but [yt-dlps issue tracker](https://github.com/yt-dlp/yt-dlp/issues) for download issues similar to mine and [internetarchives issue tracker](https://github.com/jjjake/internetarchive/issues) for upload issues similar to mine. YT-DLP has an issue up [listing known bugs](https://github.com/yt-dlp/yt-dlp/issues/3766).
 - [ ] I'm not submitting a bug report about IA S3 timeouts (we have no control over Internet Archive outages or per-user throttling, and sometimes the site has maintence like hard disk swaps)
 - [ ] I've checked the [X account for Internet Archive](https://x.com/internetarchive) for any announced outages or planned infrastructure maintenance that would affect performance of uploads.
-- [ ] I have properly indented [with triple backticks - the key directly below Escape on a QWERTY keyboar - before and after the console output]([https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code)) full terminal terminal output from the line where the command was run to where I was returned to command prompt, and am not trying to obscure item identifiers or URLs used in the creation of the bug (we need this to recreate the bug or investigate what happened).
+- [ ] I have properly indented [with triple backticks - the key directly below Escape on a QWERTY keyboard - before and after the console output](https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code) full terminal terminal output from the line where the command was run to where I was returned to command prompt, and am not trying to obscure item identifiers or URLs used in the creation of the bug (we need this to recreate the bug or investigate what happened).
 
 **Dependency versions**