diff --git a/laravel/documentation/artisan/tasks.md b/laravel/documentation/artisan/tasks.md index a5ab78b6..4f2fb7de 100644 --- a/laravel/documentation/artisan/tasks.md +++ b/laravel/documentation/artisan/tasks.md @@ -10,7 +10,7 @@ ## Contents ## The Basics -Laravel's command-line tool is called Artisan. Artisan can be used to run "tasks" such as migrations, cronjobs, unit-tests, or anything that want. +Laravel's command-line tool is called Artisan. Artisan can be used to run "tasks" such as migrations, cronjobs, unit-tests, or anything that you want. ## Creating & Running Tasks @@ -23,7 +23,7 @@ #### Creating a task class: public function run($arguments) { - // Do awesome notifying... + // Do awesome notifying… } } @@ -42,7 +42,7 @@ #### Calling a task from your application: Command::run(array('notify')); -#### Calling a task from your application with arguements: +#### Calling a task from your application with arguments: Command::run(array('notify', 'taylor')); @@ -54,7 +54,7 @@ #### Adding a method to the task: 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 @@ #### Listen for a bundle's start event: 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 @@ ### Upgrading From 3.1.4 ## 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/command-line.md b/laravel/documentation/contrib/command-line.md index 5dea4cb6..0602c2e2 100644 --- a/laravel/documentation/contrib/command-line.md +++ b/laravel/documentation/contrib/command-line.md @@ -88,8 +88,8 @@ ## Committing # git commit -s -m "I added some more stuff to the Localization documentation." -"- **-s** means that you are signing-off on your commit with your name. This tells the Laravel team know that you personally agree to your code being added to the Laravel core. -"- **-m** is the message that goes with your commit. Provide a brief explanation of what you added or changed. +- **-s** means that you are signing-off on your commit with your name. This tells the Laravel team know that you personally agree to your code being added to the Laravel core. +- **-m** is the message that goes with your commit. Provide a brief explanation of what you added or changed. ## Pushing to your Fork 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 @@ ## Cloning Laravel 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 @@ ## Creating Branches 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 @@ ## Pushing to your Fork 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/controllers.md b/laravel/documentation/controllers.md index eb3e490a..7bece18b 100644 --- a/laravel/documentation/controllers.md +++ b/laravel/documentation/controllers.md @@ -140,7 +140,7 @@ #### Access the "index" action of the controller: ## Controller Layouts -Full documentation on using layouts with Controllers [can be found on the Templating page](http://laravel.com/docs/views/templating). +Full documentation on using layouts with Controllers [can be found on the Templating page](/docs/views/templating). ## RESTful Controllers 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 @@ ## Eager Loading 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 @@ #### Using a Closure to return a default value: #### 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 public static function validate(Location $location) { - // Validate the location instance... + // Validate the location instance… } } @@ -104,7 +104,7 @@ ### Repositories 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 @@ #### Determine if an attribute has an error message: 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 @@ ## Validation Walkthrough Route::post('register', function() { - $rules = array(...); + $rules = array(…); $validation = Validator::make(Input::all(), $rules); @@ -438,13 +438,13 @@ #### Registering a custom validation rule: 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/home.md b/laravel/documentation/views/home.md index 3daf57a9..97e9e19f 100644 --- a/laravel/documentation/views/home.md +++ b/laravel/documentation/views/home.md @@ -184,7 +184,7 @@ #### Register a composer that handles multiple views: ## Redirects -It's important to note that both routes and controllers require responses to be returned with the 'return' directive. Instead of calling "Redirect::to()"" where you'd like to redirect the user. You'd instead use "return Redirect::to()". This distinction is important as it's different than most other PHP frameworks and it could be easy to accidentally overlook the importance of this practice. +It's important to note that both routes and controllers require responses to be returned with the 'return' directive. Instead of calling "Redirect::to()" where you'd like to redirect the user. You'd instead use "return Redirect::to()". This distinction is important as it's different than most other PHP frameworks and it could be easy to accidentally overlook the importance of this practice. #### Redirecting to another URI: 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 @@ #### Generate the pagination links: 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 @@ ## Pagination Styling
  • 1
  • 2
    • -
  • ...
    • +
  • …
  • 11
  • 12
    • @@ -96,7 +96,7 @@ ## Pagination Styling
  • 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 @@ #### Unless Statement: Login @endunless - // Equivalent to... + // Equivalent to… Login