Clean and fix documentation

docs/features.rst

@@ -10,7 +10,7 @@ URLs
 
 WeasyPrint can read normal files, HTTP, FTP and `data URIs`_. It will follow
 HTTP redirects but more advanced features like cookies and authentication
-are currently not supported, although a custom :ref:`url fetcher
+are currently not supported, although a custom :ref:`URL fetcher
 <url-fetchers>` can help.
 
 .. _data URIs: http://en.wikipedia.org/wiki/Data_URI_scheme
@@ -47,6 +47,7 @@ generated by WeasyPrint is missing some of the features you expect from the
 HTML, try to enable this option.
 
 .. _presentational hints: http://www.w3.org/TR/html5/rendering.html#presentational-hints
+.. _Pillow: https://python-pillow.org/
 
 
 PDF

docs/index.rst

@@ -13,5 +13,3 @@ Documentation contents
     features
     hacking
     changelog
-
-.. include:: ../AUTHORS

docs/tutorial.rst

@@ -322,7 +322,7 @@ resources. This timeout has no effect with other protocols, including access to
 If you use WeasyPrint on a server with HTML or CSS samples coming from
 untrusted users, or need to reach network resources, you should:
 
-- use a custom `URL fetcher <url-fetchers>`_,
+- use a custom :ref:`URL fetcher <url-fetchers>`,
 - follow solutions listed in :ref:`long-renderings`.
 
 Infinite loops
@@ -373,7 +373,7 @@ If you use WeasyPrint on a server with HTML or CSS samples coming from
 untrusted users, you should:
 
 - restrict your process access to trusted files using sandboxing solutions,
-- use a custom `URL fetcher <url-fetchers>`_ that doesn't allow ``file://``
+- use a custom :ref:`URL fetcher <url-fetchers>` that doesn't allow ``file://``
   URLs or filters access depending on given paths.
 - follow solutions listed in :ref:`long-renderings`.