Fixed broken links in computer_science/CONTRIBUTING.md.

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 ## New contributor guide
 
-To get an overview of the project, read the [README](README.md). Here are some resources to help you get started with open source contributions:
+To get an overview of the project, read the [README](https://github.com/shhossain/computer_science/blob/main/readme.md). Here are some resources to help you get started with open source contributions:
 
 - [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
 - [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git)
@@ -10,9 +10,9 @@ To get an overview of the project, read the [README](README.md). Here are some r
 
 ## Getting started
 
-To navigate our codebase with confidence, see [the introduction to working in the docs repository](/contributing/working-in-docs-repository.md) :confetti_ball:. For more information on how we write our markdown files, see [the GitHub Markdown reference](contributing/content-markup-reference.md).
+To navigate our codebase with confidence, see [the introduction to working in the docs repository](https://docs.github.com/en/get-started/quickstart/hello-world) :confetti_ball:. For more information on how we write our markdown files, see [the GitHub Markdown reference](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
 
-Check to see what [types of contributions](/contributing/types-of-contributions.md) we accept before making changes. Some of them don't even require writing a single line of code :sparkles:.
+Check to see what [types of contributions](https://github.com/github/docs/blob/main/contributing/types-of-contributions.md) we accept before making changes. Some of them don't even require writing a single line of code :sparkles:.
 
 ### Issues
 
@@ -22,7 +22,7 @@ If you spot a problem with the docs, [search if an issue already exists](https:/
 
 #### Solve an issue
 
-Scan through our [existing issues](/issues) to find one that interests you. You can narrow down the search using `labels` as filters. See [Labels](/contributing/how-to-use-labels.md) for more information. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
+Scan through our [existing issues](https://github.com/shhossain/computer_science/issues) to find one that interests you. You can narrow down the search using `labels` as filters. See [Labels](https://github.com/abdonrd/github-labels) for more information. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
 
 ### Make Changes
 
@@ -33,7 +33,7 @@ Click **Make a contribution** at the bottom of any docs page to make small chang
 
 #### Make changes in a codespace
 
-For more information about using a codespace for working on GitHub documentation, see "[Working in a codespace](https://github.com/github/docs/blob/main/contributing/codespace.md)."
+For more information about using a code space for working on GitHub documentation, see "[Working in a codespace](https://github.com/github/docs/blob/main/contributing/codespace.md)."
 
 #### Make changes locally
 
@@ -47,15 +47,15 @@ For more information about using a codespace for working on GitHub documentation
 - Using the command line:
   - [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them.
 
-3. Install or update to **Node.js v16**. For more information, see [the development guide](contributing/development.md).
+3. Install or update to **Node.js v16**. For more information, see [the development guide](https://github.com/PacktPublishing/Complete-Guide-to-Node.js-Development).
 
 4. Create a working branch and start with your changes!
 
 ### Commit your update
 
 Commit the changes once you are happy with them. See [Atom's contributing guide](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#git-commit-messages) to know how to use emoji for commit messages.
 
-Once your changes are ready, don't forget to [self-review](/contributing/self-review.md) to speed up the review process:zap:.
+Once your changes are ready, don't forget to [self-review](https://github.com/github/docs/blob/main/contributing/self-review.md) to speed up the review process:zap:.
 
 ### Pull Request
 
@@ -74,4 +74,4 @@ Congratulations :tada::tada: The GitHub team thanks you :sparkles:.
 
 Once your PR is merged, your contributions will be publicly visible on the [GitHubs docs](https://docs.github.com/en). 
 
-Now that you are part of the GitHub docs community, see how else you can [contribute to the docs](/contributing/types-of-contributions.md).
+Now that you are part of the GitHub docs community, see how else you can [contribute to the docs](https://github.com/github/docs/blob/main/CONTRIBUTING.md).