docs: Mention PS 5.1 bug where Start-Transcript inverts when it should log Write-Information messages (#11803)

* docs: Mention Windows PowerShell 5 bug where Write-Information logic is reversed in Start-Transcript

* Update note on `Start-Transcript` behavior

editorial

* Fix formatting issues in Start-Transcript documentation

---------

Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>

Author: deadlydog

reference/5.1/Microsoft.PowerShell.Host/Start-Transcript.md

@@ -266,6 +266,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 -WarningAction, and -WarningVariable. For more information, see
 [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
+
 ## INPUTS
 
 ### None
@@ -285,6 +286,13 @@ To stop a transcript, use the `Stop-Transcript` cmdlet.
 To record an entire session, add the `Start-Transcript` command to your profile. For more
 information, see [about_Profiles](../Microsoft.PowerShell.Core/About/about_Profiles.md).
 
+> [!NOTE]
+> When you use `Start-Transcript`, the default value of `$InformationPreference` is changed to
+> `Continue`. Output from `Write-Information` is written to the console, but not to the transcript
+> file. If the `$InformationPreference` is set to `SilentlyContinue`, Information messages aren't
+> written to the console, but are written to the transcript file. This is fixed in PowerShell 6 and
+> higher.
+
 ## RELATED LINKS
 
 [Stop-Transcript](Stop-Transcript.md)