bash-unit
diff --git a/‎README.adoc
+3-2 b/‎README.adoc
+3-2
diff --git a/‎getting_started/README.md
-7 b/‎getting_started/README.md
-7
diff --git a/‎getting_started/bash_unit
-1 b/‎getting_started/bash_unit
-1
diff --git a/‎getting_started/bonjour_monde
-3 b/‎getting_started/bonjour_monde
-3
diff --git a/‎getting_started/hello_i18n
-22 b/‎getting_started/hello_i18n
-22
diff --git a/‎getting_started/hello_timed
-17 b/‎getting_started/hello_timed
-17
diff --git a/‎getting_started/hello_world
-3 b/‎getting_started/hello_world
-3
diff --git a/‎getting_started/hola_mundo
-4 b/‎getting_started/hola_mundo
-4
diff --git a/‎getting_started/tests/test_bonjour_monde
-3 b/‎getting_started/tests/test_bonjour_monde
-3
diff --git a/‎getting_started/tests/test_hello_i18n
-18 b/‎getting_started/tests/test_hello_i18n
-18
diff --git a/‎getting_started/tests/test_hello_timed
-34 b/‎getting_started/tests/test_hello_timed
-34
diff --git a/‎getting_started/tests/test_hello_world
-3 b/‎getting_started/tests/test_hello_world
-3
diff --git a/‎getting_started/tests/test_no_ablo_espanol
-7 b/‎getting_started/tests/test_no_ablo_espanol
-7
diff --git a/‎getting_started/tests/test_skipping
-27 b/‎getting_started/tests/test_skipping
-27
@@ -20,8 +20,9 @@ bash_unit - bash unit testing enterprise edition framework for professionals!
 run them and, in case of failure, displays the stack trace
 with source file and line number indications to locate the problem.
 
-You might want to take a look at link:getting_started[how to get started]
-before continuing reading this documentation.
+Need a quick start? The
+https://github.com/bash-unit/getting_started/[getting started project]
+will help you get on track in no time.
 
 The following functions are available in your tests (see below for detailed documentation):