Removed incorrect JFact OWL reasoner version number and improved link.

README.md

@@ -17,9 +17,9 @@ Once pytest and all other required libraries are installed, you can execute all
 
 Curated phyloreferences produced by the [Curation Tool] as Phyloreference eXchange (PHYX) files are currently stored in the [`phyx`] directory (see [Brochu 2003] as an example). When executed as a test suite, these files are converted into the Web Ontology Language (OWL) in the following steps:
 
-1. PHYX files are converted to JSON-LD files using the [`phyx2owl`] Python tool. This tool translates [phylogenies represented in Newick] into a series of statements describing individual nodes and their relationships, and translates phyloreferences into OWL class restrictions that describes the nodes they resolve to.
+1. PHYX files are converted to JSON-LD files using the [`phyx2owl`] Python tool. This tool translate phylogenies stored in [the Newick format] into a series of statements describing individual nodes and their relationships, and translates phyloreferences into OWL class restrictions that describes the nodes they resolve to.
 2. The produced JSON-LD files can be transformed by any standards-compliant converter into OWL files. In the test suite, we use the  [`rdfpipe`] tool included in the [`rdflib`] Python library.
-3. Any compliant [OWL 2 DL reasoner] should be able to reason over this OWL file and provide information on which nodes each phyloreference resolved to. In the test suite, we use [`jphyloref`], a Java application that uses the [JFact++ 1.2.4 OWL reasoner] to reason over input OWL files. `jphyloref` can also read the annotations that indicate where each phyloreference was expected to resolve on any of the included phylogenies, and test whether phyloreferences resolved to the expected nodes.
+3. Any compliant [OWL 2 DL reasoner] should be able to reason over this OWL file and provide information on which nodes each phyloreference resolved to. In the test suite, we use [`jphyloref`], a Java application that uses the [JFact++ OWL reasoner] to reason over input OWL files. `jphyloref` can also read the annotations that indicate where each phyloreference was expected to resolve on any of the included phylogenies, and test whether phyloreferences resolved to the expected nodes.
 
 We are currently working on a complete workflow that would allow us to [merge separate PHYX files into a single Clade Ontology] available as a single OWL file available for individual download. At the moment, therefore, OWL files need to be generated by running the test suite on your own computer.
 
@@ -31,7 +31,7 @@ We are currently working on a complete workflow that would allow us to [merge se
 [`phyx`]: ./phyx/
 [Brochu 2003]: ./phyx/Brochu%202003/paper.json
 [`phyx2owl`]: ./phyx2owl/
-[phylogenies represented in Newick]: https://en.wikipedia.org/wiki/Newick_format
+[the Newick format]: https://en.wikipedia.org/wiki/Newick_format
 [`rdfpipe`]: http://rdflib.readthedocs.io/en/stable/apidocs/rdflib.tools.html#module-rdflib.tools.rdfpipe
 [`rdflib`]: http://rdflib.readthedocs.io/
 [OWL 2 DL reasoner]: https://www.w3.org/TR/2012/REC-owl2-direct-semantics-20121211/