concept item property in category powershell

This is an excerpt from Manning's book PowerShell in Depth, Second Edition.
But Registry values are presented as item properties, so they don’t show up when you run Dir. Instead, you have to switch to using the item property commands, such as Get-ItemProperty, or its alias, gp. Here’s what you need to do:
PS HKCU:\software\microsoft\notepad> cd .. PS HKCU:\software\microsoft> gp notepad iWindowPosX : 246 iWindowPosY : 64 iWindowPosDX : 1199 iWindowPosDY : 630 fWrap : 0 StatusBar : 0 lfEscapement : 0 lfOrientation : 0 lfWeight : 400 lfItalic : 0 lfUnderline : 0 lfStrikeOut : 0 lfCharSet : 0 lfOutPrecision : 3 lfClipPrecision : 2 lfQuality : 1 lfPitchAndFamily : 49 lfFaceName : Consolas iPointSize : 160 szHeader : szTrailer : iMarginTop : 1000 iMarginBottom : 1000 iMarginLeft : 750 iMarginRight : 750 PSPath : Microsoft.PowerShell.Core\Registry::HKEY_CURRENT_USER \Software\Microsoft\notepad PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_CURRENT_USER \Software\Microsoft PSChildName : notepad PSDrive : HKCU PSProvider : Microsoft.PowerShell.Core\RegistryFirst, you change up a level in the hierarchy so that the shell is focused on HKCU: \Software\Microsoft. Then, you ask the shell to display the item properties of the Notepad key. Essentially, the Notepad key looks like a file, and the settings (or values) underneath it look like properties of the file.
When you consider this technique for modifying the Registry, commands like New-ItemProperty should start making sense to you. It doesn’t make sense to add new properties to an actual file on the filesystem; the filesystem recognizes only the properties that it was designed to work with. In the Registry, though, item properties are the way Registry values are presented, and it absolutely makes sense that you’re able to create new ones, as well as delete old ones, copy them, and so on.