Fix documentation build warnings

docs/conf.py

@@ -99,7 +99,7 @@ release = __version__
 
 # List of patterns, relative to source directory, that match files and
 # directories to ignore when looking for source files.
-exclude_patterns = ['_build']
+exclude_patterns = ['_build', 'README.md']
 
 # The reST default role (used for this markup: `text`) to use for all
 # documents.

docs/contributing/security.md

@@ -40,7 +40,7 @@ On the day of disclosure, we will take the following steps:
 
 1. Apply the relevant patch(es) to Wagtail\'s codebase.
    The commit messages for these patches will indicate that they are for security issues, but will not describe the issue in any detail; instead, they will warn of upcoming disclosure.
-2. Issue the relevant release(s), by placing new packages on [the Python Package Index](https://pypi.org/project/wagtail/), tagging the new release(s) in Wagtail\'s GitHub repository and updating Wagtail\'s [release notes](../releases/).
+2. Issue the relevant release(s), by placing new packages on [the Python Package Index](https://pypi.org/project/wagtail/), tagging the new release(s) in Wagtail\'s GitHub repository and updating Wagtail\'s [release notes](../releases/index).
 3. Post a public entry on [Wagtail\'s blog](https://wagtail.io/blog/), describing the issue and its resolution in detail, pointing to the relevant patches and new releases, and crediting the reporter of the issue (if the reporter wishes to be publicly identified).
 4. Post a notice to the [Wagtail support forum](https://groups.google.com/d/forum/wagtail) and Twitter feed ([\@WagtailCMS](https://twitter.com/wagtailcms)) that links to the blog post.
 

docs/getting_started/index.md

@@ -46,7 +46,7 @@ $ ./manage.py runserver
 Your site is now accessible at `http://localhost:8000`, with the admin backend available at `http://localhost:8000/admin/`.
 
 This will set you up with a new stand-alone Wagtail project.
-If you\'d like to add Wagtail to an existing Django project instead, see [Integrating Wagtail into a Django project](integrating_into_django).
+If you\'d like to add Wagtail to an existing Django project instead, see [Integrating Wagtail into a Django project](/getting_started/integrating_into_django).
 
 There are a few optional packages which are not installed by default but are recommended to improve performance or add features to Wagtail, including:
 

docs/getting_started/tutorial.md

@@ -205,7 +205,7 @@ of a `RichTextField`:
 
 Produces:
 
-``` {.html}
+```html
 <p>
     <b>Welcome</b> to our new site!
 </p>

wagtail/core/models.py

@@ -1210,6 +1210,7 @@ class Page(AbstractPage, index.Indexed, ClusterableModel, metaclass=PageBase):
 
         By default, references to all non-field attribute values are copied
         from current object to the returned one. This includes:
+
         * Values set by a queryset, for example: annotations, or values set as
           a result of using ``select_related()`` or ``prefetch_related()``.
         * Any ``cached_property`` values that have been evaluated.