Merge pull request #166 from eXist-db/readme-fix

fix directory name...

Author: adamretter

README.md

@@ -22,17 +22,17 @@ Found an area of the documentation that needs to be improved? Please raise an [i
 
 Our test-suite performs a validation check on all articles when you open a pull request. You can speed up the review process by running `mvn validate` locally before submitting a pull request.
 
-Should you encounter documentation for features that are deprecated in the minimum eXist-db version mentioned [above](#dependencies), you can simply delete them. If you are unsure about this, please open an [issue](https://github.com/eXist-db/documentation/issues). 
+Should you encounter documentation for features that are deprecated in the minimum eXist-db version mentioned [above](#dependencies), you can simply delete them. If you are unsure about this, please open an [issue](https://github.com/eXist-db/documentation/issues).
 
 ## Building from source
 1.  Clone the repository to your system:
     ```bash
-    $ git clone https://github.com/exist-db/documentation.git exist-documentation
+    $ git clone https://github.com/exist-db/documentation.git documentation
     ```
 
 2.  Build the documentation application:
     ```bash
-    $ cd exist-documentation
+    $ cd documentation
     $ mvn clean package
     ```
     The compiled `.xar` file is located in the `/target` directory

RELEASE.md

@@ -6,6 +6,27 @@ Core-contributors should follow these steps when publishing a new release of the
 ```bash
 gpg --list-keys
 ```
+
+-  maven also requires a nexus account. You can create one at [oss.sonatype.org](https://oss.sonatype.org/#welcome) and include your credentials in your maven's `settings.xml` (replacing username and password):
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
+  <servers>
+    <server>
+      <id>sonatype-nexus-snapshots</id>
+      <username>USERNAME</username>
+      <password>PASSWORD</password>
+    </server>
+    <server>
+      <id>sonatype-nexus-staging</id>
+      <username>USERNAME</username>
+      <password>PASSWORD</password>
+    </server>
+  </servers>
+</settings>
+```
+
+
 -   You can perform a dry-run of the release procedure by executing
 ```bash
 $ mvn -DdryRun=true release:prepare