diff --git a/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki b/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki
index 1e82a466..372d4051 100644
--- a/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki
+++ b/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki
@@ -107,7 +107,7 @@ That was a targeted template: EiffelStudio will propose it whenever the user typ
 You can share your code templates using Github
 
 == Fork the project == 
-Clone your fork, and configure the remotes.  [https://github.com/EiffelSoftware/EiffelStudio  https://github.com/EiffelSoftware/EiffelStudio ]
+Clone your fork, and configure the remotes.Eiffel Studio github repository at:  [https://github.com/EiffelSoftware/EiffelStudio  https://github.com/EiffelSoftware/EiffelStudio ]
 
 # Clone your fork of the repo into the current directory: <code>git clone https://github.com/<your-username>/<repo-name></code>
 # Navigate to the newly cloned directory: <code>cd <repo-name></code>
@@ -123,7 +123,7 @@ git pull upstream <dev-branch>
 == New Branch ==
 Create a new topic branch (off the main project development branch) to contain your new code template
 <code>git checkout -b <topic-branch-name></code>
-Commit your changes in logical chunks. Before to commit double check Tim Pope's A Note About Git Commit Messages (http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+Commit your changes in logical chunks. Before to commit double check [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html Tim Pope's A Note About Git Commit Messages]
 Use Git's interactive rebase feature to tidy up your commits before making them public.
 
 Locally merge (or rebase) the upstream development branch into your topic branch: