diff --git a/docs/ref/exceptions.txt b/docs/ref/exceptions.txt
index bee8559..956ee5a 100644
a
|
b
|
URL Resolver exceptions
|
131 | 131 | |
132 | 132 | URL Resolver exceptions are defined in :mod:`django.core.urlresolvers`. |
133 | 133 | |
| 134 | Resolver404 |
| 135 | -------------- |
| 136 | .. exception:: Resolver404 |
| 137 | |
| 138 | The :exc:`Resolver404` exception is raised by |
| 139 | :func:`django.core.urlresolvers.resolve()` if the path passed to |
| 140 | ``resolve()`` doesn't map to a view. It's a subclass of |
| 141 | :class:`django.http.Http404` |
| 142 | |
134 | 143 | NoReverseMatch |
135 | 144 | -------------- |
136 | 145 | .. exception:: NoReverseMatch |
diff --git a/docs/ref/urlresolvers.txt b/docs/ref/urlresolvers.txt
index 87c0605..9419de8 100644
a
|
b
|
worry about the ``urlconf`` parameter. The function returns a
|
102 | 102 | :class:`ResolverMatch` object that allows you |
103 | 103 | to access various meta-data about the resolved URL. |
104 | 104 | |
105 | | If the URL does not resolve, the function raises an |
106 | | :class:`~django.http.Http404` exception. |
| 105 | If the URL does not resolve, the function raises a |
| 106 | :exc:`~django.core.urlresolvers.Resolver404` exception (subclass of |
| 107 | :class:`~django.http.Http404`) . |
107 | 108 | |
108 | 109 | .. class:: ResolverMatch |
109 | 110 | |