Added links to cmdlets and updated links

Author: markingmyname

docs/powershell/download-sql-server-ps-module.md

@@ -158,7 +158,13 @@ Visit [Manage SQL Server on Linux with PowerShell Core](../linux/sql-server-linu
 
 - [SqlServerDsc](https://www.powershellgallery.com/packages/SqlServerDsc/) - Module with DSC resources for deployment and configuration of Microsoft SQL Server.
 
+## Cmdlet reference
+
+- [SqlServer cmdlets](https://docs.microsoft.com/powershell/module/sqlserver)
+- [SQLPS cmdlets](https://docs.microsoft.com/powershell/module/sqlps)
+
 ## Next steps
 
 - [SQL Server PowerShell](sql-server-powershell.md)
+- [SQL Server PowerShell cmdlets](https://docs.microsoft.com/powershell/module/sqlserver)
 - [Use PowerShell with Azure Data Studio](../azure-data-studio/extensions/powershell-extension.md)

docs/powershell/encode-and-decode-sql-server-identifiers.md

@@ -38,13 +38,14 @@ The **Encode-Sqlname** and **Decode-Sqlname** cmdlets only encode or decode the
 
 ## Encoding an Identifier  
 
-**To encode a SQL Server identifier in a PowerShell path**
+### To encode a SQL Server identifier in a PowerShell path
 
 - Use one of two methods to encode a SQL Server identifier:
     - Specify the hexadecimal code for the unsupported character using the syntax %XX, where XX is the hexadecimal code.
     - Pass the identifier as a quoted string to the **Encode-Sqlname** cmdlet
 
 ### Examples (Encoding)
+
 This example specifies the encoded version of the ":" character (%3A):
 
 ```powershell
@@ -57,9 +58,9 @@ Alternatively, you can use **Encode-SqlName** to build a name supported by Windo
 Set-Location (Encode-SqlName "Table:Test")
 ```
 
-##  <a name="DecodeIdent"></a> Decoding an Identifier
+## Decoding an Identifier
 
-**To decode a SQL Server identifier from a PowerShell path**
+### To decode a SQL Server identifier from a PowerShell path
 
 Use the **Decode-Sqlname** cmdlet to replace the hexadecimal encodings with the characters represented by the encoding.
 

docs/powershell/escape-sql-server-identifiers.md

@@ -1,5 +1,5 @@
 ---
-title: "Escape SQL Server Identifiers | Microsoft Docs"
+title: Escape SQL Server Identifiers
 description: Some characters that can appear in SQL Server-delimited identifiers aren't supported in Windows PowerShell paths. Learn how some of these can be escaped with the back-tick character.
 ms.prod: sql
 ms.technology: sql-server-powershell

docs/powershell/load-the-smo-assemblies-in-windows-powershell.md

@@ -1,6 +1,6 @@
 ---
 title: Load the SMO Assemblies in Windows PowerShell
-description: Learn how to load the SQL Server Management Object (SMO) assemblies in Windows PowerShell scripts that do not use the SQL Server PowerShell provider.
+description: Learn how to load the SQL Server Management Object (SMO) assemblies in Windows PowerShell scripts that don't use the SQL Server PowerShell provider.
 ms.prod: sql
 ms.technology: sql-server-powershell
 ms.topic: conceptual
@@ -16,7 +16,7 @@ ms.date: 10/14/2020
 
 [!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW ](../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
-This article describes how to load the SQL Server Management Object (SMO) assemblies in Windows PowerShell scripts that do not use the SQL Server PowerShell provider.  
+This article describes how to load the SQL Server Management Object (SMO) assemblies in Windows PowerShell scripts that don't use the SQL Server PowerShell provider.  
 
 > [!NOTE]
 > There are two SQL Server PowerShell modules; **SqlServer** and **SQLPS**. The **SQLPS** module is included with the SQL Server installation (for backwards compatibility), but is no longer being updated. The most up-to-date PowerShell module is the **SqlServer** module. The **SqlServer** module contains updated versions of the cmdlets in **SQLPS**, and also includes new cmdlets to support the latest SQL features.  
@@ -29,7 +29,7 @@ There are two cases where you may need to load the SMO assemblies directly:
 
 - If your script references a SMO object before the first command that references the provider or cmdlets from the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] snap-ins.  
 
-- You want to port SMO code from another language, such as C# or Visual Basic, which does not use the provider or cmdlets.  
+- You want to port SMO code from another language, such as C# or Visual Basic, which doesn't use the provider or cmdlets.  
 
 ## Example: Loading the SQL Server Management Objects
 
@@ -38,7 +38,7 @@ The following code loads the SMO assemblies:
 ```powershell
 # Loads the SQL Server Management Objects (SMO)  
 
-$ErrorActionPreference = "Stop"  
+$ErrorActionPreference = "Stop"
   
 $sqlpsreg="HKLM:\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps"  
   

docs/powershell/manage-authentication-in-database-engine-powershell.md

@@ -1,19 +1,19 @@
 ---
-title: "PowerShell: Manage authentication"
+title: Manage authentication to SQL Server in PowerShell
 description: Learn how to use SQL Server Authentication rather than Windows Authentication (the default) when connecting to an instance of the Database Engine.
 titleSuffix: SQL Server on Linux
-ms.custom: seo-lt-2019
-ms.date: "03/14/2017"
 ms.prod: sql
-ms.reviewer: matteot, drskwier
 ms.technology: sql-server-powershell
 ms.topic: conceptual
 ms.assetid: ab9212a6-6628-4f08-a38c-d3156e05ddea
 author: markingmyname
 ms.author: maghan
+ms.reviewer: matteot, drskwier
+ms.custom: seo-lt-2019
+ms.date: 10/14/2020
 ---
 
-# PowerShell: Manage authentication to SQL Server
+# Manage authentication to SQL Server in PowerShell
 
 [!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW ](../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
@@ -27,26 +27,26 @@ By default, the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] PowerShel
 ## Permissions
 
 All actions you can perform in an instance of the [!INCLUDE[ssDE](../includes/ssde-md.md)] are controlled by the permissions granted to the authentication credentials used to connect to the instance. By default, the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] provider and cmdlets use the Windows account under which it is running to make a Windows Authentication connection to the [!INCLUDE[ssDE](../includes/ssde-md.md)].  
-  
- To make a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication connection you must supply a SQL Server Authentication login ID and password. When using the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] provider, you must associate the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] login credentials with a virtual drive, and then use the change directory command (**cd**) to connect to that drive. In Windows PowerShell, security credentials can only be associated with virtual drives.  
-  
+
+To make a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication connection you must supply a SQL Server Authentication login ID and password. When using the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] provider, you must associate the [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] login credentials with a virtual drive, and then use the change directory command (**cd**) to connect to that drive. In Windows PowerShell, security credentials can only be associated with virtual drives.  
+
 ## SQL Server Authentication Using a Virtual Drive
 
-**To create a virtual drive associated with a SQL Server Authentication login**  
+### To create a virtual drive associated with a SQL Server Authentication login
 
-1. Create a function that:  
+1. Create a function that:
+
+    1. Has parameters for the name to give the virtual drive, the login ID, and the provider path to associate with the virtual drive.
 
-    1. Has parameters for the name to give the virtual drive, the login ID, and the provider path to associate with the virtual drive.  
-  
     2. Uses **read-host** to prompt the user for the password.  
-  
+
     3. Uses **new-object** to create a credentials object.  
-  
+
     4. Uses **new-psdrive** to create a virtual drive with the supplied credentials.  
-  
+
 2. Invoke the function to create a virtual drive with the supplied credentials.  
 
-### Example (Virtual Drive)
+#### Example (Virtual Drive)
 
 This example creates a function named **sqldrive** that you can use to create a virtual drive that is associated with the specified [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Authentication login and instance.  
 
@@ -68,26 +68,28 @@ sqldrive SQLAuth
   
 ## CD to the virtual drive, which invokes the supplied authentication credentials.  
 cd SQLAuth  
-```  
-  
-##  <a name="SQLAuthInvSqlCmd"></a> SQL Server Authentication Using Invoke-Sqlcmd  
- **To use Invoke-Sqlcmd with SQL Server Authentication**  
-  
-1.  Use the **-Username** parameter to specify a login ID, and the **-Password** parameter to specify the associated password.  
-  
-### Example (Invoke-Sqlcmd)  
- This example uses the read-host cmdlet to prompt the user for a password, and then connects using SQL Server Authentication.  
-  
-```  
+```
+
+## SQL Server Authentication Using Invoke-Sqlcmd
+
+### To use Invoke-Sqlcmd with SQL Server Authentication
+
+1. Use the **-Username** parameter to specify a login ID, and the **-Password** parameter to specify the associated password.  
+
+#### Example (Invoke-Sqlcmd)
+
+This example uses the read-host cmdlet to prompt the user for a password, and then connects using SQL Server Authentication.  
+
+```powershell
 ## Prompt the user for their password.  
 $pwd = read-host -AsSecureString -Prompt "Password"  
   
 Invoke-Sqlcmd -Query "SELECT GETDATE() AS TimeOfQuery;" -ServerInstance "MyComputer\MyInstance" -Username "MyLogin" -Password $pwd  
-```  
-  
-## See Also  
- [SQL Server PowerShell](sql-server-powershell.md)   
- [SQL Server PowerShell Provider](sql-server-powershell-provider.md)   
- [Invoke-Sqlcmd cmdlet](invoke-sqlcmd-cmdlet.md)  
-  
-  
+```
+
+## See Also
+
+- [SQL Server PowerShell](sql-server-powershell.md)
+- [SQL Server PowerShell Provider](sql-server-powershell-provider.md)
+- [Invoke-Sqlcmd cmdlet](https://docs.microsoft.com/powershell/module/sqlserver/invoke-sqlcmd)
+- [Use PowerShell with Azure Data Studio](../azure-data-studio/extensions/powershell-extension.md)

docs/powershell/manage-tab-completion-sql-server-powershell.md

@@ -1,17 +1,19 @@
 ---
-title: "Manage Tab Completion (SQL Server PowerShell) | Microsoft Docs"
+title: Manage Tab Completion (SQL Server PowerShell)
 description: Learn how to control Windows PowerShell tab completion by making proper use of three variables in the SQL Server PowerShell modules.
-ms.custom: ""
-ms.date: "03/14/2017"
 ms.prod: sql
-ms.reviewer: matteot, drskwier
 ms.technology: sql-server-powershell
 ms.topic: conceptual
 ms.assetid: 6296848a-890f-4ad3-8d9f-92ed6a79aa00
 author: markingmyname
 ms.author: maghan
+ms.reviewer: matteot, drskwier
+ms.custom: ""
+ms.date: 10/14/2020
 ---
-# Manage Tab Completion (SQL Server PowerShell)
+
+# Manage Tab Completion with SQL Server PowerShell
+
 [!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW ](../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
 The [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] PowerShell snap-ins introduce three variables (**$SqlServerMaximumTabCompletion**, **$SqlServerMaximumChildItems**, and **$SqlServerIncludeSystemObjects**) to control Windows PowerShell tab completion. Tab completion reduces the amount of typing you must do by returning tables of items whose names start with the string you are typing.  
@@ -20,36 +22,41 @@ The [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] PowerShell snap-ins i
 > There are two SQL Server PowerShell modules; **SqlServer** and **SQLPS**. The **SQLPS** module is included with the SQL Server installation (for backwards compatibility), but is no longer being updated. The most up-to-date PowerShell module is the **SqlServer** module. The **SqlServer** module contains updated versions of the cmdlets in **SQLPS**, and also includes new cmdlets to support the latest SQL features.  
 > Previous versions of the **SqlServer** module *were* included with SQL Server Management Studio (SSMS), but only with the 16.x versions of SSMS. To use PowerShell with SSMS 17.0 and later, the **SqlServer** module must be installed from the PowerShell Gallery.
 > To install the **SqlServer** module, see [Install SQL Server PowerShell](download-sql-server-ps-module.md).
-  
+
 With Windows PowerShell tab-completion, when you have typed part of a path or cmdlet name, you can hit the Tab key to get a list of the items whose names match what you have already typed. You can then select the item you want from the list without having to type the rest of the name.  
-  
+
 If you are working in a database that has many objects, the tab-completion lists can become large. Some [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] object types, such as views, also have large numbers of system objects.  
-  
-The [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] snap-ins introduces three system variables that you can use to control the amount of information presented by tab-completion and **Get-ChildItem**.  
-  
- **$SqlServerMaximumTabCompletion =** *n*  
- Specifies the maximum number of objects to include in a tab-completion list. If you select Tab at a path node having more than *n* objects, the tab-completion list is truncated at *n*. *n* is an integer. 0 is the default setting, and means there is no limit to the number of objects listed.  
-  
- **$SqlServerMaximumChildItems =** *n*  
- Specifies the maximum number of objects displayed by **Get-ChildItem**. If **Get-ChildItem** is run at a path node having more than *n* objects, the list is truncated at *n*. *n* is an integer. 0 is the default setting, and means there is no limit to the number of objects listed.  
-  
- **$SqlServerIncludeSystemObjects =** { **$True** | **$False** }  
- If **$True**, system objects are displayed by tab-completion and **Get-ChildItem**. If **$False**, no system objects are displayed. The default setting is **$False**.  
-  
-## Set the SQL Server Tab Completion Variables  
- For any of the variables you want to change from the default value, set the variable to the new value.  
-  
-### Example (PowerShell)  
- The following example sets all three variables and lists their settings:  
-  
-```  
+
+The [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] snap-ins introduces three system variables that you can use to control the amount of information presented by tab-completion and **Get-ChildItem**.
+
+## $SqlServerMaximumTabCompletion =** *n*
+
+Specifies the maximum number of objects to include in a tab-completion list. If you select Tab at a path node having more than *n* objects, the tab-completion list is truncated at *n*. *n* is an integer. 0 is the default setting, and means there is no limit to the number of objects listed.  
+
+## $SqlServerMaximumChildItems =** *n*
+
+Specifies the maximum number of objects displayed by **Get-ChildItem**. If **Get-ChildItem** is run at a path node having more than *n* objects, the list is truncated at *n*. *n* is an integer. 0 is the default setting, and means there is no limit to the number of objects listed.  
+
+## $SqlServerIncludeSystemObjects =** { **$True** | **$False** }
+
+If **$True**, system objects are displayed by tab-completion and **Get-ChildItem**. If **$False**, no system objects are displayed. The default setting is **$False**.  
+
+## Set the SQL Server Tab Completion Variables
+
+For any of the variables you want to change from the default value, set the variable to the new value.  
+
+### Example (PowerShell)
+
+The following example sets all three variables and lists their settings:  
+
+```powershell
 $SqlServerMaximumTabCompletion = 20  
 $SqlServerMaximumChildItems = 10  
 $SqlServerIncludeSystemObjects = $False  
 dir variable:sqlserver*  
-```  
-  
-## See Also  
- [SQL Server PowerShell](sql-server-powershell.md)  
-  
-  
+```
+
+## See Also
+
+- [Install SQL Server PowerShell](download-sql-server-ps-module.md)
+- [SQL Server PowerShell](sql-server-powershell.md)