Sync docs from master to gh-pages

multi/multi__contract_dsl.html

@@ -1816,7 +1816,7 @@ leads to generation of two tests that look more or less like this:</p><pre class
 index of the contract in the list.</p><p>The generated stubs is shown in the following example:</p><pre class="screen">should post a user.json
 1_WithList.json</pre><p>As you can see, the first file got the <code class="literal">name</code> parameter from the contract. The second
 got the name of the contract file (<code class="literal">WithList.groovy</code>) prefixed with the index (in this
-case, the contract had an index of <code class="literal">1</code> in the list of contracts in the file).</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png"></td><th align="left">Tip</th></tr><tr><td align="left" valign="top"><p>As you can see, it iss much better if you name your contracts because doing so makes
+case, the contract had an index of <code class="literal">1</code> in the list of contracts in the file).</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png"></td><th align="left">Tip</th></tr><tr><td align="left" valign="top"><p>As you can see, it is much better if you name your contracts because doing so makes
 your tests far more meaningful.</p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="_generating_spring_rest_docs_snippets_from_the_contracts" href="#_generating_spring_rest_docs_snippets_from_the_contracts"></a>8.11&nbsp;Generating Spring REST Docs snippets from the contracts</h2></div></div></div><p>When you want to include the requests and responses of your API using Spring REST Docs,
 you only need to make some minor changes to your setup if you are using MockMvc and RestAssuredMockMvc.
 Simply include the following dependencies if you haven&#8217;t already.</p><p><b>Maven.&nbsp;</b>

single/spring-cloud-contract.html

@@ -5216,7 +5216,7 @@ leads to generation of two tests that look more or less like this:</p><pre class
 index of the contract in the list.</p><p>The generated stubs is shown in the following example:</p><pre class="screen">should post a user.json
 1_WithList.json</pre><p>As you can see, the first file got the <code class="literal">name</code> parameter from the contract. The second
 got the name of the contract file (<code class="literal">WithList.groovy</code>) prefixed with the index (in this
-case, the contract had an index of <code class="literal">1</code> in the list of contracts in the file).</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png"></td><th align="left">Tip</th></tr><tr><td align="left" valign="top"><p>As you can see, it iss much better if you name your contracts because doing so makes
+case, the contract had an index of <code class="literal">1</code> in the list of contracts in the file).</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png"></td><th align="left">Tip</th></tr><tr><td align="left" valign="top"><p>As you can see, it is much better if you name your contracts because doing so makes
 your tests far more meaningful.</p></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="_generating_spring_rest_docs_snippets_from_the_contracts" href="#_generating_spring_rest_docs_snippets_from_the_contracts"></a>8.11&nbsp;Generating Spring REST Docs snippets from the contracts</h2></div></div></div><p>When you want to include the requests and responses of your API using Spring REST Docs,
 you only need to make some minor changes to your setup if you are using MockMvc and RestAssuredMockMvc.
 Simply include the following dependencies if you haven&#8217;t already.</p><p><b>Maven.&nbsp;</b>

spring-cloud-contract.xml

@@ -4,7 +4,7 @@
 <book xmlns="http://docbook.org/ns/docbook" xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
 <info>
 <title>Spring Cloud Contract</title>
-<date>2018-05-08</date>
+<date>2018-05-09</date>
 </info>
 <preface>
 <title></title>
@@ -8414,7 +8414,7 @@ index of the contract in the list.</simpara>
 got the name of the contract file (<literal>WithList.groovy</literal>) prefixed with the index (in this
 case, the contract had an index of <literal>1</literal> in the list of contracts in the file).</simpara>
 <tip>
-<simpara>As you can see, it iss much better if you name your contracts because doing so makes
+<simpara>As you can see, it is much better if you name your contracts because doing so makes
 your tests far more meaningful.</simpara>
 </tip>
 </section>