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

[bd...@apache.org]

Author: bdelacretaz
Date: Fri May 17 08:53:34 2013
New Revision: 1483695

URL: http://svn.apache.org/r1483695
Log:
link to servlets and scripts

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=1483695&r1=1483694&r2=1483695&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 Fri May 17 08:53:34 2013
@@ -2,7 +2,11 @@ Title: URL to Script Resolution
 
 [TOC]
 
-This page explains how Sling maps URLs to a script or and servlet. First of all Sling looks up the resource identified 
+This page explains how Sling maps URLs to a script or and servlet. 
+
+See also [Servlets and Scripts]({{ refs.servlets.path }}) which provides detailed info about how to register servlets.
+
+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.