Updated vim and do_process sections

Prose describing how to transfer to Clarizen included in do_process section.

README.md

@@ -55,7 +55,7 @@ The output looks like this:
 
 Section total:          8.41hrs
 ```
-You may have noticed, the output of timetracker.py is in alphabetical order by category, then by task.  This follows for `./do_process` and `./chug` below.
+You may have noticed, the output of timetracker.py is in alphabetical order by category, then by task.  This follows for `./do_process` and `./chug` below.  
 
 ## `do_process`
 This script filters the output of timetracker.py, giving each category (in square brackets) its own section, with its own tallies.  The header is the list of categories and the log file basename (below this is `example`, but would normally be a date such as `2017-12-08`).  After the header, each line of output and sections are designed to be directly transferred to Clarizen manually, and the tally used to verify the daily and weekly totals in Clarizen.  It calculates the time total for each organization/category.  At the end it prints a grand total for the day, which should be used to cross-verify in Clarizen.
@@ -106,6 +106,8 @@ Grand total:          8.41hrs
 
 It takes as its argument a filename with the current date (`date +%F` format, such as `./do_process 2020-03-12`), or it assumes the current date log file.  The `.log` filename suffix is assumed (and should not be passed to `./do_process`).  Also, arbitrary filenames can be passed, so `example.log` becomes `./do_process example`.
 
+Projects in Clarizen are listed alphabetically, so to transfer data from the `./do_process` output you simply copy the data lines from the ouput put, and paste it into the notes section of the Clarizen entry.  Enter the duration of the task at the top of the Clarizen entry, and select the category and subcategory of the entry.
+
 ## `chug`
 This script is designed to be run on Mondays, after the previous week of log files have been generated and closed out. The standard Monday usage takes no arguments, it expects all log files to be processed to be in the current directory.  It runs `do_process` once for each day of the previous week, cleanly skipping any log files which do not exist.  It pauses after each day report is output, allowing the user to transfer the times manually to Clarizen.  
 
@@ -124,7 +126,7 @@ In the same vein as month-pack.sh, year-pack.sh tars up all the monthly tarballs
 Since I (the author, Trey Blancher) have been using this system to keep track of time, I've noticed that sometimes either Clarizen or these scripts get slightly off.  Usually it's no more than 0.25 hours off in the tallies, but it gets time consuming trying to track down where the tally went wrong.  If I do find the culprit, it's usually because I've entered the wrong time for a specific task in Clarizen (i.e., entering '0.08' instead of '0.25' for some tasks).
 
 ## vim
-The vim-specific files in this repository are tailored for my tastes.  One big item of note, I've disabled vim cursor navigation with the arrow keys (Up, Down, Left, Right), to force me to get into the habit of using h, j, k, l for cursor navigation.  You will probably want to delete the following lines from .vimrc if you're not interested in the true Vim way (R):
+The vim-specific files in this repository are tailored for my tastes.  One big item of note, I've disabled vim cursor navigation with the arrow keys (Up, Down, Left, Right), to force me to get into the habit of using h, j, k, l for cursor navigation, and only navigate in normal mode (not insert mode).  You will probably want to delete the following lines from .vimrc if you're not interested in the true Vim way®:
 ```
 " Force me to stop using arrow keys
 inoremap <Left> <Nop>