Merge pull request #1584 from bpierre/bug/doc-fixes

Documentation fixes

laravel/documentation/artisan/tasks.md

@@ -10,7 +10,7 @@
 <a name="the-basics"></a>
 ## 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.
 
 <a name="creating-tasks"></a>
 ## Creating & Running Tasks
@@ -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…
 		}
 
 	}
@@ -42,7 +42,7 @@ Now you can call the "run" method of your task via the command-line. You can eve
 
 	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 @@ 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)

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.

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.
 
 <a name="upgrade-3.1.4"></a>
 ### Upgrading From 3.1.3

laravel/documentation/contrib/command-line.md

@@ -88,8 +88,8 @@ Next, commit the changes to the repository:
 
 	# 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.
 
 <a name="pushing-to-your-fork"></a>
 ## Pushing to your Fork

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

laravel/documentation/controllers.md

@@ -140,7 +140,7 @@ Define the controller class and store it in **controllers/admin/panel.php**.
 <a name="controller-layouts"></a>
 ## 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).
 
 <a name="restful-controllers"></a>
 ## RESTful Controllers

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.
 

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.
 

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…
 		}
 
 	}

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)
 	{

laravel/documentation/views/home.md

@@ -184,7 +184,7 @@ Now each time the "home" view is created, an instance of the View will be passed
 <a name="redirects"></a>
 ## 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:
 

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
 			<li><a href="foo">1</a></li>
 			<li><a href="foo">2</a></li>
 
-			<li class="dots disabled"><a href="#">...</a></li>
+			<li class="dots disabled"><a href="#">…</a></li>
 
 			<li><a href="foo">11</a></li>
 			<li><a href="foo">12</a></li>
@@ -96,7 +96,7 @@ All pagination link elements can be style using CSS classes. Here is an example
 			<li><a href="foo">14</a></li>
 			<li><a href="foo">15</a></li>
 
-			<li class="dots disabled"><a href="#">...</a></li>
+			<li class="dots disabled"><a href="#">…</a></li>
 
 			<li><a href="foo">25</a></li>
 			<li><a href="foo">26</a></li>

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…
 
 	<?php if ( ! Auth::check()): ?>
 		Login