Update code contribution documentation

Signed-off-by: Jono Yang <jyang@nexb.com>

Author: JonoYang

docs/source/contributing/contrib_code.rst

@@ -1,9 +1,9 @@
 .. _contributing:
 
-Contributing to ScanCode.io
+Contributing to AboutCode
 ===========================
 
-Thank you so much for being so interested in contributing to ScanCode.io. We
+Thank you so much for being so interested in contributing to AboutCode. We
 are always on the lookout for enthusiastic contributors like you who can make
 our project better, and we're willing to lend a helping hand if you have any
 questions or need guidance along the way. That being said, here are a few
@@ -17,25 +17,22 @@ Do Your Homework
 ----------------
 
 Before adding a contribution or create a new issue, take a look at the project’s
-`README <https://github.com/aboutcode-org/scancode.io#readme>`_, read through our
-`documentation <https://scancodeio.readthedocs.io/en/latest/>`_,
-and browse existing `issues <https://github.com/aboutcode-org/scancode.io/issues>`_,
-to develop some understanding of the project and confirm whether a given
+README, read through existing documentation, and browse existing issues to
+develop some understanding of the project and confirm whether a given
 issue/feature has previously been discussed.
 
 Ways to Contribute
 ------------------
 
-Contributing to the codebase is not the only way to add value to ScanCode.io or
+Contributing to the codebase is not the only way to add value to AboutCode or
 join our community. Below are some examples to get involved:
 
 First Timers
 ^^^^^^^^^^^^
 
 You are here to help, but you're a new contributor! No worries, we always
-welcome newcomer contributors. We maintain some
-`good first issues <https://github.com/aboutcode-org/scancode.io/labels/good%20first%20issue>`_
-and encourage new contributors to work on those issues for a smooth start.
+welcome newcomer contributors. We maintain some good first issues and encourage
+new contributors to work on those issues for a smooth start.
 
 .. warning::
     **"Can I work on this issue?"**
@@ -55,12 +52,10 @@ and encourage new contributors to work on those issues for a smooth start.
 Report Issues
 ^^^^^^^^^^^^^
 
-- Report a new `bug <https://github.com/aboutcode-org/scancode.io/issues>`_; just remember to be
-  as specific as possible.
-- Create a `new issue <https://github.com/aboutcode-org/scancode.io/issues>`_ to request a
-  feature, submit a feedback, or ask a question.
-- Look into existing `bugs <https://github.com/aboutcode-org/scancode.io/labels/bug>`_,
-  try to reproduce the issue on your side, and discuss solutions in the comments.
+- Report a new bug, issue, questions, or suggestions in the "Issues" page of the
+  project's GitHub repo; just remember to be as specific as possible.
+- Look into existing bugs and try to reproduce the issue on your side, and
+  discuss solutions in the comments.
 
 .. note::
     Make sure to check existing `issues <https://github.com/aboutcode-org/scancode.io/issues>`_,
@@ -70,10 +65,10 @@ Report Issues
 Code Contributions
 ^^^^^^^^^^^^^^^^^^
 
-Code is contributed to the codebase using **pull requests**.
-A pull request should always be attached to an existing issue.
-When there is no existing issues, start by `creating one <https://github.com/aboutcode-org/scancode.io/issues>`_
-to discuss potential solutions and implementation details before writing any code.
+Code is contributed to the codebase using **pull requests**. A pull request
+should always be attached to an existing issue. When there is no existing
+issues, create one to discuss potential solutions and implementation details
+before writing any code.
 
 We use several conventions to ensure code quality regarding format, testing, and
 attribution.
@@ -115,29 +110,27 @@ Documentation Improvements
 ^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Documentation is a critical aspect of any project that is usually neglected or
-overlooked. We value any suggestions to improve
-`ScanCode.io documentation <https://scancodeio.readthedocs.io/en/latest/>`_.
+overlooked. We value any suggestions to improve ours.
 
 .. tip::
     Our documentation is treated like code. Make sure to check our
-    `writing guidelines <https://scancode-toolkit.readthedocs.io/en/latest/contribute/contrib_doc.html>`_
-    to help guide new users.
+    :ref:`writing guidelines <contrib_doc_dev>` to help guide new users.
 
 Other Ways
 ^^^^^^^^^^
 
-You want to contribute to other aspects of the ScanCode.io project, and you
-can't find what you're looking for! You can always discuss new topics, ask
-questions, and interact with us and other community members on
+You want to contribute to other aspects of AboutCode, and you can't find what
+you're looking for! You can always discuss new topics, ask questions, and
+interact with us and other community members on
 `Gitter <https://gitter.im/aboutcode-org/discuss>`_.
 
 .. _contributing_resources:
 
 Helpful Resources
 -----------------
 
-- Review our `comprehensive guide <https://scancode-toolkit.readthedocs.io/en/latest/contribute/index.html>`_
-  for more details on how to add quality contributions to our codebase and documentation
+- Review our :ref:`comprehensive guide <contrib_doc_dev>` for more details on
+  how to add quality contributions to our codebase and documentation
 - Check this free resource on `how to contribute to an open source project on github <https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github>`_
 - Follow `this wiki page <https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html>`_
   on how to write good commit messages