Updating docs.

docs/source/overview.rst

@@ -219,8 +219,8 @@ file, generated by :code:`pyupdater pkg --process --sign`, using the
 :code:`bsdiff` Python module.
 
 
-Running the v0.0.1 EXE with a Full Download Update Available
-------------------------------------------------------------
+Running the v0.0.1 EXE with a Full Update Available to Download
+---------------------------------------------------------------
 
 If v0.0.1 of PyUpdaterWxDemo.exe detects that a new version (v0.0.2) is
 available, it should be able to apply a patch, if it already has a signed
@@ -375,6 +375,10 @@ This time the application has retrieved :code:`versions.gz` from the file server
 and concluded that there are no available updates, i.e. we are already running
 the latest version.
 
+
+Running the v0.0.1 EXE with an Already-Downloaded Update Available
+------------------------------------------------------------------
+
 Now let's run PyUpdaterWxDemo.exe (extracted from PyUpdaterWxDemo-win-0.0.1.zip)
 again.  This time, it should launch more quickly, i.e. it won't need to
 redownload the v0.0.2 update - it should already be available in the user data
@@ -383,12 +387,12 @@ directory - :code:`C:\Users\wettenhj\AppData\Local\Company Name\PyUpdaterWxDemo\
 .. image:: images/updated_app_running_after_full_download.png
 
 
-Running the v0.0.2 EXE with a Patch Update Available
-----------------------------------------------------
+Running the v0.0.1 EXE with an Already-Downloaded Full Update and a Patch Update Available
+------------------------------------------------------------------------------------------
 
 Now that we have a signed v0.0.2 package in our user data directory -
 :code:`C:\Users\wettenhj\AppData\Local\Company Name\PyUpdaterWxDemo\update`,
-if we create a v0.0.3, we should be able to upgrade to that version via
+if we create a v0.0.3 package, we should be able to upgrade to that version via
 a patch, instead of downloading the full package.
 
 First, we need to increment the version in :code:`wxupdatedemo/__init__.py`