Fix more URLs.

# Conflicts:
#	docs/src/main/asciidoc/verifier_setup.adoc

docs/src/main/asciidoc/spring-cloud-wiremock.adoc

@@ -4,7 +4,7 @@
 
 == Spring Cloud Contract WireMock
 
-The Spring Cloud Contract WireMock modules let you use http://wiremock.org[WireMock] in a
+The Spring Cloud Contract WireMock modules let you use https://github.com/tomakehurst/wiremock[WireMock] in a
 Spring Boot application. Check out the
 https://github.com/spring-cloud/spring-cloud-contract/tree/{branch}/samples[samples]
 for more details.
@@ -164,7 +164,7 @@ visit `https://example.org/`, it gets the responses as being declared at that UR
 than one stub pattern can be specified, and each one can be a directory (for a recursive
 list of all ".json"), a fixed filename (as in the example above), or an Ant-style
 pattern. The JSON format is the normal WireMock format, which you can read about in the
-http://wiremock.org/docs/stubbing/[WireMock website].
+https://wiremock.org/docs/stubbing/[WireMock website].
 
 Currently, the Spring Cloud Contract Verifier supports Tomcat, Jetty, and Undertow as
 Spring Boot embedded servers, and Wiremock itself has "native" support for a particular

docs/src/main/asciidoc/verifier_faq.adoc

@@ -164,7 +164,7 @@ org.springframework.cloud.contract.spec.Contract.make {
 }
 ----
 
-IMPORTANT: Please read the http://groovy-lang.org/json.html[Groovy docs related to JSON] to understand how to
+IMPORTANT: Please read the https://groovy-lang.org/json.html[Groovy docs related to JSON] to understand how to
 properly structure the request / response bodies.
 
 === How to do Stubs versioning?

docs/src/main/asciidoc/verifier_introduction.adoc

@@ -20,7 +20,7 @@ Spring Cloud Contract Verifier.
 
 Before becoming Spring Cloud Contract, this project was called https://github.com/Codearte/accurest[Accurest].
 It was created by https://twitter.com/mgrzejszczak[Marcin Grzejszczak] and https://twitter.com/jkubrynski[Jakub Kubrynski]
-from (http://codearte.io[codearte.io].
+from (https://github.com/Codearte[Codearte].
 
 The `0.1.0` release took place on 26 Jan 2015 and it became stable with `1.0.0` release on 29 Feb 2016.
 
@@ -732,7 +732,7 @@ a map notation or String with interpolations.
 Consult the <<contract-dsl>> section for more information. We highly recommend using the map notation!
 
 TIP: You must understand the map notation in order to set up contracts. Please read the
-http://groovy-lang.org/json.html[Groovy docs regarding JSON].
+https://groovy-lang.org/json.html[Groovy docs regarding JSON].
 
 The previously shown contract is an agreement between two sides that:
 
@@ -911,7 +911,7 @@ the `contracts` folder, pick only one, which should be `fraud`. Add the `Base` s
 capitalize `fraud`. That gives you the `FraudBase` test class name.
 
 All the generated tests extend that class. Over there, you can set up your Spring Context
-or whatever is necessary. In this case, use http://rest-assured.io/[Rest Assured MVC] to
+or whatever is necessary. In this case, use https://github.com/rest-assured/rest-assured[Rest Assured MVC] to
 start the server side `FraudDetectionController`.
 
 [source,java,indent=0]
@@ -1046,9 +1046,9 @@ video::sAAklvxmPmk[youtube,start=538,width=640,height=480]
 ==== Readings
 
 - https://www.slideshare.net/MarcinGrzejszczak/stick-to-the-rules-consumer-driven-contracts-201507-confitura[Slides from Marcin Grzejszczak's talk about Accurest]
-- http://toomuchcoding.com/blog/categories/accurest/[Accurest related articles from Marcin Grzejszczak's blog]
-- http://toomuchcoding.com/blog/categories/spring-cloud-contract/[Spring Cloud Contract related articles from Marcin Grzejszczak's blog]
-- http://groovy-lang.org/json.html[Groovy docs regarding JSON]
+- https://toomuchcoding.com/blog/categories/accurest/[Accurest related articles from Marcin Grzejszczak's blog]
+- https://toomuchcoding.com/blog/categories/spring-cloud-contract/[Spring Cloud Contract related articles from Marcin Grzejszczak's blog]
+- https://groovy-lang.org/json.html[Groovy docs regarding JSON]
 
 === Samples
 

docs/src/main/asciidoc/verifier_setup.adoc

@@ -1007,7 +1007,7 @@ name of `scenario1` and the three following steps:
 . logout marked as `Step2` which will close the scenario.
 
 More details about WireMock scenarios can be found at
-http://wiremock.org/docs/stateful-behaviour/[http://wiremock.org/docs/stateful-behaviour/]
+https://wiremock.org/docs/stateful-behaviour/[https://wiremock.org/docs/stateful-behaviour/]
 
 Spring Cloud Contract Verifier also generates tests with a guaranteed order of execution.
 
@@ -1073,7 +1073,7 @@ It's enough for you to mount your contracts, pass the environment variables
 
 - generate the contract tests
 - execute the tests against the provided URL
-- generate the http://wiremock.org[WireMock] stubs
+- generate the https://github.com/tomakehurst/wiremock[WireMock] stubs
 - (optional - turned on by default) publish the stubs to a Artifact Manager
 
 ===== Environment Variables