[tinkerpop] 02/04: Updated warn on default ordering of results CTR

[sp...@apache.org]

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

spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git

commit e52c44d326c83b0e9ad324cca9e321f0c6ce99ed
Author: Stephen Mallette <sp...@genoprime.com>
AuthorDate: Thu Oct 11 12:01:30 2018 -0400

    Updated warn on default ordering of results CTR
---
 docs/src/reference/intro.asciidoc | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/src/reference/intro.asciidoc b/docs/src/reference/intro.asciidoc
index 9693267..0334a66 100644
--- a/docs/src/reference/intro.asciidoc
+++ b/docs/src/reference/intro.asciidoc
@@ -213,9 +213,10 @@ has gone through a particular section of the traversal expression (i.e. a loop).
 g.V(marko).repeat(out()).times(2).values('name')
 ----
 
-WARNING: A Traversal's result are never ordered unless explicitly by means of <<order-step,`order()`>>-step. Thus,
-never rely on the iteration order between TinkerPop3 releases and even within a release (as traversal optimizations
-may alter the flow).
+WARNING: TinkerPop does not guarantee the order of results returned from a traversal. It only guarantees not to modify
+the iteration order provided by the underlying graph. Therefore it is important to understand the order guarantees of
+the graph database being used. A traversal's result is never ordered by TinkerPop unless performed explicitly by means
+of <<order-step,`order()`>>-step.
 
 == On Gremlin Language Variants