Create run-windows-powershell-steps-in-sql-server-agent.md

ms.date, headings

Author: WilliamDAssafMSFT

docs/powershell/run-windows-powershell-steps-in-sql-server-agent.md

@@ -8,7 +8,7 @@ author: markingmyname
 ms.author: maghan
 ms.reviewer: matteot, drskwier
 ms.custom: seo-lt-2019
-ms.date: 03/16/2017
+ms.date: 11/19/2021
 ---
 
 # Run Windows PowerShell Steps in SQL Server Agent
@@ -21,7 +21,7 @@ Use SQL Server Agent to run SQL Server PowerShell scripts at scheduled times.
 
 [!INCLUDE[sql-server-powershell-no-sqlps](../includes/sql-server-powershell-no-sqlps.md)]
 
-## To run PowerShell from SQL Server Agent
+## Run PowerShell from SQL Server Agent
 
 There are several types of SQL Server Agent job steps. Each type is associated with a subsystem that implements a specific environment, such as a replication agent or command prompt environment. You can code Windows PowerShell scripts, and then use SQL Server Agent to include the scripts in jobs that run at scheduled times or in response to SQL Server events. Windows PowerShell scripts can be run using either a command prompt job step or a PowerShell job step.
 
@@ -35,7 +35,7 @@ Each SQL Server Agent job step that runs PowerShell with the **sqlps** module la
 
 ## <a name="PShellJob"></a> Create a PowerShell Job Step
 
-### To create a PowerShell job step
+### Create a PowerShell job step
 
 1. Expand **SQL Server Agent**, create a new job or right-click an existing job, and then select **Properties**. For more information about creating a job, see [Creating Jobs](../ssms/agent/create-jobs.md).
 
@@ -53,7 +53,7 @@ Each SQL Server Agent job step that runs PowerShell with the **sqlps** module la
 
 ## <a name="CmdExecJob"></a> Create a Command Prompt Job Step
 
-### To create a CmdExec job step
+### Create a CmdExec job step
 
 1. Expand **SQL Server Agent**, create a new job or right-click an existing job, and then select **Properties**. For more information about creating a job, see [Creating Jobs](../ssms/agent/create-jobs.md).
 
@@ -67,7 +67,7 @@ Each SQL Server Agent job step that runs PowerShell with the **sqlps** module la
 
 6. In the **Process exit code of a successful command** box, enter a value from 0 to 999999.
 
-7. In the **Command** box, enter commands beginning with PowerShell.exe with parameters specifying the PowerShell script to be run. These examples are similar to the syntax for executing PowerShell commands from a Windows command prompt. Refer to `PowerShell.exe -?` for all the possible syntax options.
+7. In the **Command** box, enter PowerShell.exe with parameters specifying the PowerShell script to be run. This is pretty much what you would write at a cmd command prompt, so take a look at `PowerShell.exe -?` for all the possible options.
 
    - Example 1: Runs a simple cmdlet.
      ```cmd
@@ -82,7 +82,7 @@ Each SQL Server Agent job step that runs PowerShell with the **sqlps** module la
         PWSH.exe -ExecutionPolicy RemoteSigned -File X:\MyScripts\script001.ps1 
      ```
 
-8. select the **Advanced** page to set job step options, such as: what action to take if the job step succeeds or fails, how many times SQL Server Agent should try to execute the job step, and the file where SQL Server Agent can write the job step output. Only members of the **sysadmin** fixed server role can write job step output to an operating system file.
+8. Select the **Advanced** page to set job step options, such as: what action to take if the job step succeeds or fails, how many times SQL Server Agent should try to execute the job step, and the file where SQL Server Agent can write the job step output. Only members of the **sysadmin** fixed server role can write job step output to an operating system file.
 
 ## See Also