Update not found links to ml-workspace in CONTRIBUTING.md

CONTRIBUTING.md

@@ -20,16 +20,16 @@ Everyone is welcome to contribute, and we value everybody's contribution. Code i
 
 ## Issues and bug reports
 
-- We use GitHub issues to track bugs and enhancement requests. Submit issues for any [feature request and enhancement](https://github.com/ml-tooling/workspace/issues/new?assignees=&labels=feature&template=02_feature-request.md&title=), [bugs](https://github.com/ml-tooling/workspace/issues/new?assignees=&labels=bug&template=01_bug-report.md&title=), or [documentation](https://github.com/ml-tooling/workspace/issues/new?assignees=&labels=documentation&template=03_documentation.md&title=) problems.
+- We use GitHub issues to track bugs and enhancement requests. Submit issues for any [feature request and enhancement](https://github.com/ml-tooling/ml-workspace/issues/new?assignees=&labels=feature&template=02_feature-request.md&title=), [bugs](https://github.com/ml-tooling/ml-workspace/issues/new?assignees=&labels=bug&template=01_bug-report.md&title=), or [documentation](https://github.com/ml-tooling/ml-workspace/issues/new?assignees=&labels=documentation&template=03_documentation.md&title=) problems.
 - First, do a quick search on the Github issue tracker or the known issues section in the readme to see if the issue has already been reported. If so, it's often better to just leave a comment on an existing issue rather than creating a new one. Old - and sometimes closed - issues also often include helpful tips and solutions to common problems.
-- When creating an issue, try using one of our [issue templates](https://github.com/ml-tooling/workspace/issues/new/choose) which already contain some guidelines on which content is expected to process the issue most efficiently. If no template applies, you can of course also create an issue from scratch.
+- When creating an issue, try using one of our [issue templates](https://github.com/ml-tooling/ml-workspace/issues/new/choose) which already contain some guidelines on which content is expected to process the issue most efficiently. If no template applies, you can of course also create an issue from scratch.
 - Please provide as much context as possible when you open an issue. The information you provide must be comprehensive enough to reproduce that issue for the assignee. Therefore, contributors should use but aren't restricted to the issue template provided by the project maintainers.
-- Please apply one or more applicable [labels](https://github.com/ml-tooling/workspace/labels) to your issue so that all community members are able to cluster the issues better.
+- Please apply one or more applicable [labels](https://github.com/ml-tooling/ml-workspace/labels) to your issue so that all community members are able to cluster the issues better.
 - If you have questions about one of the existing issues, please comment on them, and one of the maintainers will clarify.
 
 ## Contributing to the code base
 
-You are welcome to contribute code in order to fix a bug, to implement a new feature, to propose new documentation, or just to fix a typo. Check out [good first issue](https://github.com/ml-tooling/workspace/labels/good%20first%20issue) and [help wanted](https://github.com/ml-tooling/workspace/labels/help%20wanted) issues if you want to find open issues to implement.
+You are welcome to contribute code in order to fix a bug, to implement a new feature, to propose new documentation, or just to fix a typo. Check out [good first issue](https://github.com/ml-tooling/ml-workspace/labels/good%20first%20issue) and [help wanted](https://github.com/ml-tooling/ml-workspace/labels/help%20wanted) issues if you want to find open issues to implement.
 
 - Before writing code, we strongly advise you to search through the existing PRs or issues to make sure that nobody is already working on the same thing. If you find your issue already exists, make relevant comments and add your reaction (👍 - upvote, 👎 - downvote). If you are unsure, it is always a good idea to open an issue to get some feedback.
 - Should you wish to work on an existing issue that has not yet been claimed, please claim it first by commenting on the GitHub issue that you want to work on and begin work (the maintainers will assign it to your GitHub user as soon as they can). This is to prevent duplicated efforts from other contributors on the same issue.