Editorial fixes in response to review
diff --git a/source/documentation/io/rdf-input.md b/source/documentation/io/rdf-input.md
index 56786cd..e3429b8 100644
--- a/source/documentation/io/rdf-input.md
+++ b/source/documentation/io/rdf-input.md
@@ -82,7 +82,7 @@
### Example 1 : Using the RDFDataMgr {#using-rdfdatamgr}
-`RDFDataMgr` provide operations to load, read and write models and datasets.
+`RDFDataMgr` provides operations to load, read and write models and datasets.
`RDFDataMgr` "load" operations create an
in-memory container (model, or dataset as appropriate); "read" operations
@@ -101,7 +101,7 @@
### Example 2 : Common usage {#model-usage}
-The original Jena Model API operation for reade and write provide another way to the same machinery:
+The original Jena Model API operation for `read` and `write` provide another way to the same machinery:
Model model = ModelFactory.createDefaultModel() ;
model.read("data.ttl") ;
@@ -151,10 +151,10 @@
.source("data.ttl")
.parse(...);
-It can also be set in the chosen based on the `Context` object for the
+It can also be set in a `Context` object given the the RDFParser for the
operation, but normally this defaults to the global `Context` available via
`Context.get()`. The constant `SysRIOT.sysStreamManager`, which is
-`http://jena.apache.org/riot/streamManager` is used.
+`http://jena.apache.org/riot/streamManager`, is used.
Specialized StreamManagers can be configured with specific locators for
data:
diff --git a/source/documentation/notes/stream-manager.md b/source/documentation/notes/stream-manager.md
index 448ca09..a7410c2 100644
--- a/source/documentation/notes/stream-manager.md
+++ b/source/documentation/notes/stream-manager.md
@@ -4,7 +4,7 @@
The StreamManager is a utility to find and read files into models.
There is a standard global StreamManager and applications may also
-define specific ones by constructing addition StreamManagers.
+define specific ones by constructing additional StreamManagers.
The LocationMapper provides alternative locations for RDF data.
@@ -74,9 +74,9 @@
- `location-mapping.ttl`
- `location-mapping.rdf`
- `etc/location-mapping.rdf`
-- `etc/location-mapping.ttl`"
+- `etc/location-mapping.ttl`
-This is a specified as a path - note the path separator is always
+This is specified as a path - note the path separator is always
the character ';' regardless of operating system because URLs
contain ':'.
diff --git a/source/documentation/notes/system-initialization.md b/source/documentation/notes/system-initialization.md
index 99e46f4..e289ff4 100644
--- a/source/documentation/notes/system-initialization.md
+++ b/source/documentation/notes/system-initialization.md
@@ -9,7 +9,7 @@
must be done with care. Java initialization can lead to
visibility of uninitialized data.
-The standard initialization sequence is<br/>
+The standard initialization sequence is
Core -> RIOT -> ARQ -> TDB -> other (SDB, jena text, jena spatial)
The sequence from core to TDB should be executed before application
@@ -45,7 +45,7 @@
## The Initialization Process
-The process followed by `JenaSystem.init()` is to obtain an instance of
+The process followed by `JenaSystem.init()` is to obtain an instance of
`JenaSubsystemRegistry`, ask it to `load()` initialization code, then call
that code in an order based on declared level. The order of invocation
of different initialization code within the same level is undefined
@@ -86,7 +86,7 @@
An application can change the `JenaSubsystemRegistry` instance.
This must be done before any Jena code is called anywhere
-in the current JVM.
+in the current JVM.
// Example alternative registry.
JenaSubsystemRegistry r = new JenaSubsystemRegistryBasic() {
@@ -122,4 +122,3 @@
} finally {
Thread.currentThread().setContextClassLoader(contextClassLoader);
}
-
diff --git a/source/documentation/rdfstar/__index.md b/source/documentation/rdfstar/__index.md
index b98aa96..8e3afa1 100644
--- a/source/documentation/rdfstar/__index.md
+++ b/source/documentation/rdfstar/__index.md
@@ -75,7 +75,7 @@
| -------- | ----------- |
| `<< s p o >> apf:find t` . | Match the triple term. Any `s`, `p`, `o`, and `t` can be RDF terms or variables.|
-`apf:find` will result in all the variables being are set accorind to the match,
+`apf:find` will result in all the variables being set according to the match,
If `t` is a variable, `?t`, it is bound to a triple term for the match of `<<s p o>>`.
### SPARQL results
