This is an automated email from the ASF dual-hosted git repository.
rdale pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/master by this push:
new fa5e5b6 spelling CTR
new fb700db Merge branch 'tp33'
fa5e5b6 is described below
commit fa5e5b6bd79913b6dda703b76e6dd5abe157a04e
Author: Robert Dale <[email protected]>
AuthorDate: Wed Dec 19 12:38:12 2018 -0500
spelling CTR
---
docs/src/dev/developer/release.asciidoc | 2 +-
docs/src/recipes/anti-patterns.asciidoc | 2 +-
docs/src/recipes/olap-spark-yarn.asciidoc | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/src/dev/developer/release.asciidoc
b/docs/src/dev/developer/release.asciidoc
index fcb6cb2..384d2ea 100644
--- a/docs/src/dev/developer/release.asciidoc
+++ b/docs/src/dev/developer/release.asciidoc
@@ -126,7 +126,7 @@ during this period.
assigned (use common sense when reviewing these tickets before removing the
Fix Version as it is possible the incorrect
Resolution may have been assigned).
.. Be sure that `gremlin-io-test` has been updated (from 3.3.0 on - this
module was not available prior to the 3.3.x line)
-... This is typically a post-release task, but it's worthing checking to be
sure in case the step was somehow overlooked.
+... This is typically a post-release task, but it's worth checking to be sure
in case the step was somehow overlooked.
... Instructions for updating the module are described in the <<io,IO
Documentation and Testing Section>>.
. When all documentation changes are in place, use `bin/publish-docs.sh` to
deploy a final `SNAPSHOT` representation
of the docs and thus validate that there are no issues with the documentation
generation process. Request review
diff --git a/docs/src/recipes/anti-patterns.asciidoc
b/docs/src/recipes/anti-patterns.asciidoc
index 8b11e6a..50ede67 100644
--- a/docs/src/recipes/anti-patterns.asciidoc
+++ b/docs/src/recipes/anti-patterns.asciidoc
@@ -128,7 +128,7 @@ and under certain circumstance they will not attempt to
rewrite a traversal. For
enabled (e.g. by using certain steps, such as `path()`, `simplePath()`,
`otherV()`, etc.), then the assumption is that all steps are
required in order to produce the desired path.
-An often seen anti-pattern is the one that explicitely traversers to an edge
and then to a vertex without using any filters.
+An often seen anti-pattern is the one that explicitly traverses to an edge and
then to a vertex without using any filters.
[gremlin-groovy,modern]
----
diff --git a/docs/src/recipes/olap-spark-yarn.asciidoc
b/docs/src/recipes/olap-spark-yarn.asciidoc
index 7feab81..990c6db 100644
--- a/docs/src/recipes/olap-spark-yarn.asciidoc
+++ b/docs/src/recipes/olap-spark-yarn.asciidoc
@@ -32,7 +32,7 @@ Most configuration problems of TinkerPop with Spark on YARN
stem from three reas
1. `SparkGraphComputer` creates its own `SparkContext` so it does not get any
configs from the usual `spark-submit` command.
2. The TinkerPop Spark plugin did not include Spark on YARN runtime
dependencies until version 3.2.7/3.3.1.
3. Resolving reason 2 by adding the cluster's Spark jars to the classpath may
create all kinds of version
-conflicts with the Tinkerpop dependencies.
+conflicts with the TinkerPop dependencies.
The current recipe follows a minimalist approach in which no dependencies are
added to the dependencies
included in the TinkerPop binary distribution. The Hadoop cluster's Spark
installation is completely ignored. This
@@ -150,7 +150,7 @@ as long as you do not use the `spark-submit` or
`spark-shell` commands. You will
runtime dependencies listed in the `Gremlin-Plugin-Dependencies` section of
the manifest file in the `spark-gremlin`
jar.
-You may not like the idea that the Hadoop and Spark jars from the Tinkerpop
distribution differ from the versions in
+You may not like the idea that the Hadoop and Spark jars from the TinkerPop
distribution differ from the versions in
your cluster. If so, just build TinkerPop from source with the corresponding
dependencies changed in the various `pom.xml`
files (e.g. `spark-core_2.11-2.2.0-some-vendor.jar` instead of
`spark-core_2.11-2.2.0.jar`). Of course, TinkerPop will
only build for exactly matching or slightly differing artifact versions.
