Fix various spelling mistakes

Summary: Minor change, self-explanatory.

Test Plan: Eye-ball it

Reviewers: epriestley, #blessed_reviewers

Reviewed By: epriestley, #blessed_reviewers

Subscribers: epriestley, Korvin

Differential Revision: https://secure.phabricator.com/D9911

Author: joshuaspence

externals/mimemailparser/attachment.class.php

@@ -102,7 +102,7 @@ public function read($bytes = 2082) {
 
 	/**
 	 * Retrieve the file content in one go
-	 * Once you retreive the content you cannot use MimeMailParser_attachment::read()
+	 * Once you retrieve the content you cannot use MimeMailParser_attachment::read()
 	 * @return String
 	 */
 	public function getContent() {

src/applications/repository/graphcache/PhabricatorRepositoryGraphCache.php

@@ -276,7 +276,7 @@ private function getBucketData($bucket_key, $rebuild_data = null) {
 
 
   /**
-   * Rebuild a cache bucket, amending existing data if avialable.
+   * Rebuild a cache bucket, amending existing data if available.
    *
    * @param   int     Bucket key, from @{method:getBucketKey}.
    * @param   array   Existing bucket data.

src/docs/contributor/database.diviner

@@ -115,7 +115,7 @@ We use both autoincrementing IDs and global PHIDs because each is useful in
 different contexts. Autoincrementing IDs are chronologically ordered and allow
 us to construct short, human-readable object names (like D2258) and URIs. Global
 PHIDs allow us to represent relationships between different types of objects in
-a homogenous way.
+a homogeneous way.
 
 For example, the concept of "subscribers" is more powerfully done with PHIDs
 because we could theoretically have users, projects, teams, and more all as
@@ -148,7 +148,7 @@ to avoid it if possible.
 There are three simple steps to update the schema:
 
 # Create a `.sql` file in `resources/sql/patches/`. This file should:
-  - Contain the approprate MySQL commands to update the schema.
+  - Contain the appropriate MySQL commands to update the schema.
   - Be named as `YYYYMMDD.patchname.ext`. For example, `20130217.example.sql`.
   - Use `${NAMESPACE}` rather than `phabricator` for database names.
   - Use `COLLATE utf8_bin` for any columns that are to be used as identifiers,

src/docs/user/userguide/arcanist_lint_script_and_regex.diviner

@@ -96,7 +96,7 @@ The regex should capture these named patterns with `(?P<name>...)`:
     not present in the output. If no severity capturing group is present,
     messages are raised with "error" severity. If multiple severity capturing
     groups are present, messages are raised with the highest captured
-    serverity. Capturing groups like `error` supersede the `severity`
+    severity. Capturing groups like `error` supersede the `severity`
     capturing group.
   - `error` (optional) Match some nonempty substring to indicate that this
     message has "error" severity.

src/infrastructure/query/policy/PhabricatorPolicyAwareQuery.php

@@ -416,7 +416,7 @@ public function putObjectsInWorkspace(array $objects) {
    * searches both the current query's workspace and the workspaces of parent
    * queries.
    *
-   * @param list<phid> List of PHIDs to retreive.
+   * @param list<phid> List of PHIDs to retrieve.
    * @return this
    * @task workspace
    */

webroot/rsrc/externals/javelin/lib/control/typeahead/source/TypeaheadSource.js

@@ -25,7 +25,7 @@ JX.install('TypeaheadSource', {
      * the server. The purpose of normalization is to strip out irrelevant data,
      * like uppercase/lowercase, extra spaces, or punctuation. By default,
      * the @{JX.TypeaheadNormalizer} is used to normalize strings, but you may
-     * want to provide a different normalizer, particiularly if there are
+     * want to provide a different normalizer, particularly if there are
      * special characters with semantic meaning in your object names.
      *
      * @param function

webroot/rsrc/js/application/dashboard/behavior-dashboard-query-panel-select.js

@@ -35,7 +35,7 @@ JX.behavior('dashboard-query-panel-select', function(config) {
   }
 
   // When the user changes the selected search engine, update the query
-  // control to show avialable queries for that engine.
+  // control to show available queries for that engine.
   function update() {
     var app = app_control.value;