markdown tweaking

Known-Issues.md

@@ -1,4 +1,5 @@
-## Can't use EC256 on Linux/Mac
+## Can't use EC Keys on PowerShell Core
 
-The `ECDsa` implementation for non-Windows platforms utilizes [ECDsaOpenSsl](https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.ecdsaopenssl). As of .NET Core 2.0 which is what is distributed with PowerShell Core 6, `ECDsaOpenSsl` doesn't contain a `SignData` method.
+In .NET Core 2.0 which is what is distributed with PowerShell Core 6, the [`ECDsaOpenSsl`](https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.ecdsaopenssl) implementation is missing the `SignData` method which means we can't sign stuff using EC-based keys on non-Windows platforms. 
 
+Additionally, `ECDsaCng` in PowerShell Core on Windows has the `SignData` method, but I can't get it to work for some reason. The same code that works in Desktop edition throws an exception in Core, *"Cannot find an overload for "SignData" and the argument count: "1"."*

Posh-ACME/notes.md → Notes.md

@@ -10,9 +10,3 @@ Ironically, PowerShell Core 6 has added `-ResponseHeadersVariable` which solves
 But it doesn't really make sense to have completely separate code paths for Core right now.
 So we're left hoping they back-port the parameter or sufficient time passes that restricting
 people to Core is feasible.
-
-## No ECDsa.SignData on Core editions
-
-In .NET Core 2.0, the `ECDsaOpenSsl` implementation is missing the `SignData` method which means we can't sign stuff using EC-based keys on non-Windows platforms. 
-
-Additionally, `ECDsaCng` in PowerShell Core on Windows has the `SignData` method, but I can't get it to work for some reason. The same code that works in Desktop edition throws an exception in Core, *"Cannot find an overload for "SignData" and the argument count: "1"."*