1 files changed, 4 insertions, 2 deletions

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 727c2ec25b..5ce67ed504 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -225,6 +225,7 @@
                 results in a Yocto Project file structure whose Yocto Project source directory is named 
                 <filename>poky-edison-6.0</filename>.
                 If you create a Git repository, then you can name the repository anything you like.
+                By default, your local Git repository is named <filename>poky</filename>.
             </para>
 
             <para>
@@ -238,7 +239,8 @@
                 active development repository.
                 In this case, any local changes you make to the Yocto Project can be later applied to active
                 development branches of the upstream Yocto Project Git repository.
-                Furthermore, with the Git repository you can create a local Git branch that 
+                If you want to track a set of local changes while starting from the same point
+                as a release tarball, you can create a local Git branch that 
                 reflects the exact copy of the files at the time of their release. 
                 You do this using Git tags that are part of the repository.
                 For more information on concepts, see the section 
@@ -490,7 +492,7 @@
             And, the name of the local branch you have created and checked out is
             <filename>edison-6.0</filename>.
             The files in your repository now exactly match the Yocto Project 1.1
-            Release (edison).
+            Release tag (edison).
             It is important to understand that when you create and checkout a local 
             working branch based on a tag, your environment matches a specific point 
             in time and not a development branch.