<mapID target="disorder" url="html/webServices/proteinDisorder.html"/>
<mapID target="aacon" url="html/webServices/AACon.html"/>
<mapID target="seqfetch" url="html/features/seqfetch.html"/>
- <mapID target="dbreffetcher" url="html/webservices/dbreffetcher.html"/>
+ <mapID target="dbreffetcher" url="html/webServices/dbreffetcher.html"/>
<mapID target="seqmappings" url="html/features/seqmappings.html"/>
<mapID target="cdnafeatures" url="html/features/codingfeatures.html"/>
<mapID target="seqfeatures" url="html/features/seqfeatures.html"/>
Accession ids for the given sequence names. It is important to realise
that many DAS sources only use Uniprot accession ids, rather than
Swissprot/Uniprot sequence names.<br>
-The <a href="../webservices/dbreffetcher.html">database reference
+The <a href="../webServices/dbreffetcher.html">database reference
fetcher</a> documentation describes how Jalview discovers what database
references are appropriate for the sequences in the alignment.
<ul>
alignment</a></strong> and <strong><a href="../calculations/pca.html">PCA</a></strong>
calculations will only be performed using the <em>visible</em> parts of
the alignment.</li>
- <li><a href="../webservices/msaclient.html">Multiple Sequence
+ <li><a href="../webServices/msaclient.html">Multiple Sequence
Alignments</a> are performed locally on on each visible chunk of the input,
and concatenated with the hidden regions to form the final result.
</p>