+1 -1

externals/mimemailparser/attachment.class.php

reviewed

··· 102 102 103 103 /** 104 104 * Retrieve the file content in one go 105 105 - * Once you retreive the content you cannot use MimeMailParser_attachment::read() 105 105 + * Once you retrieve the content you cannot use MimeMailParser_attachment::read() 106 106 * @return String 107 107 */ 108 108 public function getContent() {

+1 -1

src/applications/repository/graphcache/PhabricatorRepositoryGraphCache.php

reviewed

··· 276 276 277 277 278 278 /** 279 279 - * Rebuild a cache bucket, amending existing data if avialable. 279 279 + * Rebuild a cache bucket, amending existing data if available. 280 280 * 281 281 * @param int Bucket key, from @{method:getBucketKey}. 282 282 * @param array Existing bucket data.

+2 -2

src/docs/contributor/database.diviner

reviewed

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

+1 -1

src/docs/user/userguide/arcanist_lint_script_and_regex.diviner

reviewed

··· 96 96 not present in the output. If no severity capturing group is present, 97 97 messages are raised with "error" severity. If multiple severity capturing 98 98 groups are present, messages are raised with the highest captured 99 99 - serverity. Capturing groups like `error` supersede the `severity` 99 99 + severity. Capturing groups like `error` supersede the `severity` 100 100 capturing group. 101 101 - `error` (optional) Match some nonempty substring to indicate that this 102 102 message has "error" severity.

+1 -1

src/infrastructure/query/policy/PhabricatorPolicyAwareQuery.php

reviewed

··· 416 416 * searches both the current query's workspace and the workspaces of parent 417 417 * queries. 418 418 * 419 419 - * @param list<phid> List of PHIDs to retreive. 419 419 + * @param list<phid> List of PHIDs to retrieve. 420 420 * @return this 421 421 * @task workspace 422 422 */

+1 -1

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

reviewed

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

+1 -1

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

reviewed

··· 35 35 } 36 36 37 37 // When the user changes the selected search engine, update the query 38 38 - // control to show avialable queries for that engine. 38 38 + // control to show available queries for that engine. 39 39 function update() { 40 40 var app = app_control.value; 41 41