From f8bd6416483974559b37487ba89a7bc2ec23b448 Mon Sep 17 00:00:00 2001 From: Markus Fleschutz Date: Wed, 23 Aug 2023 08:21:54 +0200 Subject: [PATCH] Update FAQ.md --- Docs/FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Docs/FAQ.md b/Docs/FAQ.md index 0689a297..f2a5448e 100644 --- a/Docs/FAQ.md +++ b/Docs/FAQ.md @@ -129,7 +129,7 @@ Want to use the PowerShell scripts everywhere on the command-line? Then you need **Good PowerShell scripts are both user-friendly and platform-independent. As a starting point I recommend the following:** -* As filename use the -.ps1 scheme. Approved verbs can be found here: [https://learn.microsoft.com/en-us/powershell/scripting/developer/cmdlet/approved-verbs-for-windows-powershell-commands](https://learn.microsoft.com/en-us/powershell/scripting/developer/cmdlet/approved-verbs-for-windows-powershell-commands) +* As filename use the `-.ps1` scheme. Approved verbs can be found here: [https://learn.microsoft.com/en-us/powershell/scripting/developer/cmdlet/approved-verbs-for-windows-powershell-commands](https://learn.microsoft.com/en-us/powershell/scripting/developer/cmdlet/approved-verbs-for-windows-powershell-commands) * Use **UTF-8 BOM** encoding to support Unicode characters in the script. * Add a **comment-based help** at the beginning with: `.SYNOPSIS`, `.DESCRIPTION`, `.PARAMETER`, `.EXAMPLE`, `.LINK`, and `.NOTES`. * Check the **requirements** for the script, e.g. `#Requires -RunAsAdministrator`, or `#Requires -Version 3`