Method Specific View Composer

When defining multiple view composers it is important to point out that you can be method/action specific.

responses.md

@@ -185,6 +185,7 @@ You may use the `composers` method to register a group of composers at the same
 	View::composers(array(
 		'AdminComposer' => array('admin.index', 'admin.profile'),
 		'UserComposer' => 'user',
+		'ProductComposer@create' => 'product' 
 	));
 
 > **Note:** There is no convention on where composer classes may be stored. You are free to store them anywhere as long as they can be autoloaded using the directives in your `composer.json` file.
@@ -231,4 +232,4 @@ The `macro` function accepts a name as its first argument, and a Closure as its
 
 	return Response::caps('foo');
 
-You may define your macros in one of your `app/start` files. Alternatively, you may organize your macros into a separate file which is included from one of your `start` files.
+You may define your macros in one of your `app/start` files. Alternatively, you may organize your macros into a separate file which is included from one of your `start` files.