README.md in sifttter-redux-0.4.4 vs README.md in sifttter-redux-0.4.6

@@ -10,22 +10,12 @@
 * Packaged as a command line app, complete with documentation and help
 * Easy installation on cron for automated running
 
 # Prerequisites
 
-In addition to Git (which, given you being on this site, I'll assume you have), there are two prerequisites needed to run Sifttter Redux in a *NIX environment:
+In addition to Git (which, given you being on this site, I'll assume you have), Ruby (v. 1.9.3 or greater) is needed.
 
-* Ruby (version 1.9.3 or greater)
-* UUID (required on the Raspberry Pi because it doesn't come with a function to do this by default)
-
-To install on a Debian-esque system:
-
-```
-$ sudo apt-get install ruby
-$ sudo apt-get install uuid
-```
-
 # Installation
 
 ```
 gem install sifttter-redux
 ```
@@ -45,11 +35,11 @@
 
 SYNOPSIS
     srd [global options] command [command options] [arguments...]
 
 VERSION
-    0.4.1
+    0.4.6
 
 GLOBAL OPTIONS
     --help         - Show this message
     --[no-]verbose - Turns on verbose output
     --version      - Display the program version
@@ -94,9 +84,25 @@
 3. Collect some user preferences:
  * The location on your filesystem where Sifttter files will be temporarily stored
  * The location of your Sifttter files in Dropbox
  * The location on your filesystem where Day One files will be temporarily stored
  * The location of your Day One files in Dropbox
+
+## Pathing
+
+Note that when Sifttter Redux asks you for paths, it will ask for "local" and "remote" filepaths. It's important to understand the difference.
+
+### Local Filepaths
+
+Local filepaths are, as you'd expect, filepaths on your local machine. Some examples might be:
+
+* `/tmp/my_data`
+* `/home/bob/ifttt/sifttter_data`
+* `~/sifttter`
+
+### Remote Filepaths
+
+Remote filepaths, on the other hand, are absolute filepaths in your Dropbox folder (*as Dropbox Uploader would see them*). For instance, `/home/bob/Dropbox/apps/sifttter` is *not* a valid remote filepath; rather, `/apps/sifttter` would be correct.
 
 ## Basic Execution
 
 ```
 $ srd exec
\ No newline at end of file