fix link

Fix https://github.com/dotnet/coreclr/issues/8816

Commit migrated from https://github.com/dotnet/coreclr/commit/25dc0b6b7d9ee40a9d64a570ada8821d2e8f0f76

diff --git a/docs/coreclr/project-docs/contributing-workflow.md b/docs/coreclr/project-docs/contributing-workflow.md
index 5c91a49..70423e5 100644 (file)
--- a/docs/coreclr/project-docs/contributing-workflow.md
+++ b/docs/coreclr/project-docs/contributing-workflow.md
@@ -85,7 +85,7 @@ We use and recommend the following workflow:
 1. Create an issue for your work. 
   - You can skip this step for trivial changes.
   - Reuse an existing issue on the topic, if there is one.
-  - Use [CODE_OWNERS.TXT](https://github.com/dotnet/coreclr/blob/CODE_OWNERS.TXT) to find relevant maintainers and @ mention them to ask for feedback on your issue.
+  - Use [CODE_OWNERS.TXT](https://github.com/dotnet/coreclr/blob/master/CODE_OWNERS.TXT) to find relevant maintainers and @ mention them to ask for feedback on your issue.
   - Get agreement from the team and the community that your proposed change is a good one.
   - If your change adds a new API, follow the [API Review Process](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/api-review-process.md). 
   - Clearly state that you are going to take on implementing it, if that's the case. You can request that the issue be assigned to you. Note: The issue filer and the implementer don't have to be the same person.