s/*Paperless*/Paperless/g

docs/consumption.rst

@@ -19,7 +19,7 @@ loop looking for new additions to this directory and when it finds them, it goes
 about the process of parsing them with the OCR, indexing what it finds, and
 encrypting the PDF, storing it in the media directory.
 
-Getting stuff into this directory is up to you.  If you're running *Paperless*
+Getting stuff into this directory is up to you.  If you're running Paperless
 on your local computer, you might just want to drag and drop files there, but if
 you're running this on a server and want your scanner to automatically push
 files to this directory, you'll need to setup some sort of service to accept the
@@ -85,7 +85,7 @@ IMAP (Email)
 
 Another handy way to get documents into your database is to email them to
 yourself.  The typical use-case would be to be out for lunch and want to send a
-copy of the receipt back to your system at home.  *Paperless* can be taught to
+copy of the receipt back to your system at home.  Paperless can be taught to
 pull emails down from an arbitrary account and dump them into the consumption
 directory where the process :ref:`above <consumption-directory>` will follow the
 usual pattern on consuming the document.
@@ -159,7 +159,7 @@ and store it on the server and the client.  Then use that secret, along with
 the text you want to verify to generate a string that you can use for
 verification.
 
-In the case of *Paperless*, you configure the server with the secret by setting
+In the case of Paperless, you configure the server with the secret by setting
 ``UPLOAD_SHARED_SECRET``.  Then on your client, you generate your signature by
 concatenating the correspondent, title, and the secret, and then using sha256
 to generate a hexdigest.

docs/migrating.rst

@@ -3,7 +3,7 @@
 Migrating, Updates, and Backups
 ===============================
 
-As *Paperless* is still under active development, there's a lot that can change
+As Paperless is still under active development, there's a lot that can change
 as software updates roll out.  You should backup often, so if anything goes
 wrong during an update, you at least have a means of restoring to something
 usable.  Thankfully, there are automated ways of backing up, restoring, and

docs/requirements.rst

@@ -87,15 +87,15 @@ enter it, and install the requirements using the ``requirements.txt`` file:
     $ pip install  --requirement /path/to/paperless/requirements.txt
 
 Now you're ready to go.  Just remember to enter your virtualenv whenever you
-want to use *Paperless*.
+want to use Paperless.
 
 
 .. _requirements-documentation:
 
 Documentation
 -------------
 
-As generation of the documentation is not required for use of *Paperless*,
+As generation of the documentation is not required for use of Paperless,
 dependencies for this process are not included in ``requirements.txt``.  If
 you'd like to generate your own docs locally, you'll need to:
 

docs/utilities.rst

@@ -3,7 +3,7 @@
 Utilities
 =========
 
-There's basically three utilities to *Paperless*: the webserver, consumer, and
+There's basically three utilities to Paperless: the webserver, consumer, and
 if needed, the exporter.  They're all detailed here.
 
 
@@ -12,7 +12,7 @@ if needed, the exporter.  They're all detailed here.
 The Webserver
 -------------
 
-At the heart of it, *Paperless* is a simple Django webservice, and the entire
+At the heart of it, Paperless is a simple Django webservice, and the entire
 interface is based on Django's standard admin interface.  Once running, visiting
 the URL for your service delivers the admin, through which you can get a
 detailed listing of all available documents, search for specific files, and
@@ -86,7 +86,7 @@ service files in the ``scripts`` directory.
 The Exporter
 ------------
 
-Tired of fiddling with *Paperless*, or just want to do something stupid and are
+Tired of fiddling with Paperless, or just want to do something stupid and are
 afraid of accidentally damaging your files?  You can export all of your PDFs
 into neatly named, dated, and unencrypted.