Skip to content

Commit 59b660d

Browse files
authored
Change 'Powershell' to 'PowerShell'.
Two times 'Powershell' was written in this text instead of 'PowerShell', which makes them inconsistent with the rest of the text where it was properly written as 'PowerShell'.
1 parent 5f7cf65 commit 59b660d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Style-Guide/Documentation-and-Comments.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ It is also possible to write `.PARAMETER` statements with the rest of the docume
9898

9999
##### Provide Usage Examples
100100

101-
Your help should always provide an example for each major use case. A 'usage example' is just an example of what you would type in to Powershell to run the script - you can even cut and paste one from the command line while you're testing your function.
101+
Your help should always provide an example for each major use case. A 'usage example' is just an example of what you would type in to PowerShell to run the script - you can even cut and paste one from the command line while you're testing your function.
102102

103103
```PowerShell
104104
function Test-Help {
@@ -171,4 +171,4 @@ Comment-based help is displayed when the user types `help Get-Example` or `Get-E
171171

172172
Your help should be helpful. That is, if you've written a tool called `Get-LOBAppUser`, don't write help that merely says, "Gets LOB App Users." Duh.
173173

174-
**Further information:** You can get more on the use of comment-based help by typing `help about_Comment_Based_Help` within Powershell.
174+
**Further information:** You can get more on the use of comment-based help by typing `help about_Comment_Based_Help` within PowerShell.

0 commit comments

Comments
 (0)