[PowerShell] Update Powershell article

Author: markingmyname

docs/powershell/sql-server-powershell.md

@@ -4,10 +4,11 @@ description: Learn about the two SQL Server PowerShell modules, SqlServer and SQ
 author: markingmyname
 ms.author: maghan
 ms.reviewer: matteot
-ms.date: 06/11/2020
+ms.date: 08/07/2023
 ms.service: sql
 ms.subservice: sql-server-powershell
 ms.topic: conceptual
+ms.custom: UpdatedFrequency5
 ---
 
 # SQL Server PowerShell
@@ -32,7 +33,7 @@ You can also use [PowerShell with Azure Data Studio](../azure-data-studio/extens
 
 **Why did the module change from SQLPS to SqlServer?**
 
-To ship SQL PowerShell updates, we had to change the identity of the SQL PowerShell module, and the wrapper known as *SQLPS.exe*. Because of this change, there are now two SQL PowerShell modules, the **SqlServer** module, and the **SQLPS** module.  
+To ship SQL PowerShell updates, we had to change the identity of the SQL PowerShell module, and the wrapper known as *SQLPS.exe*. Because of this change, there are now two SQL PowerShell modules, the **SqlServer** module, and the **SQLPS** module.
 
 **Update your PowerShell scripts if you import the SQLPS module.**
 
@@ -48,7 +49,7 @@ The **SqlServer** module comes with:
 
 - [PowerShell Providers](/powershell/module/microsoft.powershell.core/about/about_providers), which enables a simple navigation mechanism similar to file system paths. You can build paths similar to file system paths, where the drive is associated with a SQL Server management object model, and the nodes are based on the object model classes. You can then use familiar commands such as **cd** (alias for Set-Location) and **dir** (alias for Get-ChildItem) to navigate the paths similar to the way you navigate folders in a command prompt window. You can use other commands, such as **ren** (alias for Rename-Item) or **del** (alias for Remove-Item), to perform actions on the nodes in the path.
 
-- A set of cmdlets that support actions such as running a **sqlcmd** script containing Transact-SQL or XQuery statements.  
+- A set of cmdlets that support actions such as running a **sqlcmd** script containing Transact-SQL or XQuery statements.
 
 - The AS provider and cmdlets, which before they were installed separately.
 
@@ -61,19 +62,20 @@ SQL PowerShell cmdlets can be used to manage instances of Azure SQL Database, Az
 The **Encode-Sqlname** (alias for ConvertTo-EncodedSqlName) and **Decode-Sqlname** (alias for ConvertFrom-EncodedSqlName) cmdlets help you specify SQL Server identifiers that contain characters not supported in PowerShell paths. For more information, see [SQL Server Identifiers in PowerShell](sql-server-identifiers-in-powershell.md).
 
 Use the **Convert-UrnToPath** cmdlet to convert a Unique Resource Name for a Database Engine object to a path for the SQL Server PowerShell provider. For more information, see [Convert URNs to SQL Server Provider Paths](/powershell/module/sqlserver/Convert-UrnToPath).
-  
-## Query Expressions and Uniform Resource Names  
+
+## Query Expressions and Uniform Resource Names
 
 Query expressions are strings that use syntax similar to XPath to specify a set of criteria that enumerates one or more objects in an object model hierarchy. A Uniform Resource Name (URN) is a specific type of query expression string that uniquely identifies a single object. For more information, see [Query Expressions and Uniform Resource Names](query-expressions-and-uniform-resource-names.md).
 
 ## SQL Server Agent
 
 There's no change to the module used by SQL Server Agent. As such, SQL Server Agent jobs, which have PowerShell type job steps use the SQLPS module. For more information, see [How to run PowerShell with SQL Server Agent](run-windows-powershell-steps-in-sql-server-agent.md). However, starting with SQL Server 2019, you can disable SQLPS. To do so, on the first line of a job step of the type PowerShell you can add `#NOSQLPS`, which stops the SQL Agent from auto-loading the SQLPS module. When you do this, your SQL Agent Job runs the version of PowerShell installed on the machine, and then you can use any other PowerShell module you like.
 
-### Troubleshooting SQLPS
-If you see agent job steps (PowerShell subsystem) failing with the following error, this section may be helpful in troubleshooting the issue. 
+### Troubleshoot SQLPS
+
+If you see agent job steps (PowerShell subsystem) failing with the following error, this section may be helpful in troubleshooting the issue.
 
-> A job step received an error at line 1 in a PowerShell script. The corresponding line is 'import-module SQLPS'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'The specified module 'SQLPS' was not loaded because no valid module file was found in any module directory.  
+> A job step received an error at line 1 in a PowerShell script. The corresponding line is 'import-module SQLPS'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'The specified module 'SQLPS' was not loaded because no valid module file was found in any module directory.
 
 The SQLPS module must be available at the environment variable PSModulePath.  Uninstalling SSMS 16.x may remove the SQLPS from PSModulePath.  To check the current values stored in PSModulePath, run the following PowerShell:
 
@@ -92,8 +94,6 @@ If you want to use the **SqlServer** module in your SQL Agent Job step, you can
 Import-Module -Name SqlServer
 ```
 
-
-
 ## Cmdlet reference
 
 - [SqlServer cmdlets](/powershell/module/sqlserver)