Energy-requirements.md

@@ -35,16 +35,16 @@ In the project repo, **a config.txt file must be added in the root directory (R1
 **R1(a,c,d and f)** must be satisfied.
 The **source files** needed to be analysed must be specified in the config.txt (R1c) file. Also **all the include libraries** (R1d) needed for each source file to be compiled as standalone file needed to be added in the config.txt file in the way mentioned above.
 
-**Energy Indicators monitoring and Hotspots Identification**
+**Energy Indicators monitoring and Hotspots Identification (Hotspots)**
 
 **R1(a,b,c,e and f)** must be satisfied.
 The application **must be able to be built and executed on a linux machine automatically (R2)**, while the commands for its proper execution (R1b) must be included in the config.txt (R1) file as mentioned above. Commands that build the entire project should also be included (R1e) while **-g** debugging flags have to be used in the *gcc* compilation in all *makefiles*.
 
-**Acceleration Optimization Suggestion**
+**Acceleration Optimization Suggestion (Acceleration)**
 
 The same requirements as Hotspots analysis adding that the project has to be **a single-threaded application (R3)**. For the rest of the analysis types the application can be of course multi-threaded.
 
-**History Analysis**
+**History Analysis (History)**
 
 **Previous commits of the project should have been already analysed (R4)** using Static Energy Consumption Estimation tool in order for the service to retrieve them from the database. This is performed by placing {“commit”:commit-id} in the “Extra Info by Toolbox” text field for the Energy Toolbox. (The last commit of the repo should contain the config.txt file).