1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-11-22 14:52:41 +01:00

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
This commit is contained in:
Joshua Spence 2014-07-13 00:45:33 +10:00
parent ae263ddde5
commit e495ce496b
7 changed files with 8 additions and 8 deletions

View file

@ -102,7 +102,7 @@ class MimeMailParser_attachment {
/** /**
* Retrieve the file content in one go * 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 * @return String
*/ */
public function getContent() { public function getContent() {

View file

@ -276,7 +276,7 @@ final class PhabricatorRepositoryGraphCache {
/** /**
* 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 int Bucket key, from @{method:getBucketKey}.
* @param array Existing bucket data. * @param array Existing bucket data.

View file

@ -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 different contexts. Autoincrementing IDs are chronologically ordered and allow
us to construct short, human-readable object names (like D2258) and URIs. Global 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 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 For example, the concept of "subscribers" is more powerfully done with PHIDs
because we could theoretically have users, projects, teams, and more all as 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: There are three simple steps to update the schema:
# Create a `.sql` file in `resources/sql/patches/`. This file should: # 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`. - Be named as `YYYYMMDD.patchname.ext`. For example, `20130217.example.sql`.
- Use `${NAMESPACE}` rather than `phabricator` for database names. - Use `${NAMESPACE}` rather than `phabricator` for database names.
- Use `COLLATE utf8_bin` for any columns that are to be used as identifiers, - Use `COLLATE utf8_bin` for any columns that are to be used as identifiers,

View file

@ -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, not present in the output. If no severity capturing group is present,
messages are raised with "error" severity. If multiple severity capturing messages are raised with "error" severity. If multiple severity capturing
groups are present, messages are raised with the highest captured 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. capturing group.
- `error` (optional) Match some nonempty substring to indicate that this - `error` (optional) Match some nonempty substring to indicate that this
message has "error" severity. message has "error" severity.

View file

@ -416,7 +416,7 @@ abstract class PhabricatorPolicyAwareQuery extends PhabricatorOffsetPagedQuery {
* searches both the current query's workspace and the workspaces of parent * searches both the current query's workspace and the workspaces of parent
* queries. * queries.
* *
* @param list<phid> List of PHIDs to retreive. * @param list<phid> List of PHIDs to retrieve.
* @return this * @return this
* @task workspace * @task workspace
*/ */

View file

@ -25,7 +25,7 @@ JX.install('TypeaheadSource', {
* the server. The purpose of normalization is to strip out irrelevant data, * the server. The purpose of normalization is to strip out irrelevant data,
* like uppercase/lowercase, extra spaces, or punctuation. By default, * like uppercase/lowercase, extra spaces, or punctuation. By default,
* the @{JX.TypeaheadNormalizer} is used to normalize strings, but you may * 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. * special characters with semantic meaning in your object names.
* *
* @param function * @param function

View file

@ -35,7 +35,7 @@ JX.behavior('dashboard-query-panel-select', function(config) {
} }
// When the user changes the selected search engine, update the query // 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() { function update() {
var app = app_control.value; var app = app_control.value;