diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index f3ac23afd843b60cb890d65f8e9e3a7672e3ade2..09a6d5ae73350aea194a72652323a12abaadb4d1 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -2,6 +2,7 @@ image: openjdk:8-jdk
 
 variables:
     SAREF_DEV_KEY: <my_private_key>
+    SAREF_PORTAL_KEY: <my_private_key>
 
 before_script:
   - eval $(ssh-agent -s)
@@ -68,6 +69,9 @@ trigger-release:
   stage: deploy
   only:
     - /^release-v/
+  variables:
+    SAREF_DEV_KEY: $SAREF_DEV_KEY
+    SAREF_PORTAL_KEY: $SAREF_PORTAL_KEY
   trigger:
     project: saref/saref-portal
     branch: master
diff --git a/README.md b/README.md
index ef107c0f18670e0c2cd080eebfff2c9d164f44d9..1bd06e1e77200669f5dda31fe40e1a34429e6bf4 100644
--- a/README.md
+++ b/README.md
@@ -1 +1,2 @@
 Repository for the SAREF core ontology.
+ 
\ No newline at end of file
diff --git a/documentation/description.html b/documentation/description.html
index c36a88ff6c046c8410403f4bcdf257f22352099b..c1d47190c1a3fac16b186332d6e6effc97158a75 100644
--- a/documentation/description.html
+++ b/documentation/description.html
@@ -20,7 +20,7 @@
 <p>SAREF is conceived in a modular way in order to allow the definition of any device from pre-defined building blocks, based on the function(s) that the device performs. Therefore, a <a href="#saref:Device">saref:Device</a> has at least one function (<a href="#saref:hasFunction">saref:hasFunction</a> min 1 <a href="#saref:Function">saref:Function</a>). Moreover, a <a href="#saref:Device">saref:Device</a> can be used for (<a href="#saref:isUsedFor">saref:isUsedFor</a> property) the purpose of offering a commodity, such as <a href="#saref:Water">saref:Water</a> or <a href="#saref:Gas">saref:Gas</a>. It can also measure a property, such as <a href="#saref:Temperature">saref:Temperature</a>, <a href="#saref:Energy">saref:Energy</a> and <a href="#saref:Smoke">saref:Smoke</a>. Moreover, a device may consist of other devices (<a href="#saref:consistsOf">saref:consistsOf</a> property).</p>
 
 <figure>
-  <img src="diagrams/Device.png" alt="Types of devices"/>
+  <img src="diagrams/DeviceTypes.png" alt="Types of devices"/>
   <figcaption id="Figure_3">Figure 3: Types of devices</figcaption>
 </figure>
 
diff --git a/ontology/saref.ttl b/ontology/saref.ttl
index 1fdf5ccf81ba417f0c9071a59b556ff59685dcff..af50fe5e73df2013bc6158997790ba8db4c90e91 100644
--- a/ontology/saref.ttl
+++ b/ontology/saref.ttl
@@ -48,7 +48,7 @@
  - Language tags have been added to all labels and comments.
 """ ;
                           rdfs:comment """Information about changes compared to version 1.1.1:
- - The classes and properties related to how to represent devices in building spaces (such as the saref:BuildingSpace class,  saref:BuildingObject class and saref:isLocatedIn property) have been removed from SAREF and incorporated  into the SAREF4BLDG extension related to buildings, including the reuse of the W3C¨ WGS84 geo positioning vocabulary.
+ - The classes and properties related to how to represent devices in building spaces (such as the saref:BuildingSpace class,  saref:BuildingObject class and saref:isLocatedIn property) have been removed from SAREF and incorporated  into the SAREF4BLDG extension related to buildings, including the reuse of the W3C? WGS84 geo positioning vocabulary.
  - The saref:DeviceCategory and saref:FunctionCategory classes have been removed. Instead, the hierarchy of device categories has been implemented directly as subclasses of the saref:Device class.
  - The information specific for energy efficiency has been moved to the SAREF4ENER extension. For example, the saref:Profile class has been redefined to accommodate only the properties that are general enough for any type of profile, not only for energy and power. Details on how to specifically model a power profile can be found in the SAREF4ENER extension. 
  - The subclasses of the saref:Energy class  have been removed (i.e., Average Energy, Maximum Energy, Minimum Energy, Total Energy, HVAC Energy, Hot Water Energy and Lighting Energy).