diff --git a/en/annotation.php b/en/annotation.php
index fcba7d388433f7eca96da84599c1eb3abc1a39df..7c9db893b03da174ba34343ce23d7e66675d9100 100644
--- a/en/annotation.php
+++ b/en/annotation.php
@@ -18,7 +18,7 @@ require('F_mainsidebar.php');
 	 <p>All L2 feature annotations have been deduced from various sources and described in detail in the <a href="C_download.php" target="_blank">annotation scheme</a>. You can review the development and origin of the indicators on which the annotation scheme is based at <a href="C_research.php#annotations" target="_blank">MERLIN for reserach</a>. The MERLIN annotations followed a strict policy of reliability control. Again, you can read more about this at <a href="C_research.php#anchor233" target="_blank">MERLIN for research  
 	 </a>.</p>
 <div id="anchor1"></div>	
-	 <h3><a href="#anchor1" onClick="toggle('#content1','#img1')"><img id="img1" src="img/toggle-expand.png></a> Excursus: Interpretating „errors“ with target hypotheses </h3>
+	 <h3><a href="#anchor1" onClick="toggle('#content1','#img1')"><img id="img1" src="img/toggle-expand.png"></a> Excursus: Interpretating „errors“ with target hypotheses </h3>
      <div id="content1" class="content">
 	 <p>As learner language (L2) is regarded as an evolving  language system in its own right, annotations were not merely based on error coding, but also took into account other linguistic  characteristics.</p>
       <p>In order to determine whether and to what extent a text deviates incorrectly, there must be a clear idea of what a learner presumably intended to write. In a learner text collection (learner corpus), it is important to make   this interpretation explicit to make annotations more easily   understandable and to avoid problems of reliability. Therefore, the MERLIN team formulated target hypotheses (TH) that are a   corrected version of the learner texts. The team followed the rules   developed for the <a href="http://www.linguistik.hu-berlin.de/institut/professuren/korpuslinguistik/forschung/falko" target="_blank" class="reference">FALKO corpus</a> and adapted them to the project needs where necessary (cf. Reznicek/Lüdeling et al. 2012).   </p>
@@ -34,7 +34,7 @@ require('F_mainsidebar.php');
 <p>The following contains lists of L2 features annotated in the MERLIN corpus that are illsutrated by examples from the languages in question.<br />
 </p>
   <div id="anchor2"></div>
-	 <h3><a href="#anchor2" onClick="toggle('#content2','#img2')"><img id="img2" src="img/toggle-expand.png></a> Grammar tags</h3>
+	 <h3><a href="#anchor2" onClick="toggle('#content2','#img2')"><img id="img2" src="img/toggle-expand.png"></a> Grammar tags</h3>
       <div id="content2" class="content">
            <p>
      <table border="0" cellpadding="0" cellspacing="7" bordercolor="99dff9">
@@ -164,7 +164,7 @@ require('F_mainsidebar.php');
 	 <p>* [...] tag-relevant extracts of learner language expressions {...} correction of the erroneous learner expression</p>
      </div>
 	 <div id="anchor3"></div>
-	 <h3><a href="#anchor3" onClick="toggle('#content3','#img3')"><img id="img3" src="img/toggle-expand.png></a> Orthografie </h3>
+	 <h3><a href="#anchor3" onClick="toggle('#content3','#img3')"><img id="img3" src="img/toggle-expand.png"></a> Orthografie </h3>
 	 <div id="content3" class="content">
 	 <p><table border="0" cellpadding="0" cellspacing="7" bordercolor="99dff9">
 	    <tr>