Minor wording adjustments and links fixed

No text meaning changes

Documentation/issue-guide.md

@@ -25,7 +25,7 @@ In general, try to be specific. Get straight to the main point. Leave additional
 Provide clear description of your suggestion. Explain scenarios in which it would be helpful and why (motivation).
 Ideally, assume that the reader has minimal knowledge and experience with writing apps/libraries that would benefit from the feature.
 
-For API suggestions, check [API review process](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/api-review-process.md), especially examples of [good API proposals](https://github.com/dotnet/corefx/issues/271).
+For API suggestions, check [API review process](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/api-review-process.md), especially [example of good API proposals](https://github.com/dotnet/corefx/issues/271).
 
 
 
@@ -46,7 +46,7 @@ We use GitHub [labels](https://github.com/dotnet/winforms/labels) on our issues
 
 ## Milestones
 
-We use [milestones](https://github.com/dotnet/corefx/milestones) to prioritize work for each upcoming release.
+We use [milestones](https://github.com/dotnet/winforms/milestones) to prioritize work for each upcoming release.
 
 * **3.0** milestone work is focused on parity with WinForms for .NET Framework. We do not plan to take contributions or address issues that are not unique to WinForms on .NET Core in 3.0 release. For example:
     * Bugs which are present on both WinForms platforms (for .NET Core and .NET Framework) will be put into **Future** milestone and will be reviewed and prioritized after 3.0 final release.
@@ -80,7 +80,7 @@ you can escalate to WinForms team by tagging some of us (e.g. [@merriemcgaw](htt
 
 ## Triage rules
 
-Guidance for triaging issues by WinForms team members:
+Guidance for triaging issues for WinForms team members:
 
 1. Issue has no **Assignee**, unless someone is working on the issue at the moment.
 1. Use **up-for-grabs** as much as possible, ideally with a quick note about next steps / complexity of the issue.