From 6add7edfcae6999f3c52365b295d527ceb6192e6 Mon Sep 17 00:00:00 2001 From: janhartigan Date: Sun, 2 Feb 2014 13:55:09 -0800 Subject: [PATCH] small typo in readme --- readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.md b/readme.md index eeb0fbe..5902d85 100644 --- a/readme.md +++ b/readme.md @@ -58,7 +58,7 @@ Two important default behaviors of Authority to keep in mind ## Basic usage -Authority is intented to be instantiated once per application (though supports multiple instances). It works well with an IoC (Inversion of Control) container that supports singleton access, like [Laravel's IoC](https://github.com/illuminate/container), or by using standard dependency injection. You may assign rules prior to your app authorizing resources, or add at any time. +Authority is intended to be instantiated once per application (though supports multiple instances). It works well with an IoC (Inversion of Control) container that supports singleton access, like [Laravel's IoC](https://github.com/illuminate/container), or by using standard dependency injection. You may assign rules prior to your app authorizing resources, or add at any time. The Authority constructor requires at least one argument - the object that represents the current user. We'll cover the second optional argument later.