Revert changes to ps101 (#11949)

Co-authored-by: Mike F. Robbins <mikefrobbins@users.noreply.github.com>

Author: mikefrobbins

reference/docs-conceptual/learn/ps101/02-help-system.md

@@ -391,7 +391,7 @@ first position (position zero) when used positionally.
     function help and script help articles.
 
     To get help for a script that isn't located in a path that's listed in
-    the `$Env:PATH` environment variable, type the script's path and file
+    the `$env:Path` environment variable, type the script's path and file
     name.
 
     If you enter the exact name of a help article, `Get-Help` displays the

reference/docs-conceptual/learn/ps101/04-pipelines.md

@@ -604,14 +604,14 @@ use the saved data as input for another command.
 
 ```powershell
 'Background Intelligent Transfer Service', 'Windows Time' |
-    Out-File -FilePath $Env:TEMP\services.txt
+    Out-File -FilePath $env:TEMP\services.txt
 ```
 
 You can use parentheses to pass the output of one command as input for a parameter to another
 command.
 
 ```powershell
-Stop-Service -DisplayName (Get-Content -Path $Env:TEMP\services.txt)
+Stop-Service -DisplayName (Get-Content -Path $env:TEMP\services.txt)
 ```
 
 This concept is like the order of operations in Algebra. Just as mathematical operations within

reference/docs-conceptual/learn/ps101/06-flow-control.md

@@ -314,13 +314,13 @@ In this chapter, you learned about the different types of loops that exist in Po
 ## References
 
 - [ForEach-Object][ForEach-Object]
-- [about_Foreach][about_Foreach]
-- [about_For][about_For]
-- [about_Do][about_Do]
-- [about_While][about_While]
-- [about_Break][about_Break]
-- [about_Continue][about_Continue]
-- [about_Return][about_Return]
+- [about_Foreach][about-foreach]
+- [about_For][about-for]
+- [about_Do][about-do]
+- [about_While][about-while]
+- [about_Break][about-break]
+- [about_Continue][about-continue]
+- [about_Return][about-return]
 
 <!-- link references -->
 

reference/docs-conceptual/learn/ps101/09-functions.md

@@ -12,7 +12,7 @@ PowerShell one-liners and scripts that have to be modified often are good candid
 reusable functions.
 
 Write functions whenever possible because they're more tool-oriented. You can add the functions to a
-script module, put that module in a location defined in the `$Env:PSModulePath`, and call the
+script module, put that module in a location defined in the `$env:PSModulePath`, and call the
 functions without needing to locate where you saved the functions. Using the **PowerShellGet**
 module, it's easy to share your PowerShell modules in a NuGet repository. **PowerShellGet** ships
 with PowerShell version 5.0 and higher. It's also available as a separate download for PowerShell
@@ -559,7 +559,7 @@ The problem is that default values can't be used with mandatory parameters. Inst
 `ValidateNotNullOrEmpty` parameter validation attribute with a default value.
 
 Even when setting a default value, try not to use static values. In the following example,
-`$Env:COMPUTERNAME` is used as the default value, which is automatically translated to the local
+`$env:COMPUTERNAME` is used as the default value, which is automatically translated to the local
 computer name if a value isn't provided.
 
 ```powershell
@@ -568,7 +568,7 @@ function Test-MrParameterValidation {
     [CmdletBinding()]
     param (
         [ValidateNotNullOrEmpty()]
-        [string[]]$ComputerName = $Env:COMPUTERNAME
+        [string[]]$ComputerName = $env:COMPUTERNAME
     )
 
     Write-Output $ComputerName
@@ -591,7 +591,7 @@ function Test-MrVerboseOutput {
     [CmdletBinding()]
     param (
         [ValidateNotNullOrEmpty()]
-        [string[]]$ComputerName = $Env:COMPUTERNAME
+        [string[]]$ComputerName = $env:COMPUTERNAME
     )
 
     foreach ($Computer in $ComputerName) {
@@ -611,7 +611,7 @@ function Test-MrVerboseOutput {
     [CmdletBinding()]
     param (
         [ValidateNotNullOrEmpty()]
-        [string[]]$ComputerName = $Env:COMPUTERNAME
+        [string[]]$ComputerName = $env:COMPUTERNAME
     )
 
     foreach ($Computer in $ComputerName) {

reference/docs-conceptual/learn/ps101/10-script-modules.md

@@ -201,7 +201,7 @@ function Get-MrPSVersion {
 }
 
 function Get-MrComputerName {
-    $Env:COMPUTERNAME
+    $env:COMPUTERNAME
 }
 ```
 
@@ -233,10 +233,10 @@ Import-Module C:\MyScriptModule.psm1
 
 The module autoloading feature was introduced in PowerShell version 3. To take advantage of module
 autoloading, a script module needs to be saved in a folder with the same base name as the `.psm1`
-file and in a location specified in `$Env:PSModulePath`.
+file and in a location specified in `$env:PSModulePath`.
 
 ```powershell
-$Env:PSModulePath
+$env:PSModulePath
 ```
 
 ```Output
@@ -249,7 +249,7 @@ The results are difficult to read. Since the paths are separated by a semicolon,
 results to return each path on a separate line. This makes them easier to read.
 
 ```powershell
-$Env:PSModulePath -split ';'
+$env:PSModulePath -split ';'
 ```
 
 ```Output
@@ -301,7 +301,7 @@ Script     0.0        myscriptmodule                      {Get-MrComputerName, G
 The module manifest can be created with all of the recommended information.
 
 ```powershell
-New-ModuleManifest -Path $Env:ProgramFiles\WindowsPowerShell\Modules\MyScriptModule\MyScriptModule.psd1 -RootModule MyScriptModule -Author 'Mike F Robbins' -Description 'MyScriptModule' -CompanyName 'mikefrobbins.com'
+New-ModuleManifest -Path $env:ProgramFiles\WindowsPowerShell\Modules\MyScriptModule\MyScriptModule.psd1 -RootModule MyScriptModule -Author 'Mike F Robbins' -Description 'MyScriptModule' -CompanyName 'mikefrobbins.com'
 ```
 
 If any of this information is missed during the initial creation of the module manifest, it can be
@@ -323,7 +323,7 @@ function Get-MrPSVersion {
 }
 
 function Get-MrComputerName {
-    $Env:COMPUTERNAME
+    $env:COMPUTERNAME
 }
 
 Export-ModuleMember -Function Get-MrPSVersion