shiro-site git commit: Fix getSubject() method link

[bd...@apache.org]

Repository: shiro-site
Updated Branches:
  refs/heads/master 5ad50a997 -> dbc2d91e1


Fix getSubject() method link

Fixes: #24


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

Branch: refs/heads/master
Commit: dbc2d91e181bdc0b7122c157cd9476ac44a9b7b4
Parents: 5ad50a9
Author: Ian Reardon <ia...@gmail.com>
Authored: Mon Jun 26 20:59:27 2017 -0400
Committer: Brian Demers <bd...@apache.org>
Committed: Wed Jul 5 11:30:28 2017 -0400

----------------------------------------------------------------------
 10-minute-tutorial.md.vtl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/shiro-site/blob/dbc2d91e/10-minute-tutorial.md.vtl
----------------------------------------------------------------------
diff --git a/10-minute-tutorial.md.vtl b/10-minute-tutorial.md.vtl
index e23b57b..202ef71 100644
--- a/10-minute-tutorial.md.vtl
+++ b/10-minute-tutorial.md.vtl
@@ -77,7 +77,7 @@ In almost all environments, you can obtain the currently executing user via the
 Subject currentUser = SecurityUtils.getSubject();
 ```
 
-Using [`SecurityUtils`](static/current/apidocs/org/apache/shiro/SecurityUtils.html).[getSubject()](static/current/apidocs/org/apache/shiro/SecurityUtils.html#getSubject()), we can obtain the currently executing [`Subject`](static/current/apidocs/org/apache/shiro/subject/Subject.html). A _Subject_ is just a security-specific "view" of an application User. We actually wanted to call it 'User' since that "just makes sense", but we decided against it: too many applications have existing APIs that already have their own User classes/frameworks, and we didn't want to conflict with those. Also, in the security world, the term `Subject` is actually the recognized nomenclature. Ok, moving on...
+Using [`SecurityUtils`](static/current/apidocs/org/apache/shiro/SecurityUtils.html).[`getSubject()`](static/current/apidocs/org/apache/shiro/SecurityUtils.html#getSubject--), we can obtain the currently executing [`Subject`](static/current/apidocs/org/apache/shiro/subject/Subject.html). A _Subject_ is just a security-specific "view" of an application User. We actually wanted to call it 'User' since that "just makes sense", but we decided against it: too many applications have existing APIs that already have their own User classes/frameworks, and we didn't want to conflict with those. Also, in the security world, the term `Subject` is actually the recognized nomenclature. Ok, moving on...
 
 The `getSubject()` call in a standalone application might return a `Subject` based on user data in an application-specific location, and in a server environment (e.g. web app), it acquires the `Subject` based on user data associated with current thread or incoming request.