As I mentioned in PR #8704 (**Format of resolution for "The TPM is locked out."**), "ps" does not identify as a syntax highlighting code keyword for PowerShell. The keywords "powershell" or "PowerShell" should be used in the current implementation of GitHub Flavored MarkDown (GFM). The syntax highlighting added in PR PR #8704, "ps" translates to PostScript via one of its filename extensions (.ps, .eps, .epsi, .pfa), whereas PowerShell can only be identified via its filename extensions .ps1, .psd1, .psm1 when not using its dedicated keyword PowerShell/powershell. Secondary IDs like filename extensions are discouraged as long as known keywords exist and are valid.
The Linguist project here on GitHub (https://github.com/github/linguist) for a complete list of syntax highlighting keywords:
- https://github.com/github/linguist/blob/master/lib/linguist/languages.yml
("Defines all Languages known to GitHub.")
Proposed changes:
- correct the MarkDown code block syntax highlighting keyword "ps" to "powershell"
Whitespace changes:
- remove redundant end-of-line blanks
- reduce the spacing between metadata and page title from 2 to 1 blank line
- add missing NewLine at end-of-file (last line)
Ticket closure or reference:
ref. #8704
The resolution for the "The TPM is locked out." issue was missing newline characters in the PowerShell commands. This change adds newline characters between the commands so that the command is easier to run.
