Merge pull request #10860 from MicrosoftDocs/main

2/5/2024 PM Publish

reference/5.1/Microsoft.PowerShell.Core/About/about_Environment_Variables.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to access and manage environment variables in PowerShell.
 Locale: en-US
-ms.date: 09/20/2023
+ms.date: 02/05/2024
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Environment Variables
@@ -29,10 +29,10 @@ operating system platforms. The PowerShell environment provider lets you get,
 add, change, clear, and delete environment variables in the current console.
 
 Environment variables, unlike other types of variables in PowerShell, are
-always stored as a string and can't be empty. Also unlike other variables,
-they're inherited by child processes, such as local background jobs and the
-sessions in which module members run. This makes environment variables well
-suited to storing values that are needed in both parent and child processes.
+always stored as strings. Also unlike other variables, they're inherited by
+child processes, such as local background jobs and the sessions in which module
+members run. This makes environment variables well suited to storing values
+that are needed in both parent and child processes.
 
 On Windows, environment variables can be defined in three scopes:
 
@@ -46,8 +46,8 @@ parent process and is constructed from the variables in the _Machine_ and
 _User_ scopes.
 
 When you change environment variables in PowerShell, the change affects only
-the current session. This behavior resembles the behavior of the `Set` command
-in the Windows Command Shell and the `Setenv` command in UNIX-based
+the current session. This behavior resembles the behavior of the `set` command
+in the Windows Command Shell and the `setenv` command in UNIX-based
 environments. To change values in the Machine or User scopes, you must use the
 methods of the **System.Environment** class.
 
@@ -113,8 +113,9 @@ The 'Foo' environment variable is set to: An example
 An example!
 ```
 
-Because an environment variable can't be an empty string, setting one to
-`$null` or an empty string removes it. For example:
+In PowerShell, an environment variable can't be set to an empty string. Setting
+an environment variable to `$null` or an empty string removes it from the
+current session. For example:
 
 ```powershell
 $Env:Foo = ''

reference/5.1/Microsoft.WSMan.Management/Test-WSMan.md

@@ -123,7 +123,7 @@ parameter are:
 > credentials are passed to it, the credentials can be used to control the network session.
 
 > [!IMPORTANT]
-> If you do not specify the **Authentication** parameter,, the `Test-WSMan` request is sent to the
+> If you do not specify the **Authentication** parameter, the `Test-WSMan` request is sent to the
 > remote computer anonymously, without using authentication. If the request is made anonymously, it
 > returns no information that is specific to the operating-system version. Instead, this cmdlet
 > displays null values for the operating system version and service pack level (OS: 0.0.0 SP: 0.0).

reference/7.2/Microsoft.PowerShell.Core/About/about_Environment_Variables.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to access and manage environment variables in PowerShell.
 Locale: en-US
-ms.date: 09/20/2023
+ms.date: 02/05/2024
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.2&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Environment Variables
@@ -37,10 +37,10 @@ add, change, clear, and delete environment variables in the current console.
 > environment variables on non-Windows platforms.
 
 Environment variables, unlike other types of variables in PowerShell, are
-always stored as a string and can't be empty. Also unlike other variables,
-they're inherited by child processes, such as local background jobs and the
-sessions in which module members run. This makes environment variables well
-suited to storing values that are needed in both parent and child processes.
+always stored as strings. Also unlike other variables, they're inherited by
+child processes, such as local background jobs and the sessions in which module
+members run. This makes environment variables well suited to storing values
+that are needed in both parent and child processes.
 
 On Windows, environment variables can be defined in three scopes:
 
@@ -54,8 +54,8 @@ parent process and is constructed from the variables in the _Machine_ and
 _User_ scopes.
 
 When you change environment variables in PowerShell, the change affects only
-the current session. This behavior resembles the behavior of the `Set` command
-in the Windows Command Shell and the `Setenv` command in UNIX-based
+the current session. This behavior resembles the behavior of the `set` command
+in the Windows Command Shell and the `setenv` command in UNIX-based
 environments. To change values in the Machine or User scopes, you must use the
 methods of the **System.Environment** class.
 
@@ -121,8 +121,9 @@ The 'Foo' environment variable is set to: An example
 An example!
 ```
 
-Because an environment variable can't be an empty string, setting one to
-`$null` or an empty string removes it. For example:
+In PowerShell, an environment variable can't be set to an empty string. Setting
+an environment variable to `$null` or an empty string removes it from the
+current session. For example:
 
 ```powershell
 $Env:Foo = ''

reference/7.2/Microsoft.WSMan.Management/Test-WSMan.md

@@ -125,7 +125,7 @@ parameter are:
 > credentials are passed to it, the credentials can be used to control the network session.
 
 > [!IMPORTANT]
-> If you do not specify the **Authentication** parameter,, the `Test-WSMan` request is sent to the
+> If you do not specify the **Authentication** parameter, the `Test-WSMan` request is sent to the
 > remote computer anonymously, without using authentication. If the request is made anonymously, it
 > returns no information that is specific to the operating-system version. Instead, this cmdlet
 > displays null values for the operating system version and service pack level (OS: 0.0.0 SP: 0.0).

reference/7.3/Microsoft.PowerShell.Core/About/about_Environment_Variables.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to access and manage environment variables in PowerShell.
 Locale: en-US
-ms.date: 09/20/2023
+ms.date: 02/05/2024
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.3&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Environment Variables
@@ -37,10 +37,10 @@ add, change, clear, and delete environment variables in the current console.
 > environment variables on non-Windows platforms.
 
 Environment variables, unlike other types of variables in PowerShell, are
-always stored as a string and can't be empty. Also unlike other variables,
-they're inherited by child processes, such as local background jobs and the
-sessions in which module members run. This makes environment variables well
-suited to storing values that are needed in both parent and child processes.
+always stored as strings. Also unlike other variables, they're inherited by
+child processes, such as local background jobs and the sessions in which module
+members run. This makes environment variables well suited to storing values
+that are needed in both parent and child processes.
 
 On Windows, environment variables can be defined in three scopes:
 
@@ -54,8 +54,8 @@ parent process and is constructed from the variables in the _Machine_ and
 _User_ scopes.
 
 When you change environment variables in PowerShell, the change affects only
-the current session. This behavior resembles the behavior of the `Set` command
-in the Windows Command Shell and the `Setenv` command in UNIX-based
+the current session. This behavior resembles the behavior of the `set` command
+in the Windows Command Shell and the `setenv` command in UNIX-based
 environments. To change values in the Machine or User scopes, you must use the
 methods of the **System.Environment** class.
 
@@ -121,8 +121,9 @@ The 'Foo' environment variable is set to: An example
 An example!
 ```
 
-Because an environment variable can't be an empty string, setting one to
-`$null` or an empty string removes it. For example:
+In PowerShell, an environment variable can't be set to an empty string. Setting
+an environment variable to `$null` or an empty string removes it from the
+current session. For example:
 
 ```powershell
 $Env:Foo = ''

reference/7.3/Microsoft.WSMan.Management/Test-WSMan.md

@@ -125,7 +125,7 @@ parameter are:
 > credentials are passed to it, the credentials can be used to control the network session.
 
 > [!IMPORTANT]
-> If you do not specify the **Authentication** parameter,, the `Test-WSMan` request is sent to the
+> If you do not specify the **Authentication** parameter, the `Test-WSMan` request is sent to the
 > remote computer anonymously, without using authentication. If the request is made anonymously, it
 > returns no information that is specific to the operating-system version. Instead, this cmdlet
 > displays null values for the operating system version and service pack level (OS: 0.0.0 SP: 0.0).

reference/7.4/Microsoft.PowerShell.Core/About/about_Environment_Variables.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to access and manage environment variables in PowerShell.
 Locale: en-US
-ms.date: 09/20/2023
+ms.date: 02/05/2024
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.4&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Environment Variables
@@ -37,10 +37,10 @@ add, change, clear, and delete environment variables in the current console.
 > environment variables on non-Windows platforms.
 
 Environment variables, unlike other types of variables in PowerShell, are
-always stored as a string and can't be empty. Also unlike other variables,
-they're inherited by child processes, such as local background jobs and the
-sessions in which module members run. This makes environment variables well
-suited to storing values that are needed in both parent and child processes.
+always stored as strings. Also unlike other variables, they're inherited by
+child processes, such as local background jobs and the sessions in which module
+members run. This makes environment variables well suited to storing values
+that are needed in both parent and child processes.
 
 On Windows, environment variables can be defined in three scopes:
 
@@ -54,8 +54,8 @@ parent process and is constructed from the variables in the _Machine_ and
 _User_ scopes.
 
 When you change environment variables in PowerShell, the change affects only
-the current session. This behavior resembles the behavior of the `Set` command
-in the Windows Command Shell and the `Setenv` command in UNIX-based
+the current session. This behavior resembles the behavior of the `set` command
+in the Windows Command Shell and the `setenv` command in UNIX-based
 environments. To change values in the Machine or User scopes, you must use the
 methods of the **System.Environment** class.
 
@@ -121,8 +121,9 @@ The 'Foo' environment variable is set to: An example
 An example!
 ```
 
-Because an environment variable can't be an empty string, setting one to
-`$null` or an empty string removes it. For example:
+In PowerShell, an environment variable can't be set to an empty string. Setting
+an environment variable to `$null` or an empty string removes it from the
+current session. For example:
 
 ```powershell
 $Env:Foo = ''

reference/7.4/Microsoft.WSMan.Management/Test-WSMan.md

@@ -125,7 +125,7 @@ parameter are:
 > credentials are passed to it, the credentials can be used to control the network session.
 
 > [!IMPORTANT]
-> If you do not specify the **Authentication** parameter,, the `Test-WSMan` request is sent to the
+> If you do not specify the **Authentication** parameter, the `Test-WSMan` request is sent to the
 > remote computer anonymously, without using authentication. If the request is made anonymously, it
 > returns no information that is specific to the operating-system version. Instead, this cmdlet
 > displays null values for the operating system version and service pack level (OS: 0.0.0 SP: 0.0).

reference/7.5/Microsoft.PowerShell.Core/About/about_Environment_Variables.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to access and manage environment variables in PowerShell.
 Locale: en-US
-ms.date: 09/20/2023
+ms.date: 02/05/2024
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.5&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about Environment Variables
@@ -37,10 +37,10 @@ add, change, clear, and delete environment variables in the current console.
 > environment variables on non-Windows platforms.
 
 Environment variables, unlike other types of variables in PowerShell, are
-always stored as a string and can't be empty. Also unlike other variables,
-they're inherited by child processes, such as local background jobs and the
-sessions in which module members run. This makes environment variables well
-suited to storing values that are needed in both parent and child processes.
+always stored as strings. Also unlike other variables, they're inherited by
+child processes, such as local background jobs and the sessions in which module
+members run. This makes environment variables well suited to storing values
+that are needed in both parent and child processes.
 
 On Windows, environment variables can be defined in three scopes:
 
@@ -54,8 +54,8 @@ parent process and is constructed from the variables in the _Machine_ and
 _User_ scopes.
 
 When you change environment variables in PowerShell, the change affects only
-the current session. This behavior resembles the behavior of the `Set` command
-in the Windows Command Shell and the `Setenv` command in UNIX-based
+the current session. This behavior resembles the behavior of the `set` command
+in the Windows Command Shell and the `setenv` command in UNIX-based
 environments. To change values in the Machine or User scopes, you must use the
 methods of the **System.Environment** class.
 
@@ -121,8 +121,9 @@ The 'Foo' environment variable is set to: An example
 An example!
 ```
 
-Because an environment variable can't be an empty string, setting one to
-`$null` or an empty string removes it. For example:
+In PowerShell, an environment variable can't be set to an empty string. Setting
+an environment variable to `$null` or an empty string removes it from the
+current session. For example:
 
 ```powershell
 $Env:Foo = ''

reference/7.5/Microsoft.WSMan.Management/Test-WSMan.md

@@ -125,7 +125,7 @@ parameter are:
 > credentials are passed to it, the credentials can be used to control the network session.
 
 > [!IMPORTANT]
-> If you do not specify the **Authentication** parameter,, the `Test-WSMan` request is sent to the
+> If you do not specify the **Authentication** parameter, the `Test-WSMan` request is sent to the
 > remote computer anonymously, without using authentication. If the request is made anonymously, it
 > returns no information that is specific to the operating-system version. Instead, this cmdlet
 > displays null values for the operating system version and service pack level (OS: 0.0.0 SP: 0.0).