--- a/components-for-industry/application-development/oak-toolkit/frontend-environment.html
+++ b/components-for-industry/application-development/oak-toolkit/frontend-environment.html
@@ -137,20 +137,26 @@
                     <div class="col-md-7 mt-sm-20 left-align-p">
                         <h2>vf-OAK Frontend</h2>
                         <br>
-                        <p>The OAK-Frontend Environment (FE) offers a GUI-Editor to allow vApp developers the implementation of end-user
-                        interfaces for their solutions. It will be accessible from within the OAK Studio as a plain browser consuming external
-                        microservices. These services provide large ranges of visual templates implemented in HTML5 + CSS3. Developers can
-                        combine them within the GUI editor to achieve enclosed vApp visualisations at the end. The templates can stand for
-                        themselves (eg customised GUI elements) or contain additional behaviour and logic (eg registration forms or error
-                        representation). vApp developers thus will have a high degree of flexibility and power as there are barely any
-                        restrictions in merging templates. The FE will still develop an abstraction layer concept, subordinating the entities
-                        into abstraction levels. This strategy will produce additional guidance for the developer and speed up the process of
-                        rapid prototyping. The editor also allows external configuration like translations for internationalisation, as well as
-                        internal, individual configurations for each template itself. The module is subdivided in lower-level modules:</p>
-
+                        <p>
+                            The OAK-Frontend Environment (FE) offers a GUI-Editor to allow vApp developers the implementation of end-user interfaces for 
+                            their solutions. It will be accessible from within the Studio as a plain browser consuming external microservices. These services 
+                            provide large ranges of visual templates implemented in HTML5 + CSS3.
+                        </p>
+
+                        <p>
+                            Developers can combine these templates within the GUI editor to achieve enclosed vApp visualisations at the end. The templates can 
+                            stand for themselves (eg customised GUI elements) or contain additional behaviour and logic (eg registration forms or error representation). 
+                            vApp developers thus will have a high degree of flexibility and power as there are barely any restrictions in merging templates.
+                        </p>
+                        <p>
+                            The FE will still develop an abstraction layer concept, subordinating the entities into abstraction levels. This strategy will produce 
+                            additional guidance for the developer and speed up the process of rapid prototyping. The editor also allows external configuration like 
+                            translations for internationalisation, as well as internal, individual configurations for each template itself. The module is subdivided 
+                            in lower-level modules:
+                        </p>
                         <ul class="fa-ul">
-                                <li><i class="fa-li fa fa-square"></i>The <em>Client</em>-Module is a single HTML file, processing user inputs and forwarding them to the mircoservices module, where necessary calculations for representing vApps take place.</span> </li>
-                                <li><i class="fa-li fa fa-square"></i>The <em>Server</em>-Module consists out of multiple Mircoservices working together, which listen to user inputs and transform them into clickable prototypes of a vApp.</span> </li>
+                                <li><i class="fa-li fa fa-square"></i>The Client-Module is a single HTML file, processing user inputs and forwarding them to the mircoservices module, where necessary calculations for representing vApps take place.</span> </li>
+                                <li><i class="fa-li fa fa-square"></i>The Server-Module consists out of multiple Mircoservices working together, which listen to user inputs and transform them into clickable prototypes of a vApp.</span> </li>
                         </ul>
 
                     </div>