Why a cheat sheet’s shortcut differs from your app

01Check the cheat sheet’s source

Look for its platform, date, app version and scope. A Windows binding is not automatically a Mac binding, and a generated illustration is not a verified catalog.

Apple documents app-specific variation, while VS Code supports customized mappings. Determine whether the sheet describes defaults, a named keymap or someone’s personal setup. If that context is missing, treat the sheet as a clue to investigate rather than proof that your installation is broken.

02Compare one safe action

1. Choose a non-destructive command and find it in the app menu or shortcut editor. Compare both the action name and the keys, including any custom assignment.
2. Do not replace a working binding just to match a picture. If the app uses a different command name, verify its meaning before assuming it is equivalent. Keep the comparison narrow enough to explain what the sheet shows, what your installation shows and which configuration difference might account for it.

03Report a useful correction

Include the source URL, app version, operating system and keyboard layout where relevant. Distinguish what you read in documentation from what you observed on your machine.

Update your own note and retain a link to the current source. Avoid turning one corrected mismatch into a universal claim. Static references can still be useful when their scope is clear and their mappings can be checked against the software you actually use.