Typos

CHANGELOG

@@ -1,6 +1,6 @@
 Version 1.2 - 2015-03-10
 
-- Rollback the migration to Jessie and use Wheezy again: the only importantant depencendy from Jessie was poppler, which is available in the backports
+- Rollback the migration to Jessie and use Wheezy again: the only important dependency from Jessie was poppler, which is available in the backports
 - Use the most recent security patches
 - Do not wait for user input in case of password protected archive
 

NOTES

@@ -3,23 +3,23 @@ Notes
 
 * don't plug in USB devices with a hub because there's no way to tell it which
   is source and target - its the first drive enumerated (top port) that is the
-  source and the second (bootom port) is the target
-* don't turn it off without shuting down the system, when grooming is done it
+  source and the second (bottom port) is the target
+* don't turn it off without shutting down the system, when grooming is done it
   shuts down automatically: losing power while it's running can trash the OS
   on the SD cards because SD cards don't always like dirty shutdowns (ie power loss)
 * Using a target usb stick that has a status light as long as the device has
   power is a really useful thing as there the other status lights on the groomer
-  are less than indicative at times: because teh 'OK' led on the rPi toggles on activity
+  are less than indicative at times: because the 'OK' led on the rPi toggles on activity
   it can be off for a long time while processing something and only comes back
   on when that process finishes - hence why a USB that has some sort of LED activity
-  when jsut plugged in (even if not reading or writing but while the USB port is
+  when just plugged in (even if not reading or writing but while the USB port is
   powered) is helpful in determining when the process is finished - when
-  teh rPI is shutdown, the USB port power is shut off and that LED will also
+  the rPI is shutdown, the USB port power is shut off and that LED will also
   then be off on the USB device
 * Use a larger target device as all zip files get unpacked and processed onto
   the target
 * if you have an hdmi monitor plugged in you can watch what's happening for about
-  30 mintues until the rPI's power saving's kick in and turn off the monitor
+  30 minutes until the rPI's power saving kicks in and turns off the monitor
 * if only one usb stick is present at power up, it doesn't groom and looks like
   a normal rPi
 * if you want to ssh into the rPi username is 'pi' password 'raspberry' as per defaults
@@ -29,14 +29,14 @@ Technical notes
 ===============
 
 * groomer script is in /opt/groomer/ with the other required files
-* dependancies are libre-office and OpenJRE
+* dependencies are libre-office and OpenJRE
 * and the ip address is 192.168.1.89
 * the groomer process is kicked off in /etc/rc.local
 * the heavy lifting takes place or is dispatched from /opt/groomer/groomer.sh
   in that script file is what file types get processed (or if not listed there,
   get ignored)
 * there are two ways pdf's can get handled -right now they have their text extracted
-  to the target device, the otherway copies it and extracts the text
+  to the target device, the other way copies it and extracts the text
 * the pdf text extraction isn't perfect and is the slowest part of it, but should
   be able to handle unicode stuff and currently doesn't do image extraction from
   pdf's but could do that too
@@ -53,11 +53,11 @@ Discussion
   nothing to sanitize any embedded links within those documents
 * for spreadsheets, if they are longer than a page, only a page worth from that
   sheet is exported right from the middle of the sheet (ie the top and bottom of
-  that sheet will get cut off and only the contents in teh middle exported to pdf)
+  that sheet will get cut off and only the contents in the middle exported to pdf)
   dumb but i figure if you want to go back to the source because it's interesting
-  enough on teh groomed side of it, then you can take the extra precautions
+  enough on the groomed side of it, then you can take the extra precautions
 * the groomed target only copies "safe" files, and does its best to convert any
-  potentiall unsafe files to a safer format
-* safe files being one that i know of that can't contain malicious embedded macros
+  potential unsafe files to a safer format
+* safe files being one that I know of that can't contain malicious embedded macros
   or other crap like that, and those than can get converted to something that wont
   contain code after conversion

NOTES-RPI2

@@ -8,5 +8,5 @@ Second: Top right
 Third: Bottom left
 Forth: Bottom right
 
-tl;rd: as long as the source key (sda) is connected to the top left port, the destination (sdb) can be connected on any other port.
+tl;dr: as long as the source key (sda) is connected to the top left port, the destination (sdb) can be connected on any other port.
 

TODO

@@ -2,7 +2,7 @@ TODO
 ====
 
 * the script locations should be changed in the next version so they don't sit
-   next to teh rPi's example development code that ships with teh stock rPi
+   next to the rPi's example development code that ships with the stock rPi
 * the system isn't optimised and should be : cleanup and making it as close to
   stock as possible
 [Npot sure] Starting process should be more obfuscated
@@ -15,9 +15,9 @@ TODO
 [done in HTML] convert documents (pdfs/*office/...) in images ?
 [Not Needed] Have a look at Ghostscript to work on PDFs (.pdf -> .eps -> .png?)
 [do everything as user] do not run the conversions as root -> run in chroot
-* take eth0 down in /etc/netowrk/interfaces or in the groomer script disable the
+* take eth0 down in /etc/network/interfaces or in the groomer script disable the
   interface before anything happens
-* hdmi should stay up: solveable by poking the power management timer
+* hdmi should stay up: solvable by poking the power management timer
   (better not to disable the PM completely)
 [Done] get rid of pdfbox. remove need for java
 [WIP] scripts to generate a SD card automatically (win/mac/linux)