Rename titles of pages to be more descriptive.

docs/benchmarks.rst

@@ -1,5 +1,5 @@
-Benchmarks
-==========
+Decorator Benchmarks
+====================
 
 The **wrapt** module ensures that your decorators will work in all
 situations. The implementation therefore does not take the shortcuts that

docs/changes.rst

@@ -1,5 +1,5 @@
-Changes
-=======
+Release Notes
+=============
 
 Version 1.2.0
 -------------

docs/decorators.rst

@@ -1,5 +1,5 @@
-Decorators
-==========
+Function Decorators
+===================
 
 The **wrapt** module provides various components, but the main reason that
 it likely is to be used is for creating decorators. This document covers the

docs/examples.rst

@@ -1,12 +1,12 @@
-Examples
-========
+Assorted Examples
+=================
 
 This document provides various examples of decorators often described
 elsewhere, to exhibit what can be done with decorators using the **wrapt**
 module, for the purpose of comparison.
 
-Synchronization
----------------
+Thread Synchronization
+----------------------
 
 .. note::
     The final variant of the ``synchronized`` decorator described here

docs/issues.rst

@@ -1,5 +1,5 @@
-Issues
-======
+Known Issues
+============
 
 The following known issues exist.
 

docs/quick-start.rst

@@ -1,5 +1,5 @@
-Quick Start
-===========
+Getting Started
+===============
 
 To implement your decorator you need to first define a wrapper function.
 This will be called each time a decorated function is called. The wrapper

docs/testing.rst

@@ -1,5 +1,5 @@
-Testing
--------
+Running Unit Tests
+==================
 
 Unit tests are located in the ``tests`` directory.
 

docs/wrappers.rst

@@ -1,5 +1,5 @@
-Wrappers
-========
+Proxies and Wrappers
+====================
 
 Underlying the implementation of the decorators created by the **wrapt**
 module is a wrapper class which acts as a transparent object proxy. This