diff --git a/docs/faq/admin.txt b/docs/faq/admin.txt
index 872ad25..0e3913d 100644
      
        
          
        
        
          
            | 
              a
             | 
            
              b
             | 
            
               things:
               
             | 
          
        
        
          
            | 11 | 11 | * Set the :setting:`SESSION_COOKIE_DOMAIN` setting in your admin config | 
          
          
            | 12 | 12 |   file to match your domain. For example, if you're going to | 
          
          
            | 13 | 13 |   "http://www.example.com/admin/" in your browser, in | 
          
        
        
          
            | 14 |   |   "myproject.settings" you should set ``SESSION_COOKIE_DOMAIN = 'www.example.com'``. | 
          
          
            |   | 14 |   "myproject.settings" you should set :setting:`SESSION_COOKIE_DOMAIN` = 'www.example.com'. | 
          
        
        
          
            | 15 | 15 |  | 
          
          
            | 16 | 16 | * Some browsers (Firefox?) don't like to accept cookies from domains that | 
          
          
            | 17 | 17 |   don't have dots in them. If you're running the admin site on "localhost" | 
          
        
        
          
            | … | 
            … | 
            
               I can't log in. When I enter a valid username and password, it brings up the log
               
             | 
          
        
        
          
            | 23 | 23 | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | 
          
          
            | 24 | 24 |  | 
          
          
            | 25 | 25 | If you're sure your username and password are correct, make sure your user | 
          
        
        
          
            | 26 |   | account has ``is_active`` and ``is_staff`` set to True. The admin site only | 
          
          
            |   | 26 | account has :attr:`~django.contrib.auth.models.User.is_active` and :attr:`~django.contrib.auth.models.User.is_staff` set to True. The admin site only | 
          
        
        
          
            | 27 | 27 | allows access to users with those two fields both set to True. | 
          
          
            | 28 | 28 |  | 
          
          
            | 29 | 29 | How can I prevent the cache middleware from caching the admin site? | 
          
        
        
          
            | … | 
            … | 
            
               My "list_filter" contains a ManyToManyField, but the filter doesn't display.
               
             | 
          
        
        
          
            | 64 | 64 | Django won't bother displaying the filter for a ``ManyToManyField`` if there | 
          
          
            | 65 | 65 | are fewer than two related objects. | 
          
          
            | 66 | 66 |  | 
          
        
        
          
            | 67 |   | For example, if your ``list_filter`` includes ``sites``, and there's only one | 
          
          
            |   | 67 | For example, if your :attr:`~django.contrib.admin.ModelAdmin.list_filter` includes :doc:`sites </ref/contrib/sites>`, and there's only one | 
          
        
        
          
            | 68 | 68 | site in your database, it won't display a "Site" filter. In that case, | 
          
          
            | 69 | 69 | filtering by site would be meaningless. | 
          
          
            | 70 | 70 |  | 
          
        
        
          
            | … | 
            … | 
            
               How can I customize the functionality of the admin interface?
               
             | 
          
        
        
          
            | 85 | 85 |  | 
          
          
            | 86 | 86 | You've got several options. If you want to piggyback on top of an add/change | 
          
          
            | 87 | 87 | form that Django automatically generates, you can attach arbitrary JavaScript | 
          
        
        
          
            | 88 |   | modules to the page via the model's ``class Admin`` ``js`` parameter. That | 
          
          
            |   | 88 | modules to the page via the model's :ref:`class Admin js<modeladmin-media-definitions>` parameter. That | 
          
        
        
          
            | 89 | 89 | parameter is a list of URLs, as strings, pointing to JavaScript modules that | 
          
          
            | 90 | 90 | will be included within the admin form via a ``<script>`` tag. | 
          
          
            | 91 | 91 |  |