edit readme

Author: freekmurze

CHANGELOG.md

@@ -2,6 +2,9 @@
 
 All notable changes to `laravel-permission` will be documented in this file
 
+## 2.6.0 - 2017-09-10
+- add `permission` scope
+
 ## 2.5.4 - 2017-09-07
 - register the blade directives in the register method of the service provider
 

README.md

@@ -225,15 +225,21 @@ $permissions = $user->getAllPermissions();
 $roles = $user->getRoleNames(); // Returns a collection
 ```
 
-The `HasRoles` trait also adds a scope to your models to scope the query to certain roles or permissions:
+The `HasRoles` trait also add a `role` scopes to your models to scope the query to certain roles or permissions:
 
 ```php
 $users = User::role('writer')->get(); // Returns only users with the role 'writer'
+```
+
+The `role` scope can accept a string, a `\Spatie\Permission\Models\Role` object or an `\Illuminate\Support\Collection` object.
 
+The same trait also adds a scope to only get users that have a certain permission.
+
+```php
 $users = User::permission('edit articles')->get(); // Returns only users with the permission 'edit articles' (inherited or directly)
 ```
 
-The scope can accept a string, a `\Spatie\Permission\Models\Role` object or an `\Illuminate\Support\Collection` object.
+The scope can accept a string, a `\Spatie\Permission\Models\Permission` object or an `\Illuminate\Support\Collection` object.
 
 ### Using "direct" permissions (see below to use both roles and permissions)