Author: kwin
Date: Thu Sep 22 12:10:40 2016
New Revision: 1761920

URL: http://svn.apache.org/viewvc?rev=1761920&view=rev
Log:
fix link

Modified:
    
sling/site/trunk/content/documentation/the-sling-engine/url-to-script-resolution.mdtext

Modified: 
sling/site/trunk/content/documentation/the-sling-engine/url-to-script-resolution.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/url-to-script-resolution.mdtext?rev=1761920&r1=1761919&r2=1761920&view=diff
==============================================================================
--- 
sling/site/trunk/content/documentation/the-sling-engine/url-to-script-resolution.mdtext
 (original)
+++ 
sling/site/trunk/content/documentation/the-sling-engine/url-to-script-resolution.mdtext
 Thu Sep 22 12:10:40 2016
@@ -8,7 +8,7 @@ See also [Servlets and Scripts]({{ refs.
 
 First of all Sling looks up the resource identified by the URL - typically a 
path inside the JCR repository, which is annotated by the `sling:resourceType` 
property 
 which defines the resource type of that resource. Using this resource type 
(which is kind of a relative path, 
-eg. "myblog/comment"), scripts or servlets are looked up. For more details 
about how the initial resource is identified for a specific request URL look at 
[URL decomposition] ({{refs.url-decomposition.path}}).
+eg. "myblog/comment"), scripts or servlets are looked up. For more details 
about how the initial resource is identified for a specific request URL look at 
[URL decomposition]({{refs.url-decomposition.path}}).
 
 Scripts and servlets are itself resources in Sling and thus have a resource 
path: this is either the location in the 
 JCR repository, the resource type in a servlet component configuration or the 
"virtual" bundle resource path 


Reply via email to