Incorporated ThiefMaster's suggestions for docs

docs/errorhandling.rst

@@ -33,13 +33,13 @@ Error Logging Tools
 
 Sending error mails, even if just for critical ones, can become
 overwhelming if enough users are hitting the error and log files are
-typically never looked at. This is why we're recommending using
+typically never looked at. This is why we recommend using `Sentry
-`Sentry <http://www.getsentry.com/>`_ for dealing with application errors.
+<http://www.getsentry.com/>`_ for dealing with application errors.  It's
-It's available as an Open Source project `on GitHub
+available as an Open Source project `on GitHub
-<github.com/getsentry/sentry>`__ and is also available as `Hosted Version
+<github.com/getsentry/sentry>`__ and is also available as a `hosted version
 <https://getsentry.com/signup/>`_ which you can try for free. Sentry
-aggregates duplicate erorrs, captures the full stack trace and local
+aggregates duplicate errors, captures the full stack trace and local
-variables for debugging, and send you mails based on new errors or
+variables for debugging, and sends you mails based on new errors or
 frequency thresholds.
 
 To use Sentry you need to install the `raven` client::