You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shiro.apache.org by bd...@apache.org on 2017/06/22 20:11:14 UTC

[02/12] shiro-site git commit: Couple of typos in permissions.md

Couple of typos in permissions.md

Fixes: #14


Project: http://git-wip-us.apache.org/repos/asf/shiro-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/shiro-site/commit/2ec6c29f
Tree: http://git-wip-us.apache.org/repos/asf/shiro-site/tree/2ec6c29f
Diff: http://git-wip-us.apache.org/repos/asf/shiro-site/diff/2ec6c29f

Branch: refs/heads/master
Commit: 2ec6c29fffb0e60a6cc164f4b9caed67c87c368f
Parents: 54d249c
Author: Anton von Borries <an...@live.de>
Authored: Thu Mar 2 10:58:50 2017 +0000
Committer: Brian Demers <bd...@apache.org>
Committed: Thu Jun 22 15:44:36 2017 -0400

----------------------------------------------------------------------
 permissions.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/shiro-site/blob/2ec6c29f/permissions.md
----------------------------------------------------------------------
diff --git a/permissions.md b/permissions.md
index cb8fe98..ed8071c 100644
--- a/permissions.md
+++ b/permissions.md
@@ -27,9 +27,9 @@ So to enable easy-to-process yet still readable permission statements, Shiro pro
 <a name="Permissions-SimpleUsage"></a>
 ###Simple Usage
 
-Let's you want to protect access to your company's printers such that some people can print to particular printers, while others can query what jobs are currently in the queue.
+Let's say you want to protect access to your company's printers such that some people can print to particular printers, while others can query what jobs are currently in the queue.
 
-An extremely simple approach would be to use grant the user a "queryPrinter" permission. Then you could check to see if the user has the queryPrinter permission by calling:
+An extremely simple approach would be to grant the user a "queryPrinter" permission. Then you could check to see if the user has the queryPrinter permission by calling:
 
 ``` java
 subject.isPermitted("queryPrinter")