Doc: update wording for COOKIES_ENABLED

docs/topics/downloader-middleware.rst

@@ -158,13 +158,13 @@ more of the following methods:
       :type spider: :class:`~scrapy.spiders.Spider` object
 
    .. method:: from_crawler(cls, crawler)
-    
+
       If present, this classmethod is called to create a middleware instance
       from a :class:`~scrapy.crawler.Crawler`. It must return a new instance
       of the middleware. Crawler object provides access to all Scrapy core
       components like settings and signals; it is a way for middleware to
       access them and hook its functionality into Scrapy.
-   
+
       :param crawler: crawler that uses this middleware
       :type crawler: :class:`~scrapy.crawler.Crawler` object
 
@@ -237,16 +237,14 @@ Default: ``True``
 Whether to enable the cookies middleware. If disabled, no cookies will be sent
 to web servers.
 
-Notice that if the :class:`~scrapy.http.Request` 
-has ``meta['dont_merge_cookies']`` evaluated to ``True``. 
-despite the value of :setting:`COOKIES_ENABLED` the cookies will **not** be 
-sent to web servers and received cookies in 
-:class:`~scrapy.http.Response` will **not** be merged with the existing 
-cookies.
-
-For more detailed information see the ``cookies`` parameter in 
-:class:`~scrapy.http.Request`
+Notice that despite the value of :setting:`COOKIES_ENABLED` setting if
+``Request.``:reqmeta:`meta['dont_merge_cookies'] <dont_merge_cookies>`
+evaluates to ``True`` the request cookies will **not** be sent to the
+web server and received cookies in :class:`~scrapy.http.Response` will
+**not** be merged with the existing cookies.
 
+For more detailed information see the ``cookies`` parameter in
+:class:`~scrapy.http.Request`.
 
 .. setting:: COOKIES_DEBUG
 

docs/topics/request-response.rst

@@ -80,6 +80,8 @@ Request objects
         attributes of the cookie. This is only useful if the cookies are saved
         for later requests.
 
+        .. reqmeta:: dont_merge_cookies
+
         When some site returns cookies (in a response) those are stored in the
         cookies for that domain and will be sent again in future requests. That's
         the typical behaviour of any regular web browser. However, if, for some
@@ -294,7 +296,7 @@ Those are:
 * :reqmeta:`dont_retry`
 * :reqmeta:`handle_httpstatus_list`
 * :reqmeta:`handle_httpstatus_all`
-* ``dont_merge_cookies`` (see ``cookies`` parameter of :class:`Request` constructor)
+* :reqmeta:`dont_merge_cookies`
 * :reqmeta:`cookiejar`
 * :reqmeta:`dont_cache`
 * :reqmeta:`redirect_urls`