  
  The domain to be used when setting the CSRF cookie.  This can be useful for
  easily allowing cross-subdomain requests to be excluded from the normal cross
  site request forgery protection.  It should be set to a string such as
  ``".example.com"`` to allow a POST request from a form on one subdomain to be
  accepted by a view served from another subdomain.
  
  Please note that the presence of this setting does not imply that Django's CSRF
  protection is safe from cross-subdomain attacks by default - please see the
  :ref:`CSRF limitations <csrf-limitations>` section.
 
</s> remove       ``domain=".lawrence.com"`` will set a cookie that is readable by
      the domains www.lawrence.com, blogs.lawrence.com and
      calendars.lawrence.com. Otherwise, a cookie will only be readable by
      the domain that set it.
 </s> add       ``domain="example.com"`` will set a cookie that is readable by the
      domains www.example.com, blog.example.com, etc. Otherwise, a cookie will
      only be readable by the domain that set it. </s> remove ``".example.com"`` (note the leading dot!) for cross-domain cookies, or use
``None`` for a standard domain cookie.
 </s> add ``"example.com"`` for cross-domain cookies, or use ``None`` for a standard
domain cookie. </s> remove ``".example.com"`` (note the leading dot!) for cross-domain cookies, or use
``None`` for a standard domain cookie.
 </s> add ``"example.com"`` for cross-domain cookies, or use ``None`` for a standard
domain cookie. </s> remove # A string like ".example.com", or None for standard domain cookie.
 </s> add # A string like "example.com", or None for standard domain cookie.
``"example.com"`` to allow a POST request from a form on one subdomain to be
  
  The domain to be used when setting the CSRF cookie.  This can be useful for
  easily allowing cross-subdomain requests to be excluded from the normal cross
  site request forgery protection.  It should be set to a string such as
``"example.com"`` to allow a POST request from a form on one subdomain to be
  accepted by a view served from another subdomain.
  
  Please note that the presence of this setting does not imply that Django's CSRF
  protection is safe from cross-subdomain attacks by default - please see the
  :ref:`CSRF limitations <csrf-limitations>` section.
keep keep keep keep replace keep keep keep keep keep
 Fixed #28741 -- Removed unnecessary leading dot from cross-domain cookie examples. 
docs/ref/settings.txt