Commit 6d37a324 authored by Taylor Otwell's avatar Taylor Otwell

Cleaning up the routes file.

parent 223c3a7d
...@@ -6,9 +6,8 @@ ...@@ -6,9 +6,8 @@
|-------------------------------------------------------------------------- |--------------------------------------------------------------------------
| |
| Simply tell Laravel the HTTP verbs and URIs it should respond to. It is a | Simply tell Laravel the HTTP verbs and URIs it should respond to. It is a
| breeze to setup your applications using Laravel's RESTful routing, and it | breeze to setup your application using Laravel's RESTful routing and it
| is perfectly suited for building both large applications and simple APIs. | is perfectly suited for building large applications and simple APIs.
| Enjoy the fresh air and simplicity of the framework.
| |
| Let's respond to a simple GET request to http://example.com/hello: | Let's respond to a simple GET request to http://example.com/hello:
| |
...@@ -69,9 +68,9 @@ Event::listen('500', function() ...@@ -69,9 +68,9 @@ Event::listen('500', function()
|-------------------------------------------------------------------------- |--------------------------------------------------------------------------
| |
| Filters provide a convenient method for attaching functionality to your | Filters provide a convenient method for attaching functionality to your
| routes. The built-in "before" and "after" filters are called before and | routes. The built-in before and after filters are called before and
| after every request to your application, and you may even create other | after every request to your application, and you may even create
| filters that can be attached to individual routes. | other filters that can be attached to individual routes.
| |
| Let's walk through an example... | Let's walk through an example...
| |
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment