Fixed typo ('cause' not 'case')

INSTALL.md

@@ -58,7 +58,7 @@ Here are the basics:
      What these vim macros do is copy the category and task name from the above line (should be a Begin task), and paste it to the end of the End line.  This should eliminate any mistakes when setting the end time of a task.  Note that if a mistake is made on the Begin line, that mistake will be propagated to the End line when the "Insert Timestampt End" macro is executed. 
 1.  Both the "Insert Timestamp Begin" and "Insert Timestamp End" macros automatically press the Escape key (`Esc`), so you can trigger them from normal/command mode, or insert mode.  In vim, trigger the "Insert Timestamp Begin" macro by typing `⌘+Shift+D`, then `B` (or whatever you changed the trigger to be).  If you haven't changed the trigger, a ![Conflict Dialog][conflict_dialog] will pop up, where you can choose the desired macro (either with your mouse, or by typing `B` for Begin, or `E` for End).
 1.  If you have chosen the "Insert Timestamp Begin" macro, you can type a category (`[In Square Brackets]`), then the title of the task you are beginning.  Note that the title is free form, but having square brackets in the title, outside of the category is untested.  Any other characters should be valid.
-    - NOTE:  If you use the Rust programs for digesting your logs, having multiple categories/strings inside square brackets will case the Rust program to panic.  The older Python/Bash scripts handle this a bit more gracefully at the time of this writing.
+    - NOTE:  If you use the Rust programs for digesting your logs, having multiple categories/strings inside square brackets will cause the Rust program to panic.  The older Python/Bash scripts handle this a bit more gracefully at the time of this writing.
 1.  When you're finished with the task, run the "Insert Timestamp End" macro.  You should see the timestamp with the "End" keyword, and the category and title of the above Begin task copied verbatim.  Then the macro will automatically print another Begin line, ready for the next task.
 
 Reach out to me (Trey Blancher, tblancher@pindrop.com), if you have questions or problems with this procedure.  Or better yet, file an issue under the timetracker repository on GitHub.