From d18fca116059a16e7ee9dfa2c4ce6c781e83895f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jean-R=C3=A9mi=20Desjardins?=
 <jeanremi.desjardins@gmail.com>
Date: Mon, 13 Jul 2015 17:05:54 -0700
Subject: [PATCH] Update ScalaCheck website

---
 app/views/userGuide/generatorDrivenPropertyChecks.scala.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/views/userGuide/generatorDrivenPropertyChecks.scala.html b/app/views/userGuide/generatorDrivenPropertyChecks.scala.html
index 22fa17db2b..271afea4e9 100644
--- a/app/views/userGuide/generatorDrivenPropertyChecks.scala.html
+++ b/app/views/userGuide/generatorDrivenPropertyChecks.scala.html
@@ -25,7 +25,7 @@ <h1>Generator-driven property checks</h1>
 To use generator-driven property checks, you must mix in trait <a href="@latestScaladoc/#org.scalatest.prop.GeneratorDrivenPropertyChecks"><code>GeneratorDrivenPropertyChecks</code></a> (or import the
 members of its companion object). If you are also using table-driven property checks, you can mix in
 trait <a href="@latestScaladoc/#org.scalatest.prop.PropertyChecks"><code>PropertyChecks</code></a>,
-which extends both <code>GeneratorDrivenPropertyChecks</code> and <a href="@latestScaladoc/#org.scalatest.prop.TableDrivenPropertyChecks"><code>TableDrivenPropertyChecks</code></a>. Generator-driven property checks uses <a href="http://code.google.com/p/scalacheck/">ScalaCheck</a>, so you must also include the ScalaCheck JAR file on your classpath when you compile and run your tests.
+which extends both <code>GeneratorDrivenPropertyChecks</code> and <a href="@latestScaladoc/#org.scalatest.prop.TableDrivenPropertyChecks"><code>TableDrivenPropertyChecks</code></a>. Generator-driven property checks uses <a href="https://www.scalacheck.org/">ScalaCheck</a>, so you must also include the ScalaCheck JAR file on your classpath when you compile and run your tests.
 </p>
 
 <p>