diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
index db7127f..c1da1d1 100644
--- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
+++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -258,11 +258,11 @@ new packages would be ready to be used by our deployment scripts.
 The Validation Environment (VE) is a replica of the Production Environment
 (PE), with two exceptions: only the government officers and project leaders had
 access to it and all the data became anonymous. To configure the environment,
-we used a configuration management tool named Chef with Chake support (a
-serverless configuration for Chef tool created by our team). It maintained
-environment consistency simplifying the deployment process.  Additionally, the
-packages we built on the last step were readily available to be used by the
-management tool.
+we used a configuration management tool named Chef with Chake support
+(www.github.com/terceiro/chake) -- a serverless configuration created by our
+team). It maintained environment consistency simplifying the deployment
+process.  Additionally, the packages we built on the last step were readily
+available to be used by the management tool.
 
 The MP agents used the VE to validate new features and required changes. The VE
 also was used to verify the integrity of the entire portal as part of the next
--
libgit2 0.21.2