You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by an...@apache.org on 2021/12/09 10:16:57 UTC

[jena-site] 08/08: Fixes to address review comments

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

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

commit ffc86074dc78a9a192747020415db4b5d92091bc
Author: Andy Seaborne <an...@apache.org>
AuthorDate: Sun Dec 5 23:14:11 2021 +0000

    Fixes to address review comments
---
 source/documentation/sparql-apis/__index.md | 6 +++---
 source/documentation/tdb/faqs.md            | 2 +-
 source/documentation/tdb/tdb-xloader.md     | 8 ++++----
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/source/documentation/sparql-apis/__index.md b/source/documentation/sparql-apis/__index.md
index 9f741b1..d137820 100644
--- a/source/documentation/sparql-apis/__index.md
+++ b/source/documentation/sparql-apis/__index.md
@@ -91,7 +91,7 @@ objects have been removed.
 
 * Substitution of variables for concrete values in query and update execution.
   This is a form of paramterization that works in both local and remnote usage
-  (unlike "intial bindings" which are only available for lcoal query execution).
+  (unlike "initial bindings" which are only available for local query execution).
   See the [substitution section](#substitution) section below.
 
 * `HttpOp`, using `java.net.http.HttpClient`, is split into `HttpRDF` for
@@ -116,7 +116,7 @@ Unlike "initial bindings" substitution is provided in query and update builders
 for both local and remote cases. 
 
 Substitution is always "replace variable with RDF term" in a query or update
-that is correct syntax. This means is does not apply to `INSERT DATA` or `DELETE
+that is correct syntax. This means it does not apply to `INSERT DATA` or `DELETE
 DATA` but can be used with `INSERT { ?s ?p ?o } WHERE {}` and 
 `DELETE { ?s ?p ?o } WHERE {}`.
 
@@ -140,7 +140,7 @@ See also
 * [Parameterized Queries](documentation/query/parameterized-sparql-strings.html) 
 * [Jena Query Builder](https://jena.apache.org/documentation/extras/querybuilder/index.html)
 
-which provide a different ways to build a query.
+which provide different ways to build a query.
 
 ## <tt>RDFConnection</tt>
 
diff --git a/source/documentation/tdb/faqs.md b/source/documentation/tdb/faqs.md
index 285ed77..b51f970 100644
--- a/source/documentation/tdb/faqs.md
+++ b/source/documentation/tdb/faqs.md
@@ -25,7 +25,7 @@ title: TDB FAQs
 TDB2 is a later generation of database for Jena. It is more robust and can
 handle large update transactions.
 
-These are different databases systems - the have different on-disk file formats
+These are different databases systems - they have different on-disk file formats
 and databases for one are not compatible with other database engine.
 
 <a name="transactions"></a>
diff --git a/source/documentation/tdb/tdb-xloader.md b/source/documentation/tdb/tdb-xloader.md
index e27d77b..82c8878 100644
--- a/source/documentation/tdb/tdb-xloader.md
+++ b/source/documentation/tdb/tdb-xloader.md
@@ -4,7 +4,7 @@ title: TDB xloader
 
 TDB xloader ("x" for external) is a bulkloader for very large datasets. The goal
 is stability and reliability for long running loading, running on modest
-hardware and can load to storage of rotating disk or SSD.
+hardware and can be use to load a database on rotating disk or SSD.
 
 xloader is not a replacement for regular TDB1 and TDB2 loaders.
 
@@ -37,8 +37,8 @@ or
 Additionally, there is an argument `--tmpdir` to use a different directory for
 temporary files.
 
-`FILE` is any RDF syntax supported by Jena. Syntax is detemined by file
-extension and can include an addtional ".gz" or ".bz2" for compresses files.
+`FILE` is any RDF syntax supported by Jena. Syntax is determined by the file
+extension and can include an addtional ".gz" or ".bz2" for compressed files.
 
 ### Advice
 
@@ -46,7 +46,7 @@ To avoid a load failing due to a syntax or other data error, it is advisable to
 run `riot --check` on the data first. Parsing is faster than loading.
 
 The TDB databases will take up a lot of disk space and in addition during
-loading `xloader` uses a significant amout of temporary disk space.
+loading `xloader` uses a significant amount of temporary disk space.
 
 If desired, the data can be converted to [RDF Thrift](../io/rdf-binary.html) at
 this stage by adding `--stream rdf-thrift` to the riot checking run.  Parsing