docs(guide/Using $location), docs(guide/i18n and l10n): Format and grammar fixes.

docs/content/guide/$location.ngdoc

@@ -693,7 +693,7 @@ A path should always begin with forward slash (`/`); the `$location.path()` sett
 forward slash if it is missing.
 
 Note that the `!` prefix in the hashbang mode is not part of `$location.path()`; it is actually
-hashPrefix.
+`hashPrefix`.
 
 ## Crawling your app
 

docs/content/guide/i18n.ngdoc

@@ -305,7 +305,7 @@ matching is **case-sensitive**.
 
 #### Selection Keywords
 
-Selection keywords are simple words like "male" and "female".  The keyword, "other", and it's
+Selection keywords are simple words like "male" and "female".  The keyword, "other", and its
 corresponding message are required while others are optional.  It is used when the Angular
 expression does not match (case-insensitively) any of the other keywords specified.
 

docs/content/guide/security.ngdoc

@@ -39,7 +39,7 @@ In general, we recommend against this because it can create unintended XSS vecto
 
 However, it's ok to mix server-side templating in the bootstrap template (`index.html`) as long
 as user input cannot be used on the server to output html that would then be processed by Angular
-in a way that would cause allow for arbitrary code execution.
+in a way that would allow for arbitrary code execution.
 
 For instance, you can use server-side templating to dynamically generate CSS, URLs, etc, but not
 for generating templates that are bootstrapped/compiled by Angular.