From 81b71cba43d53b5707e0c6455274bd2a9d3da3a5 Mon Sep 17 00:00:00 2001 From: LarryWeiss Date: Fri, 22 Mar 2019 16:54:51 -0500 Subject: [PATCH] Update Learning-PowerShell-Names.md (#4038) copyedit in the Note regarding running sc.exe --- reference/docs-conceptual/learn/Learning-PowerShell-Names.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/reference/docs-conceptual/learn/Learning-PowerShell-Names.md b/reference/docs-conceptual/learn/Learning-PowerShell-Names.md index 38c4d8ba12e5..a2a65cbb5fa3 100644 --- a/reference/docs-conceptual/learn/Learning-PowerShell-Names.md +++ b/reference/docs-conceptual/learn/Learning-PowerShell-Names.md @@ -34,8 +34,9 @@ To list tasks running on DC01, you use the **/S** parameter and the computer nam backslashes. For example, `tasklist /S DC01`. > [!NOTE] -> Prior to PowerShell v6, `sc` was an alias for the `Set-Content` cmdlet. To run the **sc.exe** -> command, you must include the file extension. +> Prior to PowerShell v6, `sc` was an alias for the `Set-Content` cmdlet. Therefore, to run +> the **sc.exe** command in a version of PowerShell prior to v6, you must include the +> full filename **sc.exe** including the file extension **exe**. Services and processes are examples of manageable elements on a computer that have well-defined life cycles. You may start or stop services and processes, or get a list of all currently