  Here's how Django uses the sites framework:
  
  * In the :mod:`redirects framework <django.contrib.redirects>`, each
    redirect object is associated with a particular site. When Django searches
    for a redirect, it takes into account the current :setting:`SITE_ID`.
  
  * In the comments framework, each comment is associated with a particular
    site. When a comment is posted, its
    :class:`~django.contrib.sites.models.Site` is set to the current
    :setting:`SITE_ID`, and when comments are listed via the appropriate
 
</s> remove   :class:`~django.contrib.sites.models.Site` is set to the current
  :setting:`SITE_ID`, and when comments are listed via the appropriate
  template tag, only the comments for the current site are displayed.
 </s> add   :class:`~django.contrib.sites.models.Site` is set to the current site,
  and when comments are listed via the appropriate template tag, only the
  comments for the current site are displayed. </s> remove   checks the current :setting:`SITE_ID` in retrieving flatpages to display.
 </s> add   checks the current site in retrieving flatpages to display. </s> remove For code which relies on getting the current domain but cannot be certain
that the sites framework will be installed for any given project, there is a
utility function :func:`~django.contrib.sites.models.get_current_site` that
takes a request object as an argument and returns either a Site instance (if
the sites framework is installed) or a RequestSite instance (if it is not).
This allows loose coupling with the sites framework and provides a usable
fallback for cases where it is not installed.

.. function:: get_current_site(request)

    Checks if contrib.sites is installed and returns either the current
    :class:`~django.contrib.sites.models.Site` object or a
    :class:`~django.contrib.sites.models.RequestSite` object based on
    the request.

 </s> add  </s> remove     sites.get_current().domain, for example, as that is unique across a Django
 </s> add     sites.get_current_site().domain, for example, as that is unique across a Django </s> remove       from django.conf import settings
 </s> add       from django.contrib.sites.models import get_current_site
  for a redirect, it takes into account the current site.
  Here's how Django uses the sites framework:
  
  * In the :mod:`redirects framework <django.contrib.redirects>`, each
    redirect object is associated with a particular site. When Django searches
  for a redirect, it takes into account the current site.
  
  * In the comments framework, each comment is associated with a particular
    site. When a comment is posted, its
    :class:`~django.contrib.sites.models.Site` is set to the current
    :setting:`SITE_ID`, and when comments are listed via the appropriate
keep keep keep keep replace keep keep keep keep keep
 Made more extensive use of get_current_site

Refs #15089 
docs/ref/contrib/sites.txt