From: gmungoc <g.m.carstairs@dundee.ac.uk>
Date: Thu, 15 Jun 2017 10:34:37 +0000 (+0100)
Subject: JAL-2418 typos
X-Git-Tag: Release_2_10_3b1~183^2~4^2
X-Git-Url: http://source.jalview.org/gitweb/?p=jalview.git;a=commitdiff_plain;h=8a6f2af24f832baf9899c7b0c8f4f723c592bc99

JAL-2418 typos
---

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