Author: sseifert
Date: Fri Sep 18 13:38:24 2015
New Revision: 1703847

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

Modified:
    sling/site/trunk/content/documentation/development/sling-mock.mdtext

Modified: sling/site/trunk/content/documentation/development/sling-mock.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/sling-mock.mdtext?rev=1703847&r1=1703846&r2=1703847&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling-mock.mdtext 
(original)
+++ sling/site/trunk/content/documentation/development/sling-mock.mdtext Fri 
Sep 18 13:38:24 2015
@@ -138,7 +138,7 @@ Resource resolver types currently suppor
 
 **JCR_JACKRABBIT**
 
-* Uses a real JCR Jackrabbit implementation (not Oak) as provided by 
[sling/commons/testing][sling-comons-testing]
+* Uses a real JCR Jackrabbit implementation (not Oak) as provided by 
[sling/commons/testing][sling-commons-testing]
 * Full JCR/Sling features supported e.g. observations manager, transactions, 
versioning
 * Uses the productive [Sling JCR resource provider 
implementation][jcr-resource] internally to do the Resource-JCR mapping
 * Takes some seconds for startup on the first access 
@@ -176,9 +176,9 @@ This version is not yet released.
 
 _Remarks on the JCR_JACKRABBIT and JCR_OAK types:_
 
-* The repository is not cleared for each unit test, so make sure us use a 
unique node path for each unit test.
+* The repository is not cleared for each unit test, so make sure to use a 
unique node path for each unit test.
 * To import Sling content you have to fully register all node types required 
for the data
-* The [sling/commons/testing][sling-comons-testing] dependency introduces a 
lot of further dependencies from
+* The [sling/commons/testing][sling-commons-testing] dependency introduces a 
lot of further dependencies from
   jackrabbit and others, be careful that they do not conflict and are imported 
in the right order in your test project
 
 
@@ -388,5 +388,5 @@ If you use the `SlingContext` JUnit rule
 [jcr-mock]: {{ refs.jcr-mock.path }}
 [resourceresolver-mock]: {{ refs.resourceresolver-mock.path }}
 [jcr-resource]: 
http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource
-[sling-comons-testing]: 
http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing
+[sling-commons-testing]: 
http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/testing
 [mockito-testrunner]: 
http://mockito.github.io/mockito/docs/current/org/mockito/runners/MockitoJUnitRunner.html


Reply via email to