Author: spmallette
Date: Tue Nov 13 18:34:25 2018
New Revision: 1846529
URL: http://svn.apache.org/viewvc?rev=1846529&view=rev
Log:
Minor format fix to TinkerPop 3.4.0-SNAPSHOT docs
Modified:
tinkerpop/site/docs/3.4.0-SNAPSHOT/reference/index.html
Modified: tinkerpop/site/docs/3.4.0-SNAPSHOT/reference/index.html
URL:
http://svn.apache.org/viewvc/tinkerpop/site/docs/3.4.0-SNAPSHOT/reference/index.html?rev=1846529&r1=1846528&r2=1846529&view=diff
==============================================================================
--- tinkerpop/site/docs/3.4.0-SNAPSHOT/reference/index.html (original)
+++ tinkerpop/site/docs/3.4.0-SNAPSHOT/reference/index.html Tue Nov 13 18:34:25
2018
@@ -16929,7 +16929,7 @@ executing. It is up to the script to pr
<div class="sect2">
<h3 id="connecting-via-drivers">Connecting via Drivers</h3>
<div class="paragraph">
-<p><span class="image" style="float: right"><img
src="../images/rexster-connect.png" alt="rexster connect" width="400"></span>
TinkerPop offers client-side drivers for the Gremlin Server websocket
+<p><span class="image" style="float: right"><img
src="../images/rexster-connect.png" alt="rexster connect" width="180"></span>
TinkerPop offers client-side drivers for the Gremlin Server websocket
sub-protocol in a variety of languages:</p>
</div>
<div class="ulist">
@@ -20588,7 +20588,7 @@ connection methods described in the <a h
<div class="sect2">
<h3 id="_connecting">Connecting</h3>
<div class="paragraph">
-<p><span class="image" style="float: left"><img
src="../images/rexster-connect.png" alt="rexster connect" width="400"></span>
The pattern for connecting is described in
+<p>The pattern for connecting is described in
<a href="#connecting-gremlin">Connecting Gremlin</a> and it basically distills
down to creating a <code>GraphTraversalSource</code>.
For <a href="#connecting-embedded">embedded</a> mode, this involves first
creating a <code>Graph</code> and then spawning the
<code>GraphTraversalSource</code>:</p>
@@ -21495,7 +21495,7 @@ succinct.</p>
<div class="sect2">
<h3 id="_connecting_2">Connecting</h3>
<div class="paragraph">
-<p><span class="image" style="float: left"><img
src="../images/rexster-connect.png" alt="rexster connect" width="400"></span>
The pattern for connecting is described in
+<p>The pattern for connecting is described in
<a href="#connecting-gremlin">Connecting Gremlin</a> and it basically distills
down to creating a <code>GraphTraversalSource</code>. A
<code>GraphTraversalSource</code> is created from the anonymous
<code>traversal()</code> method where the "g" provided to the
<code>DriverRemoteConnection</code> corresponds to the name of a
<code>GraphTraversalSource</code> on the remote end.</p>
@@ -22208,7 +22208,7 @@ in order to comply with .NET conventions
<div class="sect2">
<h3 id="_connecting_3">Connecting</h3>
<div class="paragraph">
-<p><span class="image" style="float: left"><img
src="../images/rexster-connect.png" alt="rexster connect" width="400"></span>
The pattern for connecting is described in
+<p>The pattern for connecting is described in
<a href="#connecting-gremlin">Connecting Gremlin</a> and it basically distills
down to creating a <code>GraphTraversalSource</code>. A
<code>GraphTraversalSource</code> is created from the
<code>AnonymousTraversalSource.traversal()</code> method where the "g" provided
to
the <code>DriverRemoteConnection</code> corresponds to the name of a
<code>GraphTraversalSource</code> on the remote end.</p>
@@ -22559,7 +22559,7 @@ between Gremlin-Java and Gremlin-JavaScr
<div class="sect2">
<h3 id="_connecting_4">Connecting</h3>
<div class="paragraph">
-<p><span class="image" style="float: left"><img
src="../images/rexster-connect.png" alt="rexster connect" width="400"></span>
The pattern for connecting is described in
+<p>The pattern for connecting is described in
<a href="#connecting-gremlin">Connecting Gremlin</a> and it basically distills
down to creating a <code>GraphTraversalSource</code>.
A <code>GraphTraversalSource</code> is created from the
<code>AnonymousTraversalSource.traversal()</code> method where the "g" provided
to
the <code>DriverRemoteConnection</code> corresponds to the name of a
<code>GraphTraversalSource</code> on the remote end.</p>
