Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update keyboard shortcuts to meet the new GitHub content style guide #13891

Closed
1 task done
ramyaparimi opened this issue Jan 10, 2022 · 0 comments · Fixed by #13913
Closed
1 task done

Update keyboard shortcuts to meet the new GitHub content style guide #13891

ramyaparimi opened this issue Jan 10, 2022 · 0 comments · Fixed by #13913
Labels
Campus Experts + Docs program Issues for the Campus Experts + Docs program content This issue or pull request belongs to the Docs Content team

Comments

@ramyaparimi
Copy link
Contributor

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests

What part(s) of the article would you like to see updated?

Keyboard shortcuts in this document are outdated. Refer to Keyboard Shortcuts section in the content style guide on how to correctly present keyboard shortcuts in GitHub docs.

Additional information

commandk should be Command+K
commandshift7 should be Command+Shift+7

@ramyaparimi ramyaparimi added content This issue or pull request belongs to the Docs Content team Campus Experts + Docs program Issues for the Campus Experts + Docs program labels Jan 10, 2022
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jan 10, 2022
@ramyaparimi ramyaparimi removed the triage Do not begin working on this issue until triaged by the team label Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Campus Experts + Docs program Issues for the Campus Experts + Docs program content This issue or pull request belongs to the Docs Content team
Development

Successfully merging a pull request may close this issue.

1 participant