Update extending-output-objects.md (#2618)

* Update extending-output-objects.md

- removing duplicate sentences and paragraphs
- marking output of Get-Member -InputObject ... as code (type output), since original formatting messes up line breaks

* Update extending-output-objects.md

- Removed duplicated sentence
- Changed ps prompt to be consistent
- Proper cased PowerShell parameters and properties
- Minor markdown fixes

Author: purdo17

developer/cmdlet/extending-output-objects.md

@@ -30,34 +30,37 @@ The following example shows how Windows PowerShell extends the [System.Array](/d
 
 ```
 
-To see this new alias property, use a [Get-Member](/powershell/module/Microsoft.PowerShell.Utility/Get-Member) command on any array, as shown in the following example.
 To see this new alias property, use a [Get-Member](/powershell/module/Microsoft.PowerShell.Utility/Get-Member) command on any array, as shown in the following example.
 
-**Get-Member -inputobject (1,2,3,4)**
+```powershell
+Get-Member -InputObject (1,2,3,4)
+```
 
 The command returns the following results.
+```output
+Name           MemberType    Definition
+----           ----------    ----------
+Count          AliasProperty Count = Length
+Address        Method        System.Object& Address(Int32 )
+Clone          Method        System.Object Clone()
+CopyTo         Method        System.Void CopyTo(Array array, Int32 index):
+Equals         Method        System.Boolean Equals(Object obj)
+Get            Method        System.Object Get(Int32 )
+...
+Length         Property      System.Int32 Length {get;}
+```
+You can use either the `Count` property or the `Length` property to determine how many objects are in an array. For example:
 
-**Name           MemberType    Definition**
-**----           ----------    ----------**
-**Count          AliasProperty Count = Length**
-**Address        Method        System.Object& Address(Int32 )**
-**Clone          Method        System.Object Clone()**
-**CopyTo         Method        System.Void CopyTo(Array array, Int32 index):**
-**Equals         Method        System.Boolean Equals(Object obj)**
-**Get            Method        System.Object Get(Int32 )**
-**...**
-**Length         Property      System.Int32 Length {get;}** You can use either the `Count` property or the `Length` property to determine how many objects are in an array. For example:
-
-```python
-PS> (1, 2, 3, 4).count
+```powershell
+PS> (1, 2, 3, 4).Count
 ```
 
 ```output
 4
 ```
 
-```python
-(1, 2, 3, 4).length
+```powershell
+PS> (1, 2, 3, 4).Length
 ```
 
 ```output
@@ -66,7 +69,7 @@ PS> (1, 2, 3, 4).count
 
 ## Custom Types Files
 
-To create a custom types file, start by copying an existing types file. The new file can have any name, but it must have a .ps1xml file name extension. When you copy the file, you can place the new file in any directory that is accessible to Windows PowerShell, but it is useful to place the files in the Windows PowerShell installation directory `($pshome`) or in a subdirectory of the installation directory.
+To create a custom types file, start by copying an existing types file. The new file can have any name, but it must have a .ps1xml file name extension. When you copy the file, you can place the new file in any directory that is accessible to Windows PowerShell, but it is useful to place the files in the Windows PowerShell installation directory (`$pshome`) or in a subdirectory of the installation directory.
 
 To add your own extended types to the file, add a types element for each object that you want to extend. The following topics provide examples.
 
@@ -79,14 +82,10 @@ To add your own extended types to the file, add a types element for each object
 After you define your own extended types, use one of the following methods to make your extended objects available:
 
 - To make your extended types file available to the current session, use the [Update-TypeData](/powershell/module/Microsoft.PowerShell.Utility/Update-TypeData) cmdlet to add the new file. If you want your types to take precedence over the types that are defined in other types files (including the Types.ps1xml file), use the `PrependData` parameter of the [Update-TypeData](/powershell/module/Microsoft.PowerShell.Utility/Update-TypeData) cmdlet.
-- To make your extended types file available to the current session, use the [Update-TypeData](/powershell/module/Microsoft.PowerShell.Utility/Update-TypeData) cmdlet to add the new file. If you want your types to take precedence over the types that are defined in other types files (including the Types.ps1xml file), use the `PrependData` parameter of the [Update-TypeData](/powershell/module/Microsoft.PowerShell.Utility/Update-TypeData) cmdlet.
-
-To make your extended types file available to all future sessions, add the types file to a module, export the current session, or add the [Update-TypeData](/powershell/module/Microsoft.PowerShell.Utility/Update-TypeData) command to your Windows PowerShell profile.
-To make your extended types file available to all future sessions, add the types file to a module, export the current session, or add the [Update-TypeData](/powershell/module/Microsoft.PowerShell.Utility/Update-TypeData) command to your Windows PowerShell profile.
+- To make your extended types file available to all future sessions, add the types file to a module, export the current session, or add the [Update-TypeData](/powershell/module/Microsoft.PowerShell.Utility/Update-TypeData) command to your Windows PowerShell profile.
 
 ## Signing Types Files
 
-Types files should be digitally signed to prevent tampering because the XML can include script blocks. For more information about adding digital signatures, see [about_Signing](/powershell/module/microsoft.powershell.core/about/about_signing)
 Types files should be digitally signed to prevent tampering because the XML can include script blocks. For more information about adding digital signatures, see [about_Signing](/powershell/module/microsoft.powershell.core/about/about_signing)
 
 ## See Also