svn commit: r1888208 - /jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md

[mi...@apache.org]

Author: miroslav
Date: Tue Mar 30 12:21:10 2021
New Revision: 1888208

URL: http://svn.apache.org/viewvc?rev=1888208&view=rev
Log:
OAK-9332 typo in the comments

Modified:
    jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md

Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md?rev=1888208&r1=1888207&r2=1888208&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md Tue Mar 30 12:21:10 2021
@@ -99,7 +99,7 @@ when receiving an `InterruptedException`
 
 As explained in [Understanding the node state model](https://jackrabbit.apache.org/oak/docs/architecture/nodestate.html), Oak stores content in a tree hierarchy. 
 Considering that, when traversing the path to access parent or child nodes, even though being equivalent operations, 
-it is preferable to use JCR Node API instead of Session API. The reason being is that session API uses an absolute path, 
+it is preferable to use JCR Node API instead of Session API. The reason behind is that session API uses an absolute path, 
 and to get to the desired parent or child node, all ancestor nodes will have to be traversed before reaching the target node. 
 Traversal for each ancestor node includes building the node state and associating it with 
 TreePermission (check [Permission Evaluation in Detail](https://jackrabbit.apache.org/oak/docs/security/permission/evaluation.html)),