         application instance. The default application instance is the instance
         that has an instance namespace matching the application namespace (in
         this example, an instance of the ``myapp`` called ``myapp``).
  
      4. If there is no default application instance, Django will pick the first
         deployed instance of the application, whatever its instance name may be.
  
      5. If the provided namespace doesn't match an application namespace in
         step 1, Django will attempt a direct lookup of the namespace as an
         instance namespace.
 
</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 </s> remove       the first instance of ``myapp`` that is registered will be used. This could
 </s> add       the last instance of ``myapp`` that is registered will be used. This could
    4. If there is no default application instance, Django will pick the last
         application instance. The default application instance is the instance
         that has an instance namespace matching the application namespace (in
         this example, an instance of the ``myapp`` called ``myapp``).
  
    4. If there is no default application instance, Django will pick the last
         deployed instance of the application, whatever its instance name may be.
  
      5. If the provided namespace doesn't match an application namespace in
         step 1, Django will attempt a direct lookup of the namespace as an
         instance namespace.
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