diff --git a/README.md b/README.md
index 6417d261..cd9d243d 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ The Ecological Metadata Language (EML) defines a comprehensive vocabulary and a
- **EML 2.2.0 Specification**
- [Read it online](https://eml.ecoinformatics.org/)
- [Browse the interactive EML schema documentation](https://eml.ecoinformatics.org/schema)
- - [Download EML](http://knb.ecoinformatics.org/software/dist/eml-2.2.0.tar.gz) - The download consists of the
+ - [Download EML](https://knb.ecoinformatics.org/software/dist/eml-2.2.0.tar.gz) - The download consists of the
EML modules, described in the [XML Schema](http://www.w3.org/XML/Schema) language.
In addition, the full documentation on the modules is provided in HTML format.
- [Changes to EML in version 2.2.0](https://eml.ecoinformatics.org/whats-new-in-eml-2-2-0.html)
@@ -103,12 +103,12 @@ EML was originally developed by Matthew Jones at NCEAS based on a report by the
The following versions are still available for reference purposes, although they have been superseded by the current version (2.2.0). Please make every effort to use the current version.
-- [EML 2.2.0](http://knb.ecoinformatics.org/software/dist/eml-2.2.0.tar.gz)
-- [EML 2.1.1](http://knb.ecoinformatics.org/software/dist/eml-2.1.1.tar.gz)
-- [EML 2.1.0](http://knb.ecoinformatics.org/software/dist/eml-2.1.0.tar.gz)
-- [EML 2.0.1](http://knb.ecoinformatics.org/software/dist/eml-2.0.1.tar.gz)
-- [EML 2.0.0](http://knb.ecoinformatics.org/software/dist/eml-2.0.0.tar.gz)
-- [EML 1.4.1](http://knb.ecoinformatics.org/software/dist/eml-1.4.1.tar.gz)
+- [EML 2.2.0](https://knb.ecoinformatics.org/software/dist/eml-2.2.0.tar.gz)
+- [EML 2.1.1](https://knb.ecoinformatics.org/software/dist/eml-2.1.1.tar.gz)
+- [EML 2.1.0](https://knb.ecoinformatics.org/software/dist/eml-2.1.0.tar.gz)
+- [EML 2.0.1](https://knb.ecoinformatics.org/software/dist/eml-2.0.1.tar.gz)
+- [EML 2.0.0](https://knb.ecoinformatics.org/software/dist/eml-2.0.0.tar.gz)
+- [EML 1.4.1](https://knb.ecoinformatics.org/software/dist/eml-1.4.1.tar.gz)
## Copyright and License
Copyright: 1997-2019 Regents of the University of California
diff --git a/docs/eml-210info.md b/docs/eml-210info.md
index 079d63f3..65a7cc4c 100644
--- a/docs/eml-210info.md
+++ b/docs/eml-210info.md
@@ -461,7 +461,7 @@ Converting EML documents from v2.0.0/1 to v2.1.0
**A:** An XSL stylesheet is provided with the EML Utilities to convert
valid EML 2.0-series documents to EML 2.1.0 (see
-). The stylesheet performs
+). The stylesheet performs
basic tasks to create a template EML 2.1.0 document (below). For more
information, see the Utilities documentation.
@@ -492,7 +492,7 @@ and data types are not detectable by a stylesheet. Document authors are
advised to check the validity of their new EML 2.1.0 after
transformation. EML instance documents can be validated in these ways:
-1. With the [online EML Parser](http://knb.ecoinformatics.org/emlparser/ ). The online
+1. With the [online EML Parser](https://knb.ecoinformatics.org/emlparser/). The online
parser will validate all versions of EML.
2. Using the Parser that comes with EML. To execute it, change into the
diff --git a/docs/eml-220info.md b/docs/eml-220info.md
index e8d71b16..b9fed018 100644
--- a/docs/eml-220info.md
+++ b/docs/eml-220info.md
@@ -369,7 +369,7 @@ external identifiers, e.g., to a code from a system like ITIS or WoRMS.
## How can I convert from earlier versions of EML?
An XSL stylesheet is provided with the EML Utilities to convert valid EML
-2.1-series documents to EML 2.2.0 (see ).
+2.1-series documents to EML 2.2.0 (see ).
The stylesheet performs basic tasks to create a template EML 2.2.0 document.
For more information, see the Utilities documentation.
diff --git a/docs/eml-faq.md b/docs/eml-faq.md
index 58f7a404..0b4c9081 100644
--- a/docs/eml-faq.md
+++ b/docs/eml-faq.md
@@ -83,7 +83,7 @@ discovery, access, integration and synthesis.
**A:** All the documents associated with the EML development effort are
available via the project web server at
-. These projects are
+. These projects are
licensed under the GPL (Gnu Public License) agreement and can be freely
distributed and modified.
@@ -93,12 +93,12 @@ XML editor. How then do you get content into EML?
**A:** The Knowledge Network for Biocomplexity project has developed a
software client specifically to address this need.
-[Morpho](http://knb.ecoinformatics.org/software/) (after the butterfly
+[Morpho](https://knb.ecoinformatics.org/tools/morpho) (after the butterfly
genus) is written in java (making portable across computer platforms)
combines an easy to use interface to EML with a number of tools to make
it easier for ecologists to document data. These include a
reverse-engineering wizard. Morpho is available from
-. Morpho currently supports the
+. Morpho currently supports the
EML 2.1.0 release.
**Q:** EML contains provisions for communication. Is it possible to
@@ -139,7 +139,7 @@ metadata into EML depending on what form your existing metadata take.
into EML compliant XML.
3. Use an special purpose XML editor that generates EML (
- [Morpho](http://knb.ecoinformatics.org/software) or
+ [Morpho](https://knb.ecoinformatics.org/tools/morpho) or
[Xylographa](http://ces.asu.edu/bdi/Subjects/xylographa) ) and
manually retype the metadata.
@@ -185,7 +185,7 @@ metadata into EML depending on what form your existing metadata take.
NOTE: In each of the cases it may be necessary to add some additional
metadata in order to produce EML compliant documents.
-[Morpho](http://knb.ecoinformatics.org/software) will automatically
+[Morpho](https://knb.ecoinformatics.org/tools/morpho) will automatically
create EML compliant metadata either by adding it for you or indicating
that certain fields are mandatory.
@@ -195,7 +195,7 @@ query them or use them for data management?
**A:** EML is an exchange standard for communication of metadata but it
can be used as the framework for a data management system.
-[Metacat](http://knb.ecoinformatics.org/software) is a multipurpose XML
+[Metacat](https://knb.ecoinformatics.org/tools/metacat) is a multipurpose XML
metadata and data repository that is optimized for use with EML. If you
store your metadata in a relational database management system or plan
to then there are also solutions.