Fix links

Author: sdwheeler

reference/docs-conceptual/developer/cmdlet/advisory-development-guidelines.md

@@ -175,9 +175,9 @@ because it can be easily converted to a plain text string. For a full discussion
 [10]: xref:System.Management.Automation.Cmdlet.EndProcessing
 [11]: xref:System.Management.Automation.Cmdlet.ProcessRecord
 [12]: xref:System.Management.Automation.Cmdlet.StopProcessing
-[13]: xref:System.Management.Automation.Cmdlet.WriteError
-[14]: xref:System.Management.Automation.Cmdlet.WriteObject
+[13]: xref:System.Management.Automation.Cmdlet.WriteError%2A
+[14]: xref:System.Management.Automation.Cmdlet.WriteObject%2A
 [15]: xref:System.Management.Automation.PSCredential
 [16]: xref:System.Security.SecureString
 [17]: xref:Microsoft.PowerShell.Management.Get-Process
-[18]: xref:Microsoft.PowerShell.ManagementRemove-Item
+[18]: xref:Microsoft.PowerShell.Management.Remove-Item

reference/docs-conceptual/security/security-features.md

@@ -53,8 +53,8 @@ The Windows Antimalware Scan Interface (AMSI) is an API that allows applications
 an antimalware scanner, such as Windows Defender, to scan for malicious payloads. Beginning with
 PowerShell 5.1, PowerShell running on Windows 10 (and higher) passes all script blocks to AMSI.
 
-PowerShell 7.3 extends the data it sends to AMSI for inspection. It now includes all invocations of
-.NET method members.
+PowerShell 7.3 extends the data it sends to AMSI for inspection. It now includes all .NET method
+invocations.
 
 For more information about AMSI, see [How AMSI helps][09].