[jena-site] 02/02: Improve language usage

[an...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

andy pushed a commit to branch improve-language
in repository https://gitbox.apache.org/repos/asf/jena-site.git

commit cc1070d2ecd563e1e99a3f6ab29f3ad0081371c3
Author: Andy Seaborne <an...@apache.org>
AuthorDate: Thu Sep 2 16:09:02 2021 +0100

    Improve language usage
---
 README.md                                       | 2 +-
 source/documentation/fuseki2/fuseki-layout.md   | 2 +-
 source/documentation/ontology/__index.md        | 2 +-
 source/documentation/query/spatial-query-doc.md | 4 ++--
 source/documentation/tools/__index.md           | 2 +-
 source/getting_started/__index.md               | 3 ---
 6 files changed, 6 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index 8aa96db..df5a6e3 100644
--- a/README.md
+++ b/README.md
@@ -72,7 +72,7 @@ Steps to do to setup the Jenkins job:
 * Branch source -> git
 
 * Set the gitbox url -> `https://gitbox.apache.org/repos/asf/jena-site.git` and use
-the jenkins (master pub key) credentials.
+the jenkins (pub key) credentials.
 
 * In the 'Scan Multibranch Pipeline Triggers' check the 'Periodically if not
 otherwise run' checkbox and enter a sane value (e.g. 15 minutes). This is needed
diff --git a/source/documentation/fuseki2/fuseki-layout.md b/source/documentation/fuseki2/fuseki-layout.md
index 32de76a..5d1f9f5 100644
--- a/source/documentation/fuseki2/fuseki-layout.md
+++ b/source/documentation/fuseki2/fuseki-layout.md
@@ -59,7 +59,7 @@ server deployment files and directories.
 
 
 The `system_files/` keeps a copy of any assemblers uploaded to
-configure the server. The master copy is kept in the system database.
+configure the server. The primary copy is kept in the system database.
 
 # Resetting
 
diff --git a/source/documentation/ontology/__index.md b/source/documentation/ontology/__index.md
index 33dcd3f..1936801 100644
--- a/source/documentation/ontology/__index.md
+++ b/source/documentation/ontology/__index.md
@@ -156,7 +156,7 @@ the basic vocabulary, and RDFS is perfectly well suited to this.
 Note also that we can both describe classes, in general terms, and we
 can describe particular *instances* of those classes. So there may
 be a particular individual Fred who is a Fish (i.e. has
-`rdf:type Fish`), and who has two eyes. His companion Freda, a
+`rdf:type Fish`), and who has two eyes. Their companion Freda, a
 [Mexican Tetra](http://en.wikipedia.org/wiki/Mexican_tetra), or
 blind cave fish, has no eyes. One use of an ontology is to allow us
 to fill-in missing information about individuals. Thus, though it
diff --git a/source/documentation/query/spatial-query-doc.md b/source/documentation/query/spatial-query-doc.md
index f2fea6a..4f213b2 100644
--- a/source/documentation/query/spatial-query-doc.md
+++ b/source/documentation/query/spatial-query-doc.md
@@ -95,8 +95,8 @@ For 2) WKT, DBPedia uses `geo:geometry`, while Linked Geo Data adopts `ogc:asWKT
 
 **Important note** In order to read geo data in 2) WKT literal format, jena-spatial uses [JTS Topology Suite](http://tsusiatsoftware.net/jts/main.html),
 which is under LGPL licence. jena-spatial **does not** make a hard dependency on JTS. In other words,
-if an end user just uses the feature of 1), there's no need to depend on JTS (i.e. nothing needs to be done). If he wants 2),
-he can make it by setting the `SpatialContextFactory` of 
+if an end user just uses the feature of 1), there's no need to depend on JTS (i.e. nothing needs to be done). If they want 2),
+they can make it by setting the `SpatialContextFactory` of 
 [EntityDefinition](https://github.com/apache/jena/tree/main/jena-spatial/src/main/java/org/apache/jena/query/spatial/EntityDefinition.java)
 to `JtsSpatialContextFactory`, which is an optional choice. In this way, the JTS libs should be in the classpath. Here's the sample code: 
 
diff --git a/source/documentation/tools/__index.md b/source/documentation/tools/__index.md
index a75caf6..67e876e 100644
--- a/source/documentation/tools/__index.md
+++ b/source/documentation/tools/__index.md
@@ -44,7 +44,7 @@ Note that many examples of using Jena tools typically use the Linux style invoca
 
 ### Common Issues with Running the Tools
 
-If you receive errors stating that a class is not found then it is most likely that `JENA_HOME` is not set correctly.  As a quick sanity check you can try the following to see if it is set appropriately:
+If you receive errors stating that a class is not found then it is most likely that `JENA_HOME` is not set correctly.  As a quick check you can try the following to see if it is set appropriately:
 
 **On Linux / Mac**
 
diff --git a/source/getting_started/__index.md b/source/getting_started/__index.md
index b62f99a..c5523f8 100644
--- a/source/getting_started/__index.md
+++ b/source/getting_started/__index.md
@@ -45,6 +45,3 @@ The interaction between the different APIs:
 ![Jena architecture overview](/images/jena-architecture.png "Jena architecture overview")
 
 <h2><img class="logo-menu" src="/images/jena-logo/jena-logo-notext-small.png" alt="jena logo">Other resources</h2>
-
-Finally, Jena committer Paolo Castagna has listed some [example programs](https://github.com/castagna/jena-examples)
-using Jena on his GitHub site.