Database improperly closed in example code

os.unlink(flaskr.DATABASE) causes the actual application database to be
purged; whereas, I reckon, one wants the _test_ database to be removed.
So every time I ran it, the test passed, but ended up crashing the live
app for want of a valid database.

I avoided using the sample code in examples/flaskr thus far, as I chose
to type out code from the turorial docs. The actual example code looks
good - at least to my beginner's eye.
Flash messages signals

If we send a signal when a template is rendered why not when a message
is flashed? One real world use case is in tests, this signal should make
flash messages expectation easier to implement.
fix typo in quickstart guide
Added more information about app factories.
Merge pull request #693 from untitaker/factory_docs

Added more information about app factories.
Merge pull request #692 from mikegagnon/patch-1

fix typo in quickstart guide
Merge pull request #687 from poiati/flash-signal

Flash messages signals
Documented new signal message_flashed
Add import to jsonify example.
Fixed a few typos on quickstart
Updated jquery.rst with the current Google Developer hosted libraries URL and jquery version
Added self to AUTHORS file
Merge pull request #700 from SpOOnman/master

Add import to jsonify example
Merge pull request #701 from bruston/quickstart-typod

Fixed a few typos in the quickstart doc
fixing process_response

Flask.process_response will throw away functions is receives from ctx._after_request_functions if there is a Blueprint that has used @after_request.
Update README

No need to manually initialize the database with a call to `init_db()` as this call is done before `app.run()` in flaskr.py, when you run the file.
Documented new signal message_flashed
Fixed typo in URL Processor documentation
Syntax highlighting for PyPI long description
Fixed documentation in 'Design Decisions in Flask'