Skip to content

Commit 4e1dade

Browse files
authored
Update exchange-cmdlet-syntax.md
Another pipe character in a table fix
1 parent e4e9344 commit 4e1dade

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Exchange PowerShell help follows conventions that indicate what's required or op
3131
|-|A hyphen indicates a parameter. For example, `-Identity`.|
3232
|\< \>|Angle brackets indicate the possible values for a parameter. For example, `-Location <ServerName>` or `-Enabled <$true | $false>`.|
3333
|[ ]|Square brackets indicate optional parameters and their values. For example, `[-WhatIf <SwitchParameter>]`. Parameter-value pairs that aren't enclosed in square brackets are required.|
34-
|\| |Pipe symbols in parameter values indicate a choice between values. For example, `-Enabled <$true | $false>` indicates the _Enabled_ parameter can have the value `$true` or `$false`.|
34+
|\| |Pipe symbols in parameter values indicate a choice between values. For example, -Enabled \<$true \| $false\> indicates the _Enabled_ parameter can have the value `$true` or `$false`.|
3535

3636
These command conventions help you understand how a command is constructed. With the exception of the hyphen that indicates a parameter, you don't use these symbols as they're described in the table when you run cmdlets in Exchange PowerShell.
3737

0 commit comments

Comments
 (0)