Fixes

Change-Id: I126135cdcc98fc017d099a3388d2b89fed95ee33
diff --git a/examples/index.html b/examples/index.html
index f343ce1..def4889 100644
--- a/examples/index.html
+++ b/examples/index.html
@@ -23,8 +23,8 @@
 A simple example for benchmarking the interpreter.
 </li>
 <li>
-<a href=examples.php?example=universitycourses">University Courses</a>:
-shows the capabilities and usage of Units.
+<a href="examples.php?example=universitycourses">University Courses</a>:
+An example showing the capabilities and usage of Units.
 </li>
 </ol>
 
diff --git a/examples/simpleclassmodelingrefactoring/index.html b/examples/simpleclassmodelingrefactoring/index.html
index e88013d..8140fe9 100644
--- a/examples/simpleclassmodelingrefactoring/index.html
+++ b/examples/simpleclassmodelingrefactoring/index.html
@@ -22,7 +22,7 @@
 <h2>Metamodel</h2>
 
 <p>
-<a href="examples/simpleclassmodelingrefactoring/classModel.png"><image src="examples/simpleclassmodelingrefactoring/classModel.png" align="center" width="639" /></a>
+<a href="simpleclassmodelingrefactoring/classModel.png"><image src="simpleclassmodelingrefactoring/classModel.png" align="center" width="639" /></a>
 <br>
 The metamodel is defined in the file <i>ClassModel.ecore</i>. We used 
 the Ecore Tools to draw a diagram (depicted above). 
@@ -39,7 +39,7 @@
 <h2>Refactoring Transformation Rules</h2>
 
 <p>
-<a href="examples/simpleclassmodelingrefactoring/refactoringRules.png"><image src="examples/simpleclassmodelingrefactoring/refactoringRules.png" align="right" width="400" /></a>
+<a href="simpleclassmodelingrefactoring/refactoringRules.png"><image src="simpleclassmodelingrefactoring/refactoringRules.png" align="right" width="400" /></a>
 Since refactoring is a specific kind of model transformation, refactorings for EMF-based 
 models can be specified in Henshin and then integrated into a model refactoring framework 
 such as <a href="http://www.eclipse.org/emf-refactor/">EMF Refactor</a>. 
@@ -54,7 +54,7 @@
 <h2>Scenario</h2>
 
 <p>
-<a href="examples/simpleclassmodelingrefactoring/scenario.png"><image src="examples/simpleclassmodelingrefactoring/scenario.png" align="right" width="300" /></a>
+<a href="simpleclassmodelingrefactoring/scenario.png"><image src="simpleclassmodelingrefactoring/scenario.png" align="right" width="300" /></a>
 Lets assume that a software developer wants to know which refactoring rules need to be 
 applied in order to restructure a class model. More specifically, we refer to the class 
 model shown in the following figure representing an early analysis model in the development 
@@ -97,14 +97,14 @@
 &rarr; Calculate Critical Pairs).
 </p>
 
-<a href="examples/simpleclassmodelingrefactoring/callCPAWizard.png"><image src="examples/simpleclassmodelingrefactoring/callCPAWizard.png" align="center" width="300" /></a>
+<a href="simpleclassmodelingrefactoring/callCPAWizard.png"><image src="simpleclassmodelingrefactoring/callCPAWizard.png" align="center" width="300" /></a>
 
 <p>
 This brings up a wizard to specify the rule set to be analyzed and the kind of critical 
 pairs that shall be analyzed. 
 </p>
 
-<a href="examples/simpleclassmodelingrefactoring/CPAWizard.png"><image src="examples/simpleclassmodelingrefactoring/CPAWizard.png" align="center" width="300" /></a>
+<a href="simpleclassmodelingrefactoring/CPAWizard.png"><image src="simpleclassmodelingrefactoring/CPAWizard.png" align="center" width="300" /></a>
 
 <p>
 After the CPA, a dedicated results view provides an overview on all conflicts and dependencies 
@@ -112,7 +112,7 @@
 as rule pairs. For each pair, a set of conflicts (dependencies) is listed named by their kinds. 
 </p>
 
-<a href="examples/simpleclassmodelingrefactoring/CPAResultView.png"><image src="examples/simpleclassmodelingrefactoring/CPAResultView.png" align="right" width="300" /></a>
+<a href="simpleclassmodelingrefactoring/CPAResultView.png"><image src="simpleclassmodelingrefactoring/CPAResultView.png" align="right" width="300" /></a>
 
 <p>
 Here, three conflics are found. The conflicts of the first and the third rule pair in the results 
@@ -127,7 +127,7 @@
 conflict (dependency). The following figure shows a minimal model in the tree-based Ecore instance editor.
 </p>
 
-<a href="examples/simpleclassmodelingrefactoring/CPAEditor.png"><image src="examples/simpleclassmodelingrefactoring/CPAEditor.png" align="center" width="600" /></a>
+<a href="simpleclassmodelingrefactoring/CPAEditor.png"><image src="simpleclassmodelingrefactoring/CPAEditor.png" align="center" width="600" /></a>
 
 <p>
 The minimal model (see center of the figure above) is related to the first <i>produce-forbid-conflict</i> 
@@ -147,7 +147,7 @@
 corresponding API. 
 </p>
 
-<a href="examples/simpleclassmodelingrefactoring/ICriticalPairAnalysis.png"><image src="examples/simpleclassmodelingrefactoring/ICriticalPairAnalysis.png" align="center" width="471" /></a>
+<a href="simpleclassmodelingrefactoring/ICriticalPairAnalysis.png"><image src="simpleclassmodelingrefactoring/ICriticalPairAnalysis.png" align="center" width="471" /></a>
 
 <p>
 The initialization can be done with one or two rule sets containing Henshin 
@@ -173,7 +173,7 @@
 
 <p>The following figure shows the results API.</p>
 
-<a href="examples/simpleclassmodelingrefactoring/CPAResultAPI.png"><image src="examples/simpleclassmodelingrefactoring/CPAResultAPI.png" align="center" width="400" /></a>
+<a href="simpleclassmodelingrefactoring/CPAResultAPI.png"><image src="simpleclassmodelingrefactoring/CPAResultAPI.png" align="center" width="400" /></a>
 
 <p>
 All conflicts (dependencies) are within the container <i>CPAResult</i>. Conflict 
@@ -192,4 +192,4 @@
 strictly separated.
 </p>
 
-<a href="examples/simpleclassmodelingrefactoring/CPKinds.png"><image src="examples/simpleclassmodelingrefactoring/CPKinds.png" align="center" width="429" /></a>
+<a href="simpleclassmodelingrefactoring/CPKinds.png"><image src="simpleclassmodelingrefactoring/CPKinds.png" align="center" width="429" /></a>
diff --git a/get-involved.php b/get-involved.php
index e7d5538..25f425f 100644
--- a/get-involved.php
+++ b/get-involved.php
@@ -49,7 +49,7 @@
 
 <h2>Contribute code</h2> 
 <ul>
- <li>Check out our codebase from the <a href="http://git.eclipse.org/c/henshin/org.eclipse.emft.henshin.git" target="_blank">Git repository</a> at Eclipse. Please refer to our instructions for <a href="https://wiki.eclipse.org/Henshin_Committer_Instructions#imports" target="_blank">importing projects and resolving dependencies</a>. We recommend </li>
+ <li>Check out our codebase from the <a href="http://git.eclipse.org/c/henshin/org.eclipse.emft.henshin.git" target="_blank">Git repository</a> at Eclipse. Please refer to our instructions for <a href="https://wiki.eclipse.org/Henshin_Committer_Instructions#imports" target="_blank">importing projects and resolving dependencies</a>. </li>
  <li>Ideally, please use <a href="https://git.eclipse.org/r/#/q/status%3Aopen+project%3Ahenshin/org.eclipse.emft.henshin" target="_blank">Gerrit</a> to contribute changes to the codebase. This allows us to apply our quality assurance process to all contributions. In our Wiki, we provide more detailed descriptions for <a href="https://wiki.eclipse.org/Henshin_Committer_Instructions" target="_blank">working with Gerrit</a>.</li>
  <li>Alternatively, you can also submit patches via e-mail -- especially if you want to contribute relatively small changes that do not justify the overhead of setting up Gerrit. In this case, <a href="#get-in-touch">get in touch with us</a>.</li>
 </ul>