diff --git a/docs/en/installation/from-source.md b/docs/en/installation/from-source.md
index 38258c7f3..ff965781c 100644
--- a/docs/en/installation/from-source.md
+++ b/docs/en/installation/from-source.md
@@ -149,7 +149,8 @@ Please replace `<username>` below with your github username.
 	cd my-silverstripe-project
 	git clone git@github.com:<username>/sapphire.git sapphire
 	git clone git@github.com:<username>/silverstripe-cms.git cms
-	git clone git@github.com:<username>/silverstripe-blackcandy.git themes/blackcandy
+	rm -rf themes
+	git clone git@github.com:<username>/silverstripe-blackcandy.git themes
 
 Now you need to add the original repository as `upstream`, so you can keep your fork updated later on.
 
diff --git a/docs/en/misc/release-process.md b/docs/en/misc/release-process.md
index d0c498cc9..ca516974f 100644
--- a/docs/en/misc/release-process.md
+++ b/docs/en/misc/release-process.md
@@ -37,6 +37,8 @@ for stability and regression testing. Naming convention is *A.B.C-alpha* and *A.
 *  Major, minor and micro releases can have one or more *release candidates (RC)*, to be used by the wider community. A
 release candidate signifies that the core team thinks the release is ready without further changes. The actual release
 should be a identical copy of the latest RC. Naming convention is *A.B.C-rc1* (and further increments).
+* Major releases may have a *preview* cycle which is a early snapshot of the codebase for developers before 
+going into the *alpha* cycle. Preview releases are named *A.B.C-pr1* (and further increments).
 
 ### Major releases