svn commit: r1795449 - /sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.mdtext

[ss...@apache.org]

Author: sseifert
Date: Wed May 17 20:01:18 2017
New Revision: 1795449

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

Modified:
    sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.mdtext

Modified: sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.mdtext?rev=1795449&r1=1795448&r2=1795449&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/context-aware-configuration/context-aware-configuration-default-implementation.mdtext Wed May 17 20:01:18 2017
@@ -38,6 +38,7 @@ If you get the context-aware configurati
 7. `/libs/conf` - because it is configured as fallback path
 
 So the basic rules are:
+
 * Go up in the content resource tree until a resource with `sling:configRef` is found. This is the 'inner-most' context. Check if a configuration resource exists at the path the property points to.
 * Check for parent resources of the references configuration resource (below `/conf`)
 * Go further up in the content resource tree for parent contexts, and check their configuration resources as well (they may reference completely different location below `/conf`)