Also, although someone has identified one exception (and I can't remember right now what that was), virtually every command prompt command is aliased in PowerShell.
As far as following step-by-step instructions that ask you to do something in Command Prompt the odds are very, very good that you can do exactly what's asked in PowerShell instead.
The converse, however, is not true if the step-by-step instructions are using native PowerShell syntax. PowerShell came after Command Prompt and, as is noted by jenae, there exist millions of .bat files that contain scripts written in Command Prompt syntax. Microsoft knew that most of these would probably be simply converted to PowerShell by changing their extensions to .ps1 (PowerShell Script) and wanted them to be "runnable as is."
I need to try this with a couple of my .bat files that I still use. I know that I still issue quite a few Command Prompt commands in PowerShell, using their old syntax, and they work just fine.
Brian AKA Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134
. . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it. The willing suspension of disbelief has its limits, or should.
~ Ruth Marcus, November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story