From a1facced9a7df2b887af7daca551f7cb46e825a7 Mon Sep 17 00:00:00 2001 From: Pierre Bertet Date: Tue, 8 Jan 2013 17:10:38 +0100 Subject: [PATCH] Documentation typography: ellipses Signed-off-by: Pierre Bertet --- laravel/documentation/artisan/tasks.md | 4 ++-- laravel/documentation/bundles.md | 2 +- laravel/documentation/changes.md | 2 +- laravel/documentation/contrib/tortoisegit.md | 6 +++--- laravel/documentation/database/eloquent.md | 2 +- laravel/documentation/input.md | 2 +- laravel/documentation/models.md | 4 ++-- laravel/documentation/validation.md | 8 ++++---- laravel/documentation/views/pagination.md | 6 +++--- laravel/documentation/views/templating.md | 2 +- 10 files changed, 19 insertions(+), 19 deletions(-) diff --git a/laravel/documentation/artisan/tasks.md b/laravel/documentation/artisan/tasks.md index a5ab78b6..761c6414 100644 --- a/laravel/documentation/artisan/tasks.md +++ b/laravel/documentation/artisan/tasks.md @@ -23,7 +23,7 @@ To create a task create a new class in your **application/tasks** directory. The public function run($arguments) { - // Do awesome notifying... + // Do awesome notifying… } } @@ -54,7 +54,7 @@ Remember, you can call specific methods on your task, so, let's add an "urgent" public function run($arguments) { - // Do awesome notifying... + // Do awesome notifying… } public function urgent($arguments) diff --git a/laravel/documentation/bundles.md b/laravel/documentation/bundles.md index 674deb25..ae9ff72a 100644 --- a/laravel/documentation/bundles.md +++ b/laravel/documentation/bundles.md @@ -116,7 +116,7 @@ Each time a bundle is started, it fires an event. You can listen for the startin Event::listen('laravel.started: admin', function() { - // The "admin" bundle has started... + // The "admin" bundle has started… }); It is also possible to "disable" a bundle so that it will never be started. diff --git a/laravel/documentation/changes.md b/laravel/documentation/changes.md index 7cc76b9b..03e65647 100644 --- a/laravel/documentation/changes.md +++ b/laravel/documentation/changes.md @@ -315,7 +315,7 @@ Add the following code above `Blade::sharpen()` in `application/start.php`.. ## Laravel 3.1.4 - Fixes Response header casing bug. -- Fixes SQL "where in" (...) short-cut bug. +- Fixes SQL "where in" (…) short-cut bug. ### Upgrading From 3.1.3 diff --git a/laravel/documentation/contrib/tortoisegit.md b/laravel/documentation/contrib/tortoisegit.md index 74049ead..96f1d9b9 100644 --- a/laravel/documentation/contrib/tortoisegit.md +++ b/laravel/documentation/contrib/tortoisegit.md @@ -28,7 +28,7 @@ Login to GitHub and visit the [Laravel Repository](https://github.com/laravel/la Open up Windows Explorer and create a new directory where you can make development changes to Laravel. -- Right-click the Laravel directory to bring up the context menu. Click on **Git Clone...** +- Right-click the Laravel directory to bring up the context menu. Click on **Git Clone…** - Git clone - **Url:** https://github.com/laravel/laravel.git - **Directory:** the directory that you just created in the previous step @@ -73,7 +73,7 @@ Now that you have created your own branch and have switched to it, it's time to Now that you have finished coding and testing your changes, it's time to commit them to your local repository: -- Right-click the Laravel directory and goto **Git Commit -> "feature/localization-docs"...** +- Right-click the Laravel directory and goto **Git Commit -> "feature/localization-docs"…** - Commit - **Message:** Provide a brief explaination of what you added or changed - Click **Sign** - This tells the Laravel team know that you personally agree to your code being added to the Laravel core @@ -85,7 +85,7 @@ Now that you have finished coding and testing your changes, it's time to commit Now that your local repository has your committed changes, it's time to push (or sync) your new branch to your fork that is hosted in GitHub: -- Right-click the Laravel directory and goto **Git Sync...** +- Right-click the Laravel directory and goto **Git Sync…** - Git Syncronization - **Local Branch:** feature/localization-docs - **Remote Branch:** leave this blank diff --git a/laravel/documentation/database/eloquent.md b/laravel/documentation/database/eloquent.md index b2178635..d38ed380 100644 --- a/laravel/documentation/database/eloquent.md +++ b/laravel/documentation/database/eloquent.md @@ -425,7 +425,7 @@ In this example, **only two queries will be executed**! SELECT * FROM "books" - SELECT * FROM "authors" WHERE "id" IN (1, 2, 3, 4, 5, ...) + SELECT * FROM "authors" WHERE "id" IN (1, 2, 3, 4, 5, …) Obviously, wise use of eager loading can dramatically increase the performance of your application. In the example above, eager loading cut the execution time in half. diff --git a/laravel/documentation/input.md b/laravel/documentation/input.md index f1429ac3..a4002c41 100644 --- a/laravel/documentation/input.md +++ b/laravel/documentation/input.md @@ -41,7 +41,7 @@ By default, *null* will be returned if the input item does not exist. However, y #### Determining if the input contains a given item: - if (Input::has('name')) ... + if (Input::has('name')) … > **Note:** The "has" method will return *false* if the input item is an empty string. diff --git a/laravel/documentation/models.md b/laravel/documentation/models.md index a1f4620c..3218dc2c 100644 --- a/laravel/documentation/models.md +++ b/laravel/documentation/models.md @@ -85,7 +85,7 @@ Services contain the *processes* of your application. So, let's keep using our T public static function validate(Location $location) { - // Validate the location instance... + // Validate the location instance… } } @@ -104,7 +104,7 @@ Repositories are the data access layer of your application. They are responsible public function save(Location $location, $user_id) { - // Store the location for the given user ID... + // Store the location for the given user ID… } } diff --git a/laravel/documentation/validation.md b/laravel/documentation/validation.md index 06feb707..aad4150e 100644 --- a/laravel/documentation/validation.md +++ b/laravel/documentation/validation.md @@ -286,7 +286,7 @@ Laravel makes working with your error messages a cinch using a simple error coll if ($validation->errors->has('email')) { - // The e-mail attribute has errors... + // The e-mail attribute has errors… } #### Retrieve the first error message for an attribute: @@ -327,7 +327,7 @@ Once you have performed your validation, you need an easy way to get the errors Route::post('register', function() { - $rules = array(...); + $rules = array(…); $validation = Validator::make(Input::all(), $rules); @@ -438,13 +438,13 @@ Or by adding an entry for your rule in the **language/en/validation.php** file: As mentioned above, you may even specify and receive a list of parameters in your custom rule: - // When building your rules array... + // When building your rules array… $rules = array( 'username' => 'required|awesome:yes', ); - // In your custom rule... + // In your custom rule… Validator::register('awesome', function($attribute, $value, $parameters) { diff --git a/laravel/documentation/views/pagination.md b/laravel/documentation/views/pagination.md index 081a6f60..867bd85b 100644 --- a/laravel/documentation/views/pagination.md +++ b/laravel/documentation/views/pagination.md @@ -38,7 +38,7 @@ You can also pass an optional array of table columns to select in the query: The links method will create an intelligent, sliding list of page links that looks something like this: - Previous 1 2 ... 24 25 26 27 28 29 30 ... 78 79 Next + Previous 1 2 … 24 25 26 27 28 29 30 … 78 79 Next The Paginator will automatically determine which page you're on and update the results and links accordingly. @@ -86,7 +86,7 @@ All pagination link elements can be style using CSS classes. Here is an example
  • 1
  • 2
    • -
  • ...
    • +
  • …
  • 11
  • 12
    • @@ -96,7 +96,7 @@ All pagination link elements can be style using CSS classes. Here is an example
  • 14
  • 15
    • -
  • ...
    • +
  • …
  • 25
  • 26
    • diff --git a/laravel/documentation/views/templating.md b/laravel/documentation/views/templating.md index 9e99e5d4..0e04430a 100644 --- a/laravel/documentation/views/templating.md +++ b/laravel/documentation/views/templating.md @@ -152,7 +152,7 @@ Similarly, you can use **@render**, which behaves the same as **@include** excep Login @endunless - // Equivalent to... + // Equivalent to… Login