Join-PipeScript: Improving Unnamed end block behavior (Fixes #363)

Author: StartAutomating

docs/ValidatePropertyName.md

@@ -1,14 +1,26 @@
 ValidatePropertyName
 --------------------
+
+
+
+
 ### Synopsis
 Validates Property Names
 
+
+
 ---
+
+
 ### Description
 
 Validates that an object has one or more property names.
 
+
+
 ---
+
+
 ### Examples
 #### EXAMPLE 1
 ```PowerShell
@@ -44,49 +56,53 @@ $InputObject
 ```
 $InputObject
     }
+
+
 ---
+
+
 ### Parameters
 #### **PropertyName**
 
 The property names being validated.
 
 
 
-> **Type**: ```[String[]]```
 
-> **Required**: true
 
-> **Position**: 1
 
-> **PipelineInput**:false
+|Type        |Required|Position|PipelineInput|
+|------------|--------|--------|-------------|
+|`[String[]]`|true    |1       |false        |
 
 
 
----
 #### **VariableAST**
 
 A variable expression.
 If this is provided, will apply a ```[ValidateScript({})]``` attribute to the variable, constraining future values.
 
 
 
-> **Type**: ```[VariableExpressionAst]```
 
-> **Required**: false
 
-> **Position**: named
 
-> **PipelineInput**:true (ByValue)
+|Type                     |Required|Position|PipelineInput |
+|-------------------------|--------|--------|--------------|
+|`[VariableExpressionAst]`|false   |named   |true (ByValue)|
+
+
 
 
 
 ---
+
+
 ### Syntax
 ```PowerShell
 ValidatePropertyName [-PropertyName] <String[]> [<CommonParameters>]
 ```
 ```PowerShell
 ValidatePropertyName [-PropertyName] <String[]> [-VariableAST <VariableExpressionAst>] [<CommonParameters>]
 ```
----