X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2Freleases.html;h=e39a4c19197802dcf32f18a48473d19c4f75b1d3;hb=8a6f2af24f832baf9899c7b0c8f4f723c592bc99;hp=97d6789b4b2cb756b292915b5f0f2c59daa41974;hpb=a07bb83b2db533506ec098ec05cd920d4109314c;p=jalview.git

diff --git a/help/html/releases.html b/help/html/releases.html
index 97d6789..e39a4c1 100755
--- a/help/html/releases.html
+++ b/help/html/releases.html
@@ -127,7 +127,7 @@ li:before {
           <ul>
             <li>
               <!-- JAL-2398, -->Fixed incorrect value in BLOSUM 62 score
-              matrix - C->R should be '3'<br />Old matrix restored with
+              matrix - C->R should be '-3'<br />Old matrix restored with
               this one-line groovy script:<br />jalview.analysis.scoremodels.ScoreModels.instance.BLOSUM62.@matrix[4][1]=3
             </li>
             <li>
@@ -136,7 +136,7 @@ li:before {
               earlier versions of Jalview, gaps matching gaps were
               penalised, and gaps matching non-gaps penalised even more.
               In the PCA calculation, gaps were actually treated as
-              non-gaps - so different costs were applied, which mean't
+              non-gaps - so different costs were applied, which meant
               Jalview's PCAs were different to those produced by
               SeqSpace.<br />Jalview now treats gaps in the same way as
               SeqSpace (ie it scores them as 0). To restore pre-2.10.2