diff --git a/docs/installationguide.md b/docs/installationguide.md
index 2cf227c3..cd48f081 100644
--- a/docs/installationguide.md
+++ b/docs/installationguide.md
@@ -129,23 +129,10 @@ In this mode, the log file is written in `/var/log/iotaul/iotaul.log`.
 The Docker automatically starts listening in the API ports, so there is no need to execute any process in order to have
 the application running. The Docker image will automatically start.
 
-## Packaging
-
-The only package type allowed is RPM. In order to execute the packaging scripts, the RPM Build Tools must be available
-in the system.
-
-From the root folder of the project, create the RPM with the following commands:
-
-```bash
-cd rpm
-./create-rpm.sh -v <version-number> -r  <release-number>
-```
-
-Where `<version-number>` is the version (x.y.z) you want the package to have and `<release-number>` is an increasing
-number dependent un previous installations.
-
 ## Configuration
 
+#### Overview
+
 All the configuration for the IoT Agent resides in the `config.js` file, in the root of the application. This file is a
 JavaScript file, that contains the following sections:
 
@@ -416,3 +403,18 @@ It means that we need to make some changes in the execution of node.js and in th
             net.nf_conntrack_max = 1048576
 
     For more details about any other kernel parameters, take a look to the example [sysctl.conf](sysctl.conf) file.
+    
+## Packaging
+
+The only package type allowed is RPM. In order to execute the packaging scripts, the RPM Build Tools must be available
+in the system.
+
+From the root folder of the project, create the RPM with the following commands:
+
+```bash
+cd rpm
+./create-rpm.sh -v <version-number> -r  <release-number>
+```
+
+Where `<version-number>` is the version (x.y.z) you want the package to have and `<release-number>` is an increasing
+number dependent un previous installations.
diff --git a/docs/usermanual.md b/docs/usermanual.md
index 91854528..5a029aa4 100644
--- a/docs/usermanual.md
+++ b/docs/usermanual.md
@@ -9,7 +9,7 @@
 ## API Overview
 
 This section describes the specific South-bound API implemented by this IoTAgent. For the Configuration API and other
-APIs concerning general IoTAgents, check the [API Reference section](#apireference);
+APIs concerning general IoTAgents, check the [API Reference section](https://github.com/telefonicaid/iotagent-ul/blob/master/README.md#api).
 
 ### Ultralight 2.0 Protocol
 
@@ -47,7 +47,7 @@ Measure groups can additionally have an optional timestamp, with the following s
 ```
 
 The timestamp will be added as a prefix of the measures themselves, separated by a '|'. The attribute will be translated
-to a `TimeInstant` attribute in the final entity.T
+to a `TimeInstant` attribute in the final entity.
 
 #### Active versus passive attributes
 
@@ -334,7 +334,6 @@ by the protocol, in this case '/ul', just include apikey and deviceid (e.g: `/FF
 >  receive commands in an appropriate format.
 
 
-This transport protocol binding is still under development.
 
 ##### Sending a single measure in one message