SLING-9422 - Content Package Installer: Use service resource resolvers instead of admin resource resolver for installation
Alternative code highlighting syntax
diff --git a/src/main/jbake/content/documentation/bundles/content-package-installer-factory.md b/src/main/jbake/content/documentation/bundles/content-package-installer-factory.md
index 3bc4076..2251c06 100644
--- a/src/main/jbake/content/documentation/bundles/content-package-installer-factory.md
+++ b/src/main/jbake/content/documentation/bundles/content-package-installer-factory.md
@@ -14,25 +14,25 @@
As of version 1.0.4 the bundle requires a service user mapping to function correctly. An example mapping, using the provisioning model is
-```
- org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-installer-factories
- user.mapping=[
- "org.apache.sling.installer.factory.packages\=sling-package-install"
- ]
-```
+
+ org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-installer-factories
+ user.mapping=[
+ "org.apache.sling.installer.factory.packages\=sling-package-install"
+ ]
+
The service user requires needs access to all locations which are covered by packages and to `/etc/packages` itself.
A sample user configuration using repoinit is
-```
-create service user sling-package-install
-set ACL for sling-package-install
- allow jcr:all on /
- allow jcr:namespaceManagement,jcr:nodeTypeDefinitionManagement on :repository
-end
-```
+ create service user sling-package-install
+
+ set ACL for sling-package-install
+ allow jcr:all on /
+ allow jcr:namespaceManagement,jcr:nodeTypeDefinitionManagement on :repository
+ end
+
# Project Info
