You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ju...@apache.org on 2015/04/21 15:30:35 UTC

svn commit: r1675116 - /sling/site/trunk/content/documentation/bundles/sling-query.mdtext

Author: justin
Date: Tue Apr 21 13:30:34 2015
New Revision: 1675116

URL: http://svn.apache.org/r1675116
Log:
minor wording tweaks

Modified:
    sling/site/trunk/content/documentation/bundles/sling-query.mdtext

Modified: sling/site/trunk/content/documentation/bundles/sling-query.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/sling-query.mdtext?rev=1675116&r1=1675115&r2=1675116&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/sling-query.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/sling-query.mdtext Tue Apr 21 13:30:34 2015
@@ -1,10 +1,10 @@
 Title: Sling Query
 
-SlingQuery is a Sling resource tree traversal tool inspired by the [jQuery](http://api.jquery.com/category/traversing/tree-traversal/).
+SlingQuery is a Sling resource tree traversal tool inspired by the [jQuery](http://api.jquery.com/category/traversing/tree-traversal/) JavaScript API.
 
 ## Introduction
 
-Recommended way to find resources in the Sling repository is using tree-traversal methods, like `listChildren()` and `getParent()` rather than JCR queries. The latter are great for listing resources with given properties, but we can't leverage the repository tree structure with such queries. On the other hand, using tree-traversal method is quite verbose. Consider following code that takes an resource and returns its first ancestor, being `cq:Page`, with given `jcr:content/cq:template` attribute:
+The recommended way to find resources in the Sling repository is using tree-traversal methods, like `listChildren()` and `getParent()` rather than JCR queries. The latter are great for listing resources with given properties, but we can't leverage the repository tree structure with such queries. On the other hand, using tree-traversal method is quite verbose. Consider following code that takes an resource and returns its first ancestor, being `cq:Page`, with given `jcr:content/cq:template` attribute:
 
     Resource resource = ...;
     while ((resource = resource.getParent()) != null) {