Architectural-Toolbox-Usage.md

@@ -14,7 +14,7 @@ java -jar path/to/arcan-c.jar -h
 ## Java projects
 To trigger the most basic analysis on a Java project stored in a Git repository you need to first run the following:
 ```
-java -jar path/to/arcan.jar-p $INPUTDIR -out $OUTDIR_ARCAN -git -branch $BRANCH -nDays $INTERVAL_GIT_COMMITS -startDate $STARTDATE
+java -jar path/to/arcan.jar -p $INPUTDIR -out $OUTDIR_ARCAN -git -branch $BRANCH -nDays $INTERVAL_GIT_COMMITS -startDate $STARTDATE
 ```
 This will trigger an analysis for the given repository stored in `$INPUTDIR` on the given branch and analysing one commit every `$INTERVAL_GIT_COMMITS` days starting from `$STARTDATE` (format YYYY-MM-DD).
 
@@ -26,8 +26,19 @@ java -jar path/to/astracker.jar -p $PROJECT -i $OUTDIR_ARCAN -o $OUTPUTDIR -pC -
 where `$PROJECT` is the name of your project (arbitrary).
 This should trigger the analysis and as soon as the analysis is complete, a number of CSV files will be saved under `$OUTPUTDIR/trackASOutput/$PROJECT` containing the smells, their characteristics, and the historical information of each commit analysed, including the number of changes to each class/package.
 
-# C/C++ projects
-For C/C++ projects, you need to run the following
+## C/C++ projects
+For C/C++ projects, the process is very similar to the Java one.
+
+```
+java -jar path/to/arcan-c.jar -p $INPUTDIR -out $OUTDIR_ARCAN -git -branch $BRANCH -nDays $INTERVAL_GIT_COMMITS -startDate $STARTDATE
+```
+
+and then, execute ASTracker:
+
+```
+java -jar path/to/astracker.jar -p $PROJECT -i $OUTDIR_ARCAN -o $OUTPUTDIR -pC -pCC -gitRepo $INPUTDIR -cppP
+```
+*Note* that the `-jP` flag was swapped with the `-cppP`, indicating that the project is a C++ project. For C projects, you have to use the `-cP` flag instead.