From 2ef9d52c235af11584907cf2cca6b278d13b5aca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Adri=C3=A1n=20Chaves?= <adrian@chaves.io>
Date: Tue, 11 Feb 2020 00:56:20 +0100
Subject: [PATCH] Clarify the scope of @abstractspider

It can be used regardless of the value of SPIDER_LOADER_REQUIRE_NAME.
---
 docs/topics/spiders.rst | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/docs/topics/spiders.rst b/docs/topics/spiders.rst
index 27f9ded81..991a5131a 100644
--- a/docs/topics/spiders.rst
+++ b/docs/topics/spiders.rst
@@ -836,19 +836,20 @@ How you mark a spider as a concrete spider depends on the value of the
     concrete spider.
 
 -   If :setting:`SPIDER_LOADER_REQUIRE_NAME` is ``False``, all spiders are
-    considered concrete spiders by default. Use
-    :func:`~scrapy.spiders.abstractspider` to mark a spider as an abstract
-    spider:
+    considered concrete spiders by default.
 
-    .. autodecorator:: scrapy.spiders.abstractspider
+Use :func:`~scrapy.spiders.abstractspider` to mark a spider as an abstract
+spider:
 
-    For example::
+.. autodecorator:: scrapy.spiders.abstractspider
 
-        from scrapy import abstractspider, Spider
+For example::
 
-        @abstractspider
-        class MyBaseSpider(Spider):
-            pass
+    from scrapy import abstractspider, Spider
 
-        class MySpider(MyBaseSpider):
-            pass
+    @abstractspider
+    class MyBaseSpider(Spider):
+        pass
+
+    class MySpider(MyBaseSpider):
+        pass