From f079b8e440d818688f23c5f0abaed0fb46b078b6 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Fri, 23 Sep 2016 10:55:22 +0200 Subject: [PATCH] Updated docs --- README.adoc | 2 +- docs/src/main/asciidoc/verifier/introduction.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.adoc b/README.adoc index 5f6b46822e..3afb31345b 100644 --- a/README.adoc +++ b/README.adoc @@ -1241,7 +1241,7 @@ It can be related to security issues where the consumers can't clone the produce 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. -* Repo structure * +===== Repo structure Let's assume that we have a producer with coordinates `com.example:server` and 3 consumers: `client1`, `client2`, `client3`. Then in the repository with common contracts you would have the following setup diff --git a/docs/src/main/asciidoc/verifier/introduction.adoc b/docs/src/main/asciidoc/verifier/introduction.adoc index 19678bee58..e1a365e737 100644 --- a/docs/src/main/asciidoc/verifier/introduction.adoc +++ b/docs/src/main/asciidoc/verifier/introduction.adoc @@ -732,7 +732,7 @@ It can be related to security issues where the consumers can't clone the produce 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. -* Repo structure * +===== Repo structure Let's assume that we have a producer with coordinates `com.example:server` and 3 consumers: `client1`, `client2`, `client3`. Then in the repository with common contracts you would have the following setup