reorder sections

README.md

@@ -14,27 +14,6 @@ In addition it provides an extension for [filtering in filevault-package-maven-p
 
 The encryption algorithm used internally is symmetrical **AES encryption (AES/CBC/PKCS5Padding)** with a **128 bit** key. Since it uses [Cypher Block Chaining](https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation#CBC) a random initialisation vector is used to make the encrypted text always look different (for the same plaintext). It uses [BSAFE Crypto-J from RSA (now Dell)][bsafe-wikipedia] as implementation basis.
 
-## Retrieve key from AEM environment
-
-The easiest way to retrieve the (usually auto-generated random) key from an AEM server is to leverage the [Groovy Console][groovyconsole]. The key is usually stored on the file system (either below the bundle data directory or in a directory given through OSGi property/environment variable with name `com.adobe.granite.crypto.keys.path`). It can be exposed with the following Groovy script.
-
-```
-org.osgi.framework.Bundle bundle = Arrays.asList(bundleContext.getBundles()).find { "com.adobe.granite.crypto.file".equals(it.getSymbolicName()) };
-
-out.println("Bundle " + bundle);
-out.println("Data File " + bundle.getBundleContext().getDataFile("master"));
-String keyPath = bundle.getBundleContext().getProperty("com.adobe.granite.crypto.keys.path");
-out.println("Keys Path " + keyPath );
-File masterFile;
-if (keyPath != null) {
-    masterFile = new File(keyPath, "master");
-} else {
-    masterFile = bundle.getDataFile("master")
-}
-byte [] bytes = java.nio.file.Files.readAllBytes(masterFile.toPath());
-out.println("master key in base64 encoding:\n" + Base64.getEncoder().encodeToString(bytes));
-```
-
 ## Usage
 
 This library can be used as extension for the filevault-package-maven plugin or programmatically via API.
@@ -90,6 +69,27 @@ try (CryptoSupportFactory cryptoSupportFactory = new CryptoSupportFactory(this.g
 }
 ```
 
+## Retrieve key from AEM environment
+
+The easiest way to retrieve the (usually auto-generated random) master key from an AEM server is to leverage the [Groovy Console][groovyconsole]. The key is usually stored on the file system (either below the bundle data directory or in a directory given through OSGi property/environment variable with name `com.adobe.granite.crypto.keys.path`). It can be exposed with the following Groovy script.
+
+```
+org.osgi.framework.Bundle bundle = Arrays.asList(bundleContext.getBundles()).find { "com.adobe.granite.crypto.file".equals(it.getSymbolicName()) };
+
+out.println("Bundle " + bundle);
+out.println("Data File " + bundle.getBundleContext().getDataFile("master"));
+String keyPath = bundle.getBundleContext().getProperty("com.adobe.granite.crypto.keys.path");
+out.println("Keys Path " + keyPath );
+File masterFile;
+if (keyPath != null) {
+    masterFile = new File(keyPath, "master");
+} else {
+    masterFile = bundle.getDataFile("master")
+}
+byte [] bytes = java.nio.file.Files.readAllBytes(masterFile.toPath());
+out.println("master key in base64 encoding:\n" + Base64.getEncoder().encodeToString(bytes));
+```
+
 ## Use Cases
 
 Several [AEM Cloud Service configurations][aem-cloudservice-configs] still access (encrypted) credentials from the repository (like [Dynamic Media configuration][dynamic-media-aem-config]) instead of leveraging interpolated OSGi configurations.