You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by ki...@apache.org on 2017/10/23 02:32:49 UTC

svn commit: r1812967 [2/2] - in /jena/site/trunk/content: documentation/ documentation/assembler/ documentation/csv/ documentation/fuseki2/ documentation/hadoop/ documentation/inference/ documentation/io/ documentation/jdbc/ documentation/notes/ docume...

Modified: jena/site/trunk/content/documentation/tdb/architecture.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/architecture.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/architecture.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/architecture.mdtext Mon Oct 23 02:32:48 2017
@@ -103,7 +103,7 @@ bottom 56 bits. The top 8 bits indicates
 or the value space.
 
 The value spaces handled are (TDB 0.8): xsd:decimal, xsd:integer,
-xsd:dateTime, xsd:date and xsd:boolean. Each has it's own encoding
+xsd:dateTime, xsd:date and xsd:boolean. Each has its own encoding
 to fit in 56 bits. If a node falls outside of the range of values
 that can be represented in the 56 bit encoding.
 
@@ -113,7 +113,7 @@ information is retained to an accuracy o
 timezones for Z and for no explicit timezone.
 
 By storing the value, the exact lexical form is not recorded. The
-integers 01 and 1 will both be treated as a the value 1.
+integers 01 and 1 will both be treated as the value 1.
 
 Derived XSD datatypes are held as their base type. The exact
 datatype is not retained; the value of the RDF term is.
@@ -130,7 +130,7 @@ TDB provides low level optimization of b
 TDB runs on both 32-bit and 64-bit Java Virtual Machines. The same
 file formats are used on both systems and database files can be
 transferred between architectures (no TDB system should be running
-for the the database at the time of copy). What differs is the file
+for the database at the time of copy). What differs is the file
 access mechanism used.
 
 TDB is faster on a 64 bit JVM because more memory is available for
@@ -158,7 +158,7 @@ limit the size of TDB datasets. Instead,
 LRU cache of B+Tree blocks. Applications should set the JVM heap to
 1G or above (within the JVM specific limit).
 
-On 32-bit Java, TDB uses it's own file caching to enable large
+On 32-bit Java, TDB uses its own file caching to enable large
 databases. 32-bit Java limits the address space of the JVM to about
 1.5Gbytes (the exact size is JVM-dependent), and this includes
 memory mapped files, even though they are not in the Java heap. The

Modified: jena/site/trunk/content/documentation/tdb/commands.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/commands.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/commands.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/commands.mdtext Mon Oct 23 02:32:48 2017
@@ -35,7 +35,7 @@ Cygwin.
 
 ### Script set up - bash scripts
 
-Set the environment variable `JENAROOT` to the root of the the Jena
+Set the environment variable `JENAROOT` to the root of the Jena
 installation. E.g:
 
     export JENAROOT=/home/somebody/dev/apache-jena
@@ -113,7 +113,7 @@ is assumed.
 
 ### `tdbloader`
 
-Bulk loader and index builder. Performans bulk load operations more
+Bulk loader and index builder. Performs bulk load operations more
 efficiently than simply reading RDF into a TDB-back model.
 
 ### `tdbloader2`
@@ -167,4 +167,4 @@ format.
 ### tdbstats
 
 Produce a statistics for the dataset. See the
-[TDB Optimizer description.](optimizer.html#statistics-rule-file).
\ No newline at end of file
+[TDB Optimizer description.](optimizer.html#statistics-rule-file).

Modified: jena/site/trunk/content/documentation/tdb/configuration.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/configuration.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/configuration.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/configuration.mdtext Mon Oct 23 02:32:48 2017
@@ -21,7 +21,7 @@ Options can be set globally, through out
 execution basis. TDB uses the same mechanism as
 [ARQ](http://jena.sf.net/ARQ "http://jena.sf.net/ARQ").
 
-There is a global context, which is give to each query query
+There is a global context, which is give to each query
 execution as it is created. Modifications to the global context
 after the query execution is created are not seen by the query
 execution. Modifications to the context of a single query execution

Modified: jena/site/trunk/content/documentation/tdb/datasets.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/datasets.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/datasets.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/datasets.mdtext Mon Oct 23 02:32:48 2017
@@ -36,7 +36,7 @@ Alternatively, if the symbol tdb:unionDe
 [TDB Configuration](configuration.html)) is
 set, the unnamed graph for the query is the union of all the named
 graphs in the datasets. The stored default graph is ignored and is
-not part of the the data of the union graph although it is
+not part of the data of the union graph although it is
 accessible by the special name `<urn:x-arq:DefaultGraph\>` in a GRAPH
 pattern.
 
@@ -83,4 +83,4 @@ The use of [TDB Transactions](tdb_transa
 
       ...
       //Perform operations on infModel.
-      ...
\ No newline at end of file
+      ...

Modified: jena/site/trunk/content/documentation/tdb/dynamic_datasets.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/dynamic_datasets.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/dynamic_datasets.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/dynamic_datasets.mdtext Mon Oct 23 02:32:48 2017
@@ -25,7 +25,7 @@ graphs drawn only from the TDB data stor
     dataset to be the union of those graphs.
 -   Using one or more FROM NAMED, with no FROM in a query,
     causes an empty graph to be used for the default graph.
--   Using one or more FROM NAMED, with no FROM in a query, where the the symbol
+-   Using one or more FROM NAMED, with no FROM in a query, where the symbol
     [`TDB.symUnionDefaultGraph`](configuration.html)
     is also set, causes the default graph to be the set union of all the named
     graphs (FROM NAMED).

Modified: jena/site/trunk/content/documentation/tdb/optimizer.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/optimizer.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/optimizer.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/optimizer.mdtext Mon Oct 23 02:32:48 2017
@@ -108,7 +108,7 @@ set globally:
 and it may also be set on an individual query execution using it's
 local context.
 
-     try(QueryExecutiuon qExec = QueryExecutionFactory.create(...)) {
+     try(QueryExecution qExec = QueryExecutionFactory.create(...)) {
         qExec.getContext().set(ARQ.symLogExec,true) ;
         ResultSet rs = qExec.execSelect() ;
      }
@@ -226,7 +226,7 @@ relative counts are representative of th
 ### Statistics Rule Language
 
 A rule is made up of a triple pattern and a count estimation for
-the approximate number of matches that the pattern will yeild. This
+the approximate number of matches that the pattern will yield. This
 does have to be exact, only an indication.
 
 In addition, the optimizer considers which variables will be bound
@@ -287,7 +287,7 @@ While a complete rule is of the form:
 
 there is an abbreviated form:
 
-    (prediate count)
+    (predicate count)
 
 The abbreviated form is equivalent to writing:
 
@@ -366,7 +366,7 @@ and does not need to predicate exact cou
 right but may be slightly wrong are still useful overall.
 
 Rules involving rdf:type can be useful where they indicate whether
-a partciualr class is common or not. In some datasets
+a particular class is common or not. In some datasets
 
     ((VAR rdf:type class) ...)
 
@@ -382,4 +382,4 @@ number of instances, in which case
 
     ((VAR rdf:type class) ...)
 
-is a useful selective rule.
\ No newline at end of file
+is a useful selective rule.

Modified: jena/site/trunk/content/documentation/tdb/store-parameters.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/store-parameters.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/store-parameters.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/store-parameters.mdtext Mon Oct 23 02:32:48 2017
@@ -66,7 +66,7 @@ demands from other programmes on the sam
 * "direct" using TDB's own in-heap block caching.  It avoids the problem that
 addressing is limited to a total of about 1.5Gbytes on 32 bit Java.
 
-By default, TDB uses memory mapped files on 64 bit Java and it's own file
+By default, TDB uses memory mapped files on 64 bit Java and its own file
 caching on 32 bit java.
 
 On Microsoft Windows, "mapped" databases can not be deleted while the JVM is running on MS
@@ -145,7 +145,7 @@ This is modified by any dynamic options
 create a specialized database, one way to do that is to create an empty
 directory and put a `tdb.cfg` in place.
 
-If there is no parameter file and this this is a new database, use the
+If there is no parameter file and this is a new database, use the
 application provided store parameters, or if there are no application
 provided parameters, use the system default parameters. If application
 supplied parameters are used, write a `tdb.cfg` file.

Modified: jena/site/trunk/content/documentation/tdb/tdb_system.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/tdb_system.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/tdb_system.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/tdb_system.mdtext Mon Oct 23 02:32:48 2017
@@ -3,7 +3,7 @@ Title: TDB with 64-bit and 32-bit JVMs
 TDB runs on both 32-bit and 64-bit Java Virtual Machines. The same
 file formats are used on both systems and database files can be
 transferred between architectures (no TDB system should be running
-for the the database at the time of copy). The difference is that a
+for the database at the time of copy). The difference is that a
 different file access mechanism used.
 
 The file access mechanism can be set explicitly, but this is not a
@@ -23,7 +23,7 @@ file caching.
 
 ## 32-bit Java
 
-On 32-bit Java, TDB uses it's own file caching to enable large
+On 32-bit Java, TDB uses its own file caching to enable large
 databases. 32-bit Java limits the address space of the JVM to about
 1.5Gbytes (the exact size is JVM-dependent), and this includes
 memory mapped files, even though they are not in the Java heap. The
@@ -36,4 +36,4 @@ The on-disk file format is compatible be
 and databases can be transferred between systems by file copy if the
 databases are not in use (no TDB or Fuseki instance is accessing them
 at the time).  Databases can not be copied while TDB is running, even
-if TDB is not actively processing a query or update.
\ No newline at end of file
+if TDB is not actively processing a query or update.

Modified: jena/site/trunk/content/documentation/tdb2/tdb2_admin.md
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb2/tdb2_admin.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb2/tdb2_admin.md (original)
+++ jena/site/trunk/content/documentation/tdb2/tdb2_admin.md Mon Oct 23 02:32:48 2017
@@ -19,8 +19,8 @@ right.
 `Backups` is the directory used to write backup files.
 
 `tdb.lock` is the lock file to stop multiple use of the same database at
-the same time by different JVM processes. (If yuo wish to share a datbase
-bewteen processes, or machines, consider using [Fuseki2 with TDB2](tdb2_fuseki.html).
+the same time by different JVM processes. (If you wish to share a database
+between processes, or machines, consider using [Fuseki2 with TDB2](tdb2_fuseki.html).
 
 ## Compaction
 

Modified: jena/site/trunk/content/documentation/tdb2/tdb2_fuseki.md
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb2/tdb2_fuseki.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb2/tdb2_fuseki.md (original)
+++ jena/site/trunk/content/documentation/tdb2/tdb2_fuseki.md Mon Oct 23 02:32:48 2017
@@ -4,7 +4,7 @@ TDB2 is incorporated into Fuseki2, both
 [Fuseki2 basic server](../fuseki2/fuseki-embedded.html#fuseki-basic).
 
 In each case, the database needs to be defined in a configuration file,
-either a completw server configuration (see below) or as an entry in the
+either a complete server configuration (see below) or as an entry in the
 `FUSEKI_BASE/configuration/` area of the full server.
 
 Example complete server configuration file for full or basic servers:
@@ -50,7 +50,7 @@ The key difference is the declared `rdf:
 
 Note that the Fuseki UI does not provide a way to create TDB2 databases;
 a configuration file must be used. Once setup, upload, query and graph
-editting will be routed to the TDB2 database.
+editing will be routed to the TDB2 database.
 
 For a service configuration in `FUSEKI_BASE/configuration/`:
 

Modified: jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext (original)
+++ jena/site/trunk/content/documentation/tools/eyeball-manual.mdtext Mon Oct 23 02:32:48 2017
@@ -83,7 +83,7 @@ Run the Eyeball command:
         [-remark] [-version]
 
 The -*whatever* sections can come in any order and may be repeated,
-in which case the additonal arguments are appended to the existing
+in which case the additional arguments are appended to the existing
 ones. Exactly one of *-check*, *-sign*, *-accept*, or *version*
 must be provided; all the other options are optional.
 
@@ -379,7 +379,7 @@ reported if the constraint fails.
 
 Checks that all URI and bnode resources in the model have an
 rdf:type property in the model or the schema(s). If there is a
-statement in the confiuration with property `eye:checkLiteralTypes`
+statement in the configuration with property `eye:checkLiteralTypes`
 and value `eye:true`, also checks that every literal has a type or
 a language. *Not* in the default set of inspectors.
 
@@ -677,7 +677,7 @@ need to be downloaded each time Eyeball
 
 ### Configuring inspectors
 
-The inspectors that Eyeball runs over the model are specfied by
+The inspectors that Eyeball runs over the model are specified by
 *eye:inspector* properties of inspector resources. These resources
 are identified by `eye:shortName`s (supplied on the command line).
 Each such property value must be a plain string literal whose value
@@ -790,7 +790,7 @@ configuration root, as its argument.
 The `ShortClassHandle` is a string literal giving the short name
 used to refer to the class. The default short name used is
 **default**. There should be no more than one *eye:shortName*
-statement with the same ShortClassHandle in the configuation file,
+statement with the same ShortClassHandle in the configuration file,
 but the same class can have many different short names.
 
 The `TextRenderer` supports an additional property `eye:labels` to
@@ -873,7 +873,7 @@ four operations:
 
 -   *begin( Report r, OntModel assume )*: Begin a new inspection.
     `r` is the `Report` object which will accept the reports in this
-    inpsection; `assume` is the model containing the assumed
+    inspection; `assume` is the model containing the assumed
     ontologies. `begin` is responsible for declaring this inspectors
     *report properties*.
 -   *inspectModel( Report r, OntModel m )*: Do a whole-model

Modified: jena/site/trunk/content/documentation/tools/schemagen.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tools/schemagen.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tools/schemagen.mdtext (original)
+++ jena/site/trunk/content/documentation/tools/schemagen.mdtext Mon Oct 23 02:32:48 2017
@@ -54,14 +54,14 @@ Command line option | RDF config file pr
 `--noproperties` | `sgen:noproperties` | Option to suppress properties in the generated vocabulary file.
 `-o <filename>`  <br /> `-o <dir>` | `sgen:output` | Specify the destination for the output. If the given value evaluates to a directory, the generated class will be placed in that directory with a file name formed from the generated (or given) class name with ".java" appended.
 `--nostrict` | `sgen:noStrict` | Option to turn off strict checking for ontology classes and properties (prevents `ConversionExceptions`).
-`--ontology` | `sgen:ontology` | The generated vocabulary will use the ontology API terms, inpreference to RDF model API terms.
+`--ontology` | `sgen:ontology` | The generated vocabulary will use the ontology API terms, in preference to RDF model API terms.
 `--owl` | `sgen:owl` | Specify that the language of the source is OWL (the default). Note that RDFS is a subset of OWL, so this setting also suffices for RDFS.
 `--package <string>` | `sgen:package` | Specify the Java package name and directory.
 `--propSection <string>` | `sgen:propSection` | Section declaration comment for properties section.
 `--propTemplate <string>` | `sgen:propTemplate` | Template for writing out declarations of property resources.
 `-r <uri>` | | Specify the uri of the root node in the RDF configuration model.
 `--rdfs` | `sgen:rdfs` | Specify that the language of the source ontology is RDFS.
-`--strictIndividuals` | `sgen:strictIndividuals` | When selecting the individuals to include in the output class, schemagen will normally include those individuals whose `rdf:type` is in the included namespaces for the vocabulary. However, if `strictIndividuals` is turned on, then all individuals in theoutput class must themselves have a URI in the included namespaces.
+`--strictIndividuals` | `sgen:strictIndividuals` | When selecting the individuals to include in the output class, schemagen will normally include those individuals whose `rdf:type` is in the included namespaces for the vocabulary. However, if `strictIndividuals` is turned on, then all individuals in the output class must themselves have a URI in the included namespaces.
 `--uppercase`  | `sgen:uppercase` | Option for mapping constant names to uppercase (like Java constants). Default is to leave the case of names unchanged.
 `--includeSource` | `sgen:includeSource` | Serializes the source code of the vocabulary, and includes this into the generated class file. At class load time, creates a `Model` containing the definitions from the source
 
@@ -320,7 +320,7 @@ options) to configure the tool. If a fil
 `-c`, and that file cannot be located, schemagen will stop with an
 error.
 
-Schemagen will assume the the language encoding of the
+Schemagen will assume the language encoding of the
 configuration file is implied by the filename/ULRL suffix: ".n3"
 means N3, ".nt" means NTRIPLES, ".rdf" and ".owl" mean "RDF/XML".
 By default it assumes RDF/XML.
@@ -688,7 +688,7 @@ vocabulary with `--includeSource` may ri
         </plugins>
       </build>
 
-At this point you can run `mvn generate-sources` in your project to cause `schemagen` to run and create your Java source (note that this goal is run automatically from `mvn compile` or `mvn install`, so there really isn't any reason to to run it manually unless you wish to just generate the source).  The source file is placed in the maven standard `target/generated-sources/java` directory, which is added to the project classpath by `build-helper-maven-plugin`.
+At this point you can run `mvn generate-sources` in your project to cause `schemagen` to run and create your Java source (note that this goal is run automatically from `mvn compile` or `mvn install`, so there really isn't any reason to run it manually unless you wish to just generate the source).  The source file is placed in the maven standard `target/generated-sources/java` directory, which is added to the project classpath by `build-helper-maven-plugin`.
 
 
 ## Using schemagen with Ant

Modified: jena/site/trunk/content/documentation/txn/index.md
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/txn/index.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/txn/index.md (original)
+++ jena/site/trunk/content/documentation/txn/index.md Mon Oct 23 02:32:48 2017
@@ -15,7 +15,7 @@ on the basic API using Java8 features.
 ## Overview
 
 Transaction provide applications with a safe way to use and update data between
-threads. The properies of transactions are [ACID](https://en.wikipedia.org/wiki/ACID)
+threads. The properties of transactions are [ACID](https://en.wikipedia.org/wiki/ACID)
 - Atomic, Consistent, Isolation, Durable -
 meaning that groups of changes are made visible to other transactions
 in a single unit or all chnages are not at all, and when made chnages are not
@@ -24,12 +24,12 @@ reversed, or the case of persistent stor
 Jena provides transaction on datasets and provides "serializable transactions".
 Any application code reading data sees all changes made elsewhere,
 not parts of changes.  In particular, SPARQL aggregation like `COUNT` are
-correct and do no tsee partial changes due to other transactions.
+correct and do not see partial changes due to other transactions.
 
 The exact details are dependent on the implementation.
 
 Transactions can not be [nested](https://en.wikipedia.org/wiki/Nested_transaction)
-(a tranaction happening inside an outertransaction results in chnages visble only
+(a transaction happening inside an outertransaction results in chnages visible only
 to the outer transaction until that commits).
 
 Transactions are "per thread". Actions by different threads on the same dataset are
@@ -42,12 +42,12 @@ There is a default implementation, based
 that can be used with any mixed set of components. Certain storage sub-systems provide
 better concurrency with MR+SW (multiple-read and single writer).
 
-| Dataset   | Facilties | Creation |
+| Dataset   | Facilities | Creation |
 |-----------|-----------|----------|
 | TxnMem    | MR+SW     | `DatasetFactory.createTxnMem` |
 | TDB       | MR+SW, persistent | `TDBFactory.create` |
 | General   | MRSW      | `DatasetFactory.create` |
 
-The general dataset can have have any graphs added to it (e.g. inference graphs).
+The general dataset can have any graphs added to it (e.g. inference graphs).
 
 [More details of transactions in TDB](transactions_tdb.html).

Modified: jena/site/trunk/content/documentation/txn/transactions_api.md
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/txn/transactions_api.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/txn/transactions_api.md (original)
+++ jena/site/trunk/content/documentation/txn/transactions_api.md Mon Oct 23 02:32:48 2017
@@ -1,4 +1,4 @@
-Title: Jena Transactons API
+Title: Jena Transactions API
 
 -   [API for Transactions](#api-for-transactions)
     - [Read transactions](#read-transactions)
@@ -7,7 +7,7 @@ Title: Jena Transactons API
 
 ## API for Transactions
 
-This page decribes the basic transaction API in Jena (3.1.0 and later).
+This page describes the basic transaction API in Jena (3.1.0 and later).
 
 There is also a [higher-level API](txn.html) useful in many situations
 but sometimes it is necessary to use the basic transaction API described here.

Modified: jena/site/trunk/content/documentation/txn/txn.md
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/txn/txn.md?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/txn/txn.md (original)
+++ jena/site/trunk/content/documentation/txn/txn.md Mon Oct 23 02:32:48 2017
@@ -8,12 +8,12 @@ Features:
 
 -   Java8 idioms
 -   Application exceptions cause transaction aborts.
--   "Transaction continuation" - use any existing active trsnaction.
+-   "Transaction continuation" - use any existing active transaction.
 -   Autocommit - ensure actions are inside a transaction even if none is active.
 
 ## Transactions
 
-The [basic transactions API](basic_txn_api.html) provides opertions
+The [basic transactions API](basic_txn_api.html) provides operations
 `begin`, `commit`, `abort` and `end`.
 
 A write transaction looks like:
@@ -66,7 +66,7 @@ writer needs to read the dataset or mode
     }) ;
 
 whereas reading data into an RDF dataset needs to be a write transaction
-(the dataset or model is chanaged).
+(the dataset or model is changed).
 
     Dataset ds = ... ;
     Txn.executeWrite(ds, ()-> {
@@ -118,7 +118,7 @@ results needs to be take:
     ResultSet List<String> resultSet = Txn.calculateRead(ds, ()-> {
          List<String> accumulator = new ArrayList<>() ;
          try(QueryExecution qExec = QueryExecutionFactory.create(query, ds)) {
-             return ResutSetFactory.copyResults(qExec.execSelect()) ;
+             return ResultSetFactory.copyResults(qExec.execSelect()) ;
          }
     }) ;
     // use "resultSet"
@@ -126,7 +126,7 @@ results needs to be take:
 ## Working with RDF Models
 
 The unit of transaction is the dataset.  Model in datasets are just views of that dataset.
-Model should not be passed out of a transaction because they are still atatched to the
+Model should not be passed out of a transaction because they are still attached to the
 dataset.
 
 ## Autocommit and Transaction continuation
@@ -135,7 +135,7 @@ If there is a transaction already starte
 the transaction and that transaction is not terminated.  If there is not transaction already started,
 a transaction is wrapped around the `Txn.execute...` action.
 
-    Dataset datsset = ...
+    Dataset dataset = ...
     // Main transaction.
     dataset.begin(ReadWrite.WRITE) ;
     try {
@@ -153,7 +153,7 @@ a transaction is wrapped around the `Txn
 
 `Txn` uses Java `Runnable` for the application code, passed into control code
 that wraps the transaction operations around the application code. This results
-in application code automatically applied transction begin/commit/end as needed.   
+in application code automatically applied transaction begin/commit/end as needed.   
 
 A bare read transaction requires the following code structure (no exception handling):   
 

Modified: jena/site/trunk/content/download/maven.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/download/maven.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/download/maven.mdtext (original)
+++ jena/site/trunk/content/download/maven.mdtext Mon Oct 23 02:32:48 2017
@@ -94,7 +94,7 @@ structuring Jena development.
   <tr>
     <td><code>jena-sdb</code></td>
     <td><code>jar</code></td>
-    <td>SDB (SQL based triple store). SDB should only be used when there is an absolute requirment on
+    <td>SDB (SQL based triple store). SDB should only be used when there is an absolute requirement on
       using SQL. TDB is to be preferred.</td>
   </tr>
   <tr>
@@ -187,5 +187,5 @@ tree and build with maven
     cd jena
     mvn clean install
 
-Each of the modules can be built on it's own but they
+Each of the modules can be built on its own but they
 require the current snapshots and Jena parent POM to be installed.

Modified: jena/site/trunk/content/help_and_support/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/help_and_support/index.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/help_and_support/index.mdtext (original)
+++ jena/site/trunk/content/help_and_support/index.mdtext Mon Oct 23 02:32:48 2017
@@ -46,7 +46,7 @@ Asking good questions is **the best way
   you've at least made some effort to find things out for yourself.
 
   - Where appropriate **show a complete test case**. Seeing where your code goes wrong is generally
-  much easier if we can run it our our computers. Corollaries: **don't post your entire project** - take some
+  much easier if we can run it our computers. Corollaries: **don't post your entire project** - take some
   time to reduce it down to a minimal test case. **Include enough data** - runnable code is no help if
   critical resources like `*.rdf` files are missing. Reducing your code down to a minimal test case
   is often enough for you to figure out the problem yourself, which is always satisfying!

Modified: jena/site/trunk/content/tutorials/rdf_api.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/rdf_api.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/rdf_api.mdtext (original)
+++ jena/site/trunk/content/tutorials/rdf_api.mdtext Mon Oct 23 02:32:48 2017
@@ -64,7 +64,7 @@ might look like this in RDF:</p>
 <img border="0" src="figures/fig1.png" alt="figure 1" width="240" height="180"></p>
 
 <p>The <a href="#glos-Resource"><i>resource</i></a>, John Smith, is shown as
-an elipse and is identified by a Uniform Resource Identifier (URI)<font
+an ellipse and is identified by a Uniform Resource Identifier (URI)<font
 size="1"><sup><a href="#fn-01">1</a></sup></font>,  in this case
 "http://.../JohnSmith".  If you try to access that resource using your
 browser, you are unlikely to be successful; April the first jokes not
@@ -206,11 +206,11 @@ about a resource. A statement has three
 because of its three parts.</p>
 
 <p>An RDF Model is represented as a <i>set</i> of statements.  Each call of
-<code>addProperty</code> in tutorial2 added a another statement to the Model.
+<code>addProperty</code> in tutorial2 added another statement to the Model.
 (Because a Model is set of statements, adding a duplicate of a statement has no
 effect.)  The Jena model interface defines a <code>listStatements()</code>
 method which returns an <code>StmtIterator</code>, a subtype of Java's
-<code>Iterator</code> over all all the statements in a Model.
+<code>Iterator</code> over all the statements in a Model.
 <code>StmtIterator</code> has a method <code>nextStatement()</code>
 which returns the next statement from the iterator (the same one that
 <code>next()</code> would deliver, already cast to <code>Statement</code>).
@@ -875,7 +875,7 @@ StmtIterator iter = model.listStatements
     });</code></pre>
 </blockquote>
 
-<p>This sample code uses a neat Java technique of overridding a method
+<p>This sample code uses a neat Java technique of overriding a method
 definition inline when creating an instance of the class.  Here the
 <code>selects(...)</code> method checks to ensure that the full name ends
 with "Smith".  It is important to note that filtering based on the subject,
@@ -1108,8 +1108,8 @@ example.</p>
 <p>The Jena classes offer methods for manipulating containers including
 adding new members, inserting new members into the middle of a container and
 removing existing members.  The Jena container classes currently ensure that
-the the list of ordinal properties used starts at rdf:_1 and is contiguous.
-The RDFCore WG have relaxed this contraint, which allows partial
+the list of ordinal properties used starts at rdf:_1 and is contiguous.
+The RDFCore WG have relaxed this constraint, which allows partial
 representation of containers.  This therefore is an area of Jena may be
 changed in the future.</p>
 
@@ -1195,7 +1195,7 @@ model.write(system.out, "N-TRIPLE");</co
 statement is added.</p>
 
 <p>The RDFCore WG has defined mechanisms for supporting datatypes in RDF.
-Jena suports these using the <i>typed literal</i> mechanisms; they are
+Jena supports these using the <i>typed literal</i> mechanisms; they are
 not discussed in this tutorial.</p>
 
 <h2 id="ch-Glossary">Glossary</h2>
@@ -1256,4 +1256,4 @@ Another term for a statement.</dd>
 </ol>
 
 
-  [1]: sparql_data/vc-db-1.rdf
\ No newline at end of file
+  [1]: sparql_data/vc-db-1.rdf

Modified: jena/site/trunk/content/tutorials/sparql_basic_patterns.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/sparql_basic_patterns.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/sparql_basic_patterns.mdtext (original)
+++ jena/site/trunk/content/tutorials/sparql_basic_patterns.mdtext Mon Oct 23 02:32:48 2017
@@ -52,7 +52,7 @@ variable with the same name is used.
 This query ([q-bp2.rq](sparql_data/q-bp2.rq)) involves two triple patterns, each
 triple ends in a '.' (but the dot after the last one can be omitted
 like it was in the one triple pattern example). The variable y has
-to be the same for each triple pattern match. The the solutions
+to be the same for each triple pattern match. The solutions
 are:
 
     -------------

Modified: jena/site/trunk/content/tutorials/sparql_query1.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/sparql_query1.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/sparql_query1.mdtext (original)
+++ jena/site/trunk/content/tutorials/sparql_query1.mdtext Mon Oct 23 02:32:48 2017
@@ -41,7 +41,7 @@ command line applications.
 ## Executing the query
 
 There are [helper scripts](/documentation/query/cmds.html) in the Jena distribution `bat/` and
-`bin/` directories.  You should check these scripts before use.  They can be placed on on the shell
+`bin/` directories.  You should check these scripts before use.  They can be placed on the shell
 command path.
 
 ### Windows setup

Modified: jena/site/trunk/content/tutorials/sparql_union.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/tutorials/sparql_union.mdtext?rev=1812967&r1=1812966&r2=1812967&view=diff
==============================================================================
--- jena/site/trunk/content/tutorials/sparql_union.mdtext (original)
+++ jena/site/trunk/content/tutorials/sparql_union.mdtext Mon Oct 23 02:32:48 2017
@@ -68,7 +68,7 @@ may not come out in the same order. 
 to be faster, depending on the data and the storage used, because
 the second form may have to get all the triples from the graph to
 match the triple pattern with unbound variables (or blank nodes) in
-each slot, then test each `?p` to see it it matches one of the
+each slot, then test each `?p` to see if it matches one of the
 values. It will depend on the sophistication of the query optimizer
 as to whether it spots that it can perform the query more
 efficiently and is able to pass the constraint down as will as to