Skip to content

Commit 590da98

Browse files
authored
Markdown fixes
1 parent c988e64 commit 590da98

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

Style-Guide/Naming-Conventions.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ gps -Name Explorer
1414
Get-Process -Name Explorer
1515
```
1616

17-
#### Use full parameter names.
17+
#### Use full parameter names.
1818

1919
Because there are so many commands in PowerShell, it's impossible for every scripter to know every command. Therefore it's useful to be explicit about your parameter names for the sake of readers who may be unfamiliar with the command you're using. This will also help you avoid bugs if a future change to the command alters the parameter sets.
2020

@@ -44,7 +44,7 @@ Get-Content (Join-Path $PSScriptRoot README.md)
4444
[System.IO.File]::ReadAllText("$PSScriptRoot\README.md")
4545
```
4646

47-
##### Avoid the use of `~` to represent the home folder.
47+
##### Avoid the use of `~` to represent the home folder.
4848

4949
The meaning of ~ is unfortunately dependent on the "current" provider at the time of execution. This isn't really a style issue, but it's an important rule for code you intend to share anyway. Instead, use `${Env:UserProfile}` or `(Get-PSProvider FileSystem).Home` ...
5050

@@ -58,6 +58,4 @@ At line:1 char:1
5858
+ ~~~~
5959
+ CategoryInfo : InvalidOperation: (:) [Set-Location], PSInvalidOperationException
6060
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.SetLocationCommand
61-
6261
```
63-

0 commit comments

Comments
 (0)