  
      * If there is no current instance - say, if we were rendering a page
        somewhere else on the site - ``myapp:index`` will resolve to the first
        registered instance of ``myapp``. Since there is no default instance,
        the first instance of ``myapp`` that is registered will be used. This could
        be ``foo`` or ``bar``, depending on the order they are introduced into the
        urlpatterns of the project.
  
      * ``foo:index`` will always resolve to the index page of the instance ``foo``.
  
 
</s> remove     4. If there is no default application instance, Django will pick the first
 </s> add     4. If there is no default application instance, Django will pick the last </s> remove       somewhere else on the site - ``myapp:index`` will resolve to the first
 </s> add       somewhere else on the site - ``myapp:index`` will resolve to the last
      the last instance of ``myapp`` that is registered will be used. This could
  
      * If there is no current instance - say, if we were rendering a page
        somewhere else on the site - ``myapp:index`` will resolve to the first
        registered instance of ``myapp``. Since there is no default instance,
      the last instance of ``myapp`` that is registered will be used. This could
        be ``foo`` or ``bar``, depending on the order they are introduced into the
        urlpatterns of the project.
  
      * ``foo:index`` will always resolve to the index page of the instance ``foo``.
  
keep keep keep keep replace keep keep keep keep keep
 Fixed #13051 -- Corrected the documentation of URL namespacing to match the tested implementation behavior. Thanks to apollo13 for the report, and Gabriel Hurley for the patch.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@13161 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/topics/http/urls.txt