From 9dd3aac7d61c5a4996953d9176a4ad03dc2db972 Mon Sep 17 00:00:00 2001
From: Marcin Grzejszczak <marcin@grzejszczak.pl>
Date: Fri, 23 Sep 2016 10:57:28 +0200
Subject: [PATCH] Sync docs from master to gh-pages

---
 spring-cloud-contract.html | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/spring-cloud-contract.html b/spring-cloud-contract.html
index 7c01721689..d18e2cab8d 100644
--- a/spring-cloud-contract.html
+++ b/spring-cloud-contract.html
@@ -467,6 +467,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
 </li>
 <li><a href="#_common_repo_with_contracts">Common repo with contracts</a>
 <ul class="sectlevel4">
+<li><a href="#_repo_structure">Repo structure</a></li>
 <li><a href="#_workflow">Workflow</a>
 <ul class="sectlevel5">
 <li><a href="#_consumer">Consumer</a></li>
@@ -2031,13 +2032,8 @@ It can be related to security issues where the consumers can&#8217;t clone the p
 contracts in a single place then you, as a producer, will know how many consumers you have and which
 consumer will you break with your local changes.</p>
 </div>
-<div class="ulist">
-<ul>
-<li>
-<p>Repo structure *</p>
-</li>
-</ul>
-</div>
+<div class="sect4">
+<h5 id="_repo_structure">Repo structure</h5>
 <div class="paragraph">
 <p>Let&#8217;s assume that we have a producer with coordinates <code>com.example:server</code> and 3 consumers: <code>client1</code>,
 <code>client2</code>, <code>client3</code>. Then in the repository with common contracts you would have the following setup
@@ -2266,6 +2262,7 @@ Those poms are necessary for the consumer side to run <code>mvn clean install -D
 &lt;/assembly&gt;</code></pre>
 </div>
 </div>
+</div>
 <div class="sect4">
 <h5 id="_workflow">Workflow</h5>
 <div class="paragraph">