Repository: tinkerpop Updated Branches: refs/heads/TINKERPOP-1996 38dc70df6 -> 10478be0c
TINKERPOP-1996 Fixed up typos in docs Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/10478be0 Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/10478be0 Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/10478be0 Branch: refs/heads/TINKERPOP-1996 Commit: 10478be0c9cabb6b20723c3185464977767172bc Parents: 38dc70d Author: Stephen Mallette <sp...@genoprime.com> Authored: Fri Jul 27 07:10:41 2018 -0400 Committer: Stephen Mallette <sp...@genoprime.com> Committed: Fri Jul 27 07:10:41 2018 -0400 ---------------------------------------------------------------------- docs/src/reference/the-traversal.asciidoc | 6 +++--- docs/src/upgrade/release-3.4.x.asciidoc | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/10478be0/docs/src/reference/the-traversal.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/reference/the-traversal.asciidoc b/docs/src/reference/the-traversal.asciidoc index c861d87..d096933 100644 --- a/docs/src/reference/the-traversal.asciidoc +++ b/docs/src/reference/the-traversal.asciidoc @@ -1060,9 +1060,9 @@ job of the `io()`-step. By default, TinkerPop supports three formats for importi NOTE: Additional documentation for TinkerPop IO formats can be found in the link:http://tinkerpop.apache.org/docs/x.y.z/dev/io/[IO Reference]. -By itself the `io()` step merely configures the kind of importing and exporting that is going +By itself the `io()`-step merely configures the kind of importing and exporting that is going to occur and it is the follow-on call to the `read()` or `write()` step that determines which of those actions will -execute. Therefore, a typical usage of the `io()` step would look like this: +execute. Therefore, a typical usage of the `io()`-step would look like this: [source,java] ---- @@ -1073,7 +1073,7 @@ g.io(someOutputFile).write().iterate() IMPORTANT: The commands above are still traversals and therefore require iteration to be executed, hence the use of `iterate()` as a termination step. -By default, the `io()` step will try to detect the right file format using the file name extension. To gain greater +By default, the `io()`-step will try to detect the right file format using the file name extension. To gain greater control of the format use the `with()` step modulator to provide further information to `io()`. For example: [source,java] http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/10478be0/docs/src/upgrade/release-3.4.x.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/upgrade/release-3.4.x.asciidoc b/docs/src/upgrade/release-3.4.x.asciidoc index 0bb3903..8d87397 100644 --- a/docs/src/upgrade/release-3.4.x.asciidoc +++ b/docs/src/upgrade/release-3.4.x.asciidoc @@ -81,7 +81,7 @@ g.io(someInputFile).read().iterate() g.io(someOutputFile).write().iterate() ---- -While `io()` step is still single-threaded for OLTP style loading, it can be utilized in conjunction with OLAP which +While `io()`-step is still single-threaded for OLTP style loading, it can be utilized in conjunction with OLAP which internally uses `CloneVertexProgram` and therefore any graph `InputFormat` or `OutputFormat` can be configured in conjunction with this step for parallel loads of large datasets.
