diff --git a/docs/contributing.rst b/docs/contributing.rst
index 823979d0b..eef92e148 100644
--- a/docs/contributing.rst
+++ b/docs/contributing.rst
@@ -11,13 +11,6 @@ Contributing to Scrapy
 
 There are many ways to contribute to Scrapy. Here are some of them:
 
-* Contribute to Scrapy by fixing currently available issues in the repository.
-  See :ref:`contributing-to-scrapy-codebase` below for more information.
-
-* Blog about Scrapy. Tell the world how you're using Scrapy. This will help
-  newcomers with more examples and will help the Scrapy project to increase its
-  visibility.
-
 * Report bugs and request features in the `issue tracker`_, trying to follow
   the guidelines detailed in `Reporting bugs`_ below.
 
@@ -25,25 +18,16 @@ There are many ways to contribute to Scrapy. Here are some of them:
   :ref:`writing-patches` and `Submitting patches`_ below for details on how to
   write and submit a patch.
 
+* Blog about Scrapy. Tell the world how you're using Scrapy. This will help
+  newcomers with more examples and will help the Scrapy project to increase its
+  visibility.
+
 * Join the `Scrapy subreddit`_ and share your ideas on how to
   improve Scrapy. We're always open to suggestions.
 
 * Answer Scrapy questions at
   `Stack Overflow <https://stackoverflow.com/questions/tagged/scrapy>`__.
 
-.. _contributing-to-scrapy-codebase:
-
-===============================
-Contributing to Scrapy codebase
-===============================
-
-Scrapy has a list of `good first issues`_ and `help wanted issues`_ that you
-can work on. These issues are a great way to get started with contributing to
-Scrapy. If you're new to the codebase, you may want to focus on documentation
-or testing-related issues, as they are always useful and can help you get
-more familiar with the project. You can also check Scrapy's `test coverage`_
-to see which areas may benefit from more tests.
-
 Reporting bugs
 ==============
 
@@ -95,6 +79,13 @@ guidelines when you're going to report a new bug.
 Writing patches
 ===============
 
+Scrapy has a list of `good first issues`_ and `help wanted issues`_ that you
+can work on. These issues are a great way to get started with contributing to
+Scrapy. If you're new to the codebase, you may want to focus on documentation
+or testing-related issues, as they are always useful and can help you get
+more familiar with the project. You can also check Scrapy's `test coverage`_
+to see which areas may benefit from more tests.
+
 The better a patch is written, the higher the chances that it'll get accepted and the sooner it will be merged.
 
 Well-written patches should: