Tiny fixes in documentation.

docs/developers/shortcuts.rst

@@ -12,7 +12,7 @@ paginate
 
 .. function:: paginate(object_list, page, per_page, orphans=0, allow_empty_first_page=True)
 
-This function is a factory that validates received data and returns `Django's Page <https://docs.djangoproject.com/en/dev/topics/pagination/#page-objects>`_ object. In adition it also translates ``EmptyPage`` errors into ``Http404`` errors and validated is first page number was explictly defined in url parameter, or not.
+This function is a factory that validates received data and returns `Django's Page <https://docs.djangoproject.com/en/dev/topics/pagination/#page-objects>`_ object. In adition it also translates ``EmptyPage`` errors into ``Http404`` errors and validates if first page number was explictly defined in url parameter or not.
 
 ``paginate`` function has certain requirements on handling views that use it. Firstly, views with pagination should have two links instead of one::
 

docs/developers/views_errors.rst

@@ -17,7 +17,7 @@ Views Exceptions
 ================
 
 
-While Misago raises plenty of exceptions, only four are allowed to reach views. Two of those are django's ``Http404`` and ``PermissionDenied`` exceptions. In addition to those, Misago defines its own two exceptions that act as "messages" for it's error handler that link user clicked to get to view is not up-to-date and could use 301 request to make sure bookmarks and crawlers get clean link.
+While Misago raises plenty of exceptions, only four are allowed to leave views. Two of those are django's ``Http404`` and ``PermissionDenied`` exceptions. In addition to those, Misago defines its own two exceptions that act as "messages" for it's error handler that link user clicked to get to view is not up-to-date and could use 301 request to make sure bookmarks and crawlers get clean link.
 
 .. note::
    You should never raise those exceptions yourself. If you want to redirect user to certain page, return proper redirect response instead.