releng: Improve description of uninstallation
diff --git a/src/main/java/org/apache/sling/maven/bundlesupport/BundleUninstallMojo.java b/src/main/java/org/apache/sling/maven/bundlesupport/BundleUninstallMojo.java
index e27ccbc..3d17b05 100644
--- a/src/main/java/org/apache/sling/maven/bundlesupport/BundleUninstallMojo.java
+++ b/src/main/java/org/apache/sling/maven/bundlesupport/BundleUninstallMojo.java
@@ -33,11 +33,7 @@
/**
* Uninstall an OSGi bundle from a running Sling instance.
*
- * The plugin places by default an HTTP POST request to <a href="http://felix.apache.org/documentation/subprojects/apache-felix-web-console/web-console-restful-api.html#post-requests">
- * Felix Web Console</a> to uninstall the bundle.
- * It's also possible to use HTTP DELETE leveraging the <a href="http://sling.apache.org/documentation/development/repository-based-development.html">WebDAV bundle from Sling</a>.
- * or the <a href="http://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html">Sling POST servlet</a> to uninstall the bundle.
- * The chosen method depends on the parameter {@link #deploymentMethod}.
+ * For details refer to <a href="bundle-installation.html">Bundle Uninstallation</a>.
*/
@Mojo(name = "uninstall")
public class BundleUninstallMojo extends AbstractBundleInstallMojo {
diff --git a/src/site/markdown/bundle-installation.md b/src/site/markdown/bundle-installation.md
index 9dcd3ff..d354877 100644
--- a/src/site/markdown/bundle-installation.md
+++ b/src/site/markdown/bundle-installation.md
@@ -1,22 +1,39 @@
-# Bundle Installation
+# Bundle Installation/Uninstallation
+
+There are three different installation approaches supported by the plugin which behave differently for the installation and uninstallation. In the following section all mechanisms are outlined individually for both use cases.
+
+<!-- MACRO{toc} -->
## Deploy/Upload/Install
-There are three different installation approaches supported by the plugin
-
### Felix Web Console
The plugin by default places an *HTTP POST* request to the [Felix Web Console](https://felix.apache.org/documentation/subprojects/apache-felix-web-console/web-console-restful-api.html#post-requests). This will achieve both upload and installation of the bundle in one request *synchronously*.
### WebDAV PUT
-It's also possible to use *HTTP PUT* instead of POST leveraging the [WebDAV bundle from Sling](https://sling.apache.org/documentation/development/repository-based-development.html). This will create a new Sling resource containing the OSGi bundle in the underlying repository.
+It's also possible to use *HTTP PUT* instead of POST leveraging the [WebDAV bundle from Sling](https://sling.apache.org/documentation/development/repository-based-development.html). This will create a new JCR node containing the OSGi bundle in the underlying repository.
From there it needs to be picked up by the [JCR Installer](https://sling.apache.org/documentation/bundles/jcr-installer-provider.html) to be actually installed in the OSGi container. The latter happens *asynchronously*. It is important that the bundle resource is uploaded to a location of the repository which is actually watched by the JCR installer (by default only resources below a resource called `install`).
### Sling POST Servlet
Since version 2.1.8 you can also leverage the [Sling POST servlet](https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html) for uploading the bundle to the repository. The subsequent installation is being performed *asynchronously* by the JCR Installer (similar to the WebDAV PUT approach).
-
+
+## Undeploy/Uninstall
+
+### Felix Web Console
+
+The plugin by default places an *HTTP POST* request to the [Felix Web Console](https://felix.apache.org/documentation/subprojects/apache-felix-web-console/web-console-restful-api.html#post-requests). This will achieve both uninstallation of the bundle in one request *synchronously*.
+
+### WebDAV PUT
+
+An *HTTP DELETE* request is issued which is handled by the [WebDAV bundle from Sling](https://sling.apache.org/documentation/development/repository-based-development.html). This will remove the JCR node containing the OSGi bundle in the underlying repository.
+From there it needs to be picked up by the [JCR Installer](https://sling.apache.org/documentation/bundles/jcr-installer-provider.html) to be actually uninstalled in the OSGi container. The latter happens *asynchronously*.
+
+### Sling POST Servlet
+
+An *HTTP DELETE* request is issued which is handled by the [Sling POST servlet](https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html). This will remove the resource containing the OSGi bundle in the underlying repository. The subsequent uninstallation is being performed *asynchronously* by the JCR Installer (similar to the WebDAV PUT approach).
+
## Intermediate Resources
For both WebDAV PUT and Sling POST servlet installation, intermediate resources (i.e. non-existing parent resources)
