Patch 1 update issues template screenshot

[not-fritos]

Why:

Closes:

#31792

List item 3 could use a clarifying screenshot to show where the "issues" live in the repo settings.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adding this screenshot to item 3 in the issues templates.

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9 3.8	fpt ghec ghes@ 3.12 3.11 3.10 3.9 3.8

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[nguyenalex836]

@totally-not-frito-lays Thanks for opening a PR! I'll get this triaged for review ✨

[janbrasna]

@totally-not-frito-lays FYI there's a specific style for hiliting UI elements: https://docs.github.com/en/contributing/writing-for-github-docs/creating-screenshots#highlighting-elements-in-screenshots to follow for consistency, including the theme for Snagit tool and color definition from Primer design system — that need to be applied here, my guess is the color is not a match etc. …

[not-fritos]

@totally-not-frito-lays FYI there's a specific style for hiliting UI elements: https://docs.github.com/en/contributing/writing-for-github-docs/creating-screenshots#highlighting-elements-in-screenshots to follow for consistency, including the theme for Snagit tool and color definition from Primer design system — that need to be applied here, my guess is the color is not a match etc. …

Oh shoot, I should've known that there was a style for screenshots XD. Thanks for bringing that to my attention. I'll make an update next time I'm at my computer.

[not-fritos]

Dang, I went to review the primer docs on screenshots. Uses a closed-source screenshot tool. I was hoping this was gonna be a quick fix. This PR is kinda moot. I'll close it for now but leave the issue open.