Repository: tinkerpop Updated Branches: refs/heads/TINKERPOP-1912-tp33 17bf6efe0 -> bf1e242ee (forced update)
CTR: fixed minor 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/42bacafb Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/42bacafb Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/42bacafb Branch: refs/heads/TINKERPOP-1912-tp33 Commit: 42bacafbf4189cfb89ad53f1b38fee9ea21dd64e Parents: df7870a Author: Daniel Kuppitz <daniel_kupp...@hotmail.com> Authored: Mon Apr 9 11:32:38 2018 -0700 Committer: Daniel Kuppitz <daniel_kupp...@hotmail.com> Committed: Mon Apr 9 11:32:38 2018 -0700 ---------------------------------------------------------------------- docs/src/reference/the-traversal.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/42bacafb/docs/src/reference/the-traversal.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/reference/the-traversal.asciidoc b/docs/src/reference/the-traversal.asciidoc index 69bc8a3..86fb324 100644 --- a/docs/src/reference/the-traversal.asciidoc +++ b/docs/src/reference/the-traversal.asciidoc @@ -2342,7 +2342,7 @@ g.V().out().as('a').out().as('b').out().as('c'). by('name') ---- -By using the `from()` and `to()` modulators traversers can ensure that only certain sections of the path are are acyclic. +By using the `from()` and `to()` modulators traversers can ensure that only certain sections of the path are acyclic. [gremlin-groovy] ---- @@ -3043,7 +3043,7 @@ of the Gremlin traversal machine's compiler. There are 5 categories of strategie * There is an application-level feature that can be embedded into the traversal logic (*decoration*). * There is a more efficient way to express the traversal at the TinkerPop3 level (*optimization*). * There is a more efficient way to express the traversal at the graph system/language/driver level (*provider optimization*). - * There are are some final adjustments/cleanups/analyses required before executing the traversal (*finalization*). + * There are some final adjustments/cleanups/analyses required before executing the traversal (*finalization*). * There are certain traversals that are not legal for the application or traversal engine (*verification*). NOTE: The <<explain-step,`explain()`>>-step shows the user how each registered strategy mutates the traversal.
