diff --git a/CHANGELOG.txt b/CHANGELOG.txt
index 41c7922..dfd1d11 100644
--- a/CHANGELOG.txt
+++ b/CHANGELOG.txt
@@ -1,3 +1,9 @@
+Project Git instructiosn 6.x-1.x, 2011-04-20
+--------------------------------------------
+- Default direction updates
+    * Issue #1128070 by eliza411: Fixed Update Git instructions to include only the basic patch recommendation
+    * Issue #1127494 by eliza411: Fixed Git instructions for creating branches and tags is missing step about creating release nodes
+
 Project Git instructions 6.x-1.x, 2011-03-24
 --------------------------------------------
 - Default direction updates
diff --git a/project_git_instructions.module b/project_git_instructions.module
index 7cd4632..49227cf 100644
--- a/project_git_instructions.module
+++ b/project_git_instructions.module
@@ -364,11 +364,12 @@ function project_git_instructions_maintainer() {
   $default = <<<EOT
 <div class="meta">
 <ul>
-<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">changelog.txt</a> for details about updates to these instructions.</li>
-<li>Last updated: March 24, 2011</li>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/CHANGELOG.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
 </div>
+
 <h2>One-Time Only</h2>
-<h3>Setting up this repository in your local environment for the first time:</h3>
+<h3>Setting up this repository in your local environment for the first time</h3>
 If you have just created a project or you already have a local repository, skip this step.
 <div class="codeblock">
 <code>git clone --branch @branch @auth_project_url</code><br /><br />
@@ -376,7 +377,7 @@ If you have just created a project or you already have a local repository, skip
 </div>
 Not working for you? See <a href="/node/1065850">Troubleshooting Git clone</a>.
 <h3>Associating your copy of the repository with your Drupal.org account</h3>
-If you have NOT already <a href="/node/1022156#identify-global">identified yourself to Git globally</a>, do so now. Although it is standard practice to use a functional address, you can also use the pre-configured address <code>@git_username@@uid-no-reply.drupal.org</code>. See <a href="/node/1053134">Manage your Git identity</a> for details.
+If you have NOT already <a href="/node/1022156#identify-global">identified yourself to Git globally</a>, do so now. Although it is standard practice to use a functional address, you can also use the pre-configured address <code>@git_username@@uid.no-reply.drupal.org</code>. See <a href="/node/1022156">Identifying yourself to Git</a> for details.
 <div class="codeblock">
 <code>git config user.email "@email"</code><br />
 </div>
@@ -395,7 +396,7 @@ When you clone the repository you have access to all the branches and tags. The
 </div>
 
 <h3>Committing all changes locally</h3>
-After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/1061754">Commit messages</a> for details.
+After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/52287">Commit messages</a> for details.
 <div class="codeblock">
 <code>git add -A</code><br />
 <code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code>
@@ -404,44 +405,41 @@ After making changes, add and commit them. Do not begin commit messages with the
 <div class="codeblock">
 <code>git push origin @branch</code><br />
 </div>
-<h3>Creating a patch</h3>
-For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
+<h2>Patching</h2>
+<h3>Getting ready to create or apply patches</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch, then ensure it is up-to-date with the following command: 
 <div class="codeblock">
-<code>git checkout -b [description]-[issue-number]</code>
+<code>git pull origin @branch</code><br />
 </div>
-After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/1061754">Commit messages</a> for details.
+
+<h3>Creating a patch</h3>
+For most improvements, use the following command after making your changes:
 <div class="codeblock">
-<code>git add -A</code><br />
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
+<code>git diff >  [description]-[issue-number]-[comment-number].patch</code> <br />
 </div>
-Roll the patch.
+For more complex improvements that require adding/removing files, work over the course of multiple days, or collaboration with others, see the <a href="/node/1054616">Advanced patch workflow</a>.
+
+<h3>Applying a patch </h3>
+Download the patch to your working directory. Apply the patch with the following command:
 <div class="codeblock">
-<code>git status</code><br />
-<code>git fetch origin</code><br />
-<code>git rebase origin/@branch</code><br />
-<code>git diff origin/@branch > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>git apply -v [patchname.patch]</code><br />
 </div>
 
-<h3>Applying a patch</h3>
-If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch and that it is up-to-date using the following commands:
+To avoid accidentally including the patch file in future commits, remove it:
 <div class="codeblock">
-<code>git checkout --track origin/@branch</code><br />
-<code>git pull origin @branch</code><br />
+<code>rm  [patchname.patch]</code><br />
 </div>
 
-Next, download the patch to your working directory to apply it. There are many variables involved in applying patches, so if the following command doesn't work for you, see <a href="/patch/apply">Applying patches</a> for more detail.</p>
-<div class="codeblock"><code>git apply [patch.name]</code><br /></div>
-Finally, remove the patch file:
-<div class="codeblock"><code>rm  [patch.name]</code><br /></div>
+<h3>When you're done: Reverting uncommited changes</h3>
+Revert changes to a specific file: 
+<div class="codeblock">
+<code>git checkout [filename]</code><br />
+</div>
 
-<h3>Abandoning your local changes</h3>
-<p>
-Abandon changes to a specific file: <br />
-<div class="codeblock"><code>git checkout [filename]</code></div>
-</p><p>
-Abandon changes to the whole working tree: <br />
-<div class="codeblock"><code>git reset --hard</code></div>
-</p>
+Revert changes to the whole working tree: 
+<div class="codeblock">
+<code>git reset --hard</code><br />
+</div>
 
 <h2>Creating Releases</h2>
 See the <a href="/node/1015226">naming conventions</a> for a complete description of how to name branches and tags so you can create releases.
@@ -457,6 +455,7 @@ This creates and checks out a new branch in one command.
 <code>git tag 7.x-1.0</code><br />
 <code>git push origin 7.x-1.0</code><br />
 </div>
+<p>Once you've pushed the properly  formed tag or branch, see <a href="/node/1068944">Creating a project release</a> for directions to actually create the release node.</p>
 EOT;
   return $default;
 }
@@ -468,12 +467,13 @@ function project_git_instructions_nonmaintainer() {
   $default = <<<EOT
 <div class="meta">
 <ul>
-<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">changelog.txt</a> for details about updates to these instructions.</li>
-<li>Last updated: March 24, 2011</li>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
 </div>
 
+
 <h2>One-Time Only</h2>
-<h3>Setting up repository for the first time:</h3>
+<h3>Setting up repository for the first time</h3>
 <div class="codeblock">
 <code>git clone --branch @branch @anon_project_url</code><br />
 <code>cd @uri</code><br />
@@ -492,44 +492,41 @@ When you clone the repository you have access to all the branches and tags.  The
 <code>git branch -a</code><br />
 <code>git checkout [branchname]</code><br />
 </div>
-<h3>Creating a patch</h3>
-For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
+<h2>Patching</h2>
+<h3>Getting ready to create or apply patches</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch, then ensure it is up-to-date with the following command: 
 <div class="codeblock">
-<code>git checkout -b [description]-[issue-number]</code>
+<code>git pull origin @branch</code><br />
 </div>
-After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/1061754">Commit messages</a> for details.
+
+<h3>Creating a patch</h3>
+For most improvements, use the following command after making your changes:
 <div class="codeblock">
-<code>git add -A</code><br />
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
+<code>git diff >  [description]-[issue-number]-[comment-number].patch</code> <br />
 </div>
-Roll the patch.
+For more complex improvements that require adding/removing files, work over the course of multiple days, or collaboration with others, see the <a href="/node/1054616">Advanced patch workflow</a>.
+
+<h3>Applying a patch </h3>
+Download the patch to your working directory. Apply the patch with the following command:
 <div class="codeblock">
-<code>git status</code><br />
-<code>git fetch origin</code><br />
-<code>git rebase origin/@branch</code><br />
-<code>git diff origin/@branch  > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>git apply -v [patchname.patch]</code><br />
 </div>
 
-<h3>Applying a patch</h3>
-If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch and that it is up-to-date using the following commands:
+To avoid accidentally including the patch file in future commits, remove it:
 <div class="codeblock">
-<code>git checkout --track origin/@branch</code><br />
-<code>git pull origin @branch</code><br />
+<code>rm  [patchname.patch]</code><br />
 </div>
 
-Next, download the patch to your working directory to apply it. There are many variables involved in applying patches, so if the following command doesn't work for you, see <a href="/patch/apply">Applying patches</a> for more detail.</p>
-<div class="codeblock"><code>git apply [patch.name]</code><br /></div>
-Finally, remove the patch file:
-<div class="codeblock"><code>rm  [patch.name]</code><br /></div>
+<h3>When you're done: Reverting uncommited changes</h3>
+Revert changes to a specific file: 
+<div class="codeblock">
+<code>git checkout [filename]</code><br />
+</div>
 
-<h3>Abandoning your local changes</h3>
-<p>
-Abandon changes to a specific file: <br />
-<div class="codeblock"><code>git checkout [filename]</code></div>
-</p><p>
-Abandon changes to the whole working tree: <br />
-<div class="codeblock"><code>git reset --hard</code></div>
-</p>
+Revert changes to the whole working tree: 
+<div class="codeblock">
+<code>git reset --hard</code><br />
+</div>
 EOT;
   return $default;
 }
@@ -579,21 +576,22 @@ function project_git_instructions_sandbox_maintainer() {
   $default = <<<EOT
 <div class="meta">
 <ul>
-<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">changelog.txt</a> for details about updates to these instructions.</li>
-<li>Last updated: March 24, 2011</li>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
 </div>
+
 <h2>One-Time Only</h2>
-<h3>Setting up this repository in your local environment for the first time:</h3>
-<p>You will be prompted to enter your Drupal.org password after the
-first step (and any time you make requests from Drupal.org) if you
-have not uploaded an SSH key or if your SSH key fails. See <a
-href="/node/1027094">Authenticate with Git on Drupal.org</a> for
-details.</p>
+<h3>Setting up repository for the first time</h3>
 <div class="codeblock">
 <code>git clone --branch @branch @auth_sandbox_url @project_fullname</code><br />
-<br />
 <code>cd @project_fullname</code><br />
 </div>
+Not working for you? See <a href="/node/1065850">Troubleshooting Git clone</a>.
+<h3>Associating your copy of the repository with your Drupal.org account</h3>
+If you have NOT already <a href="/node/1022156#identify-global">identified yourself to Git globally</a>, do so now. Although it is standard practice to use a functional address, you can also use the pre-configured address <code>@git_username@@uid-no-reply.drupal.org</code>. See <a href="/node/1022156">Identifying yourself to Git</a> for details.
+<div class="codeblock">
+<code>git config user.email "@email"</code><br />
+</div>
 <h2>Routinely</h2>
 The headings below are not sequential. What you choose to do depends on where you are in your process.
 <h3>Checking your repository status</h3>
@@ -601,37 +599,18 @@ To see what you will commit by running <code>git commit</code> and what you coul
 <div class="codeblock">
 <code>git status</code><br />
 </div>
-
 <h3>Switching to a different branch</h3>
-When you clone the repository you have access to all the branches and tags. The first command shows your choices. The second command makes the switch.  See <a href="/node/1066342">branching and tagging</a> for details.
+When you clone the repository you have access to all the branches and tags.  The first command shows your choices. The second command makes the switch. See <a href="/node/1066342">branching and tagging</a> for details.
 <div class="codeblock">
 <code>git branch -a</code><br />
 <code>git checkout [branchname]</code><br />
 </div>
-
-<h3>Committing all changes locally</h3>
-After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/1061754">Commit messages</a> for details.
-<div class="codeblock">
-<code>git add -A</code><br />
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
-</div>
-<br />
-<p><strong>Note:</strong> When patching in response to an issue from your issue queue, the format for the commit message takes the form
-of:</p>
-<div class="codeblock">
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
-</div>
-<h3>Pushing your code back to the repository on Drupal.org</h3>
-<div class="codeblock">
-<code>git diff origin/@branch</code><br />
-<code>git push origin @branch</code><br />
-</div>
 <h3>Creating a patch</h3>
 For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
 <div class="codeblock">
 <code>git checkout -b [description]-[issue-number]</code>
 </div>
-After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/1061754">Commit messages</a> for details.
+After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/52287">Commit messages</a> for details.
 <div class="codeblock">
 <code>git add -A</code><br />
 <code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
@@ -641,8 +620,29 @@ Roll the patch.
 <code>git status</code><br />
 <code>git fetch origin</code><br />
 <code>git rebase origin/@branch</code><br />
-<code>git format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>git diff origin/@branch  > [description]-[issue-number]-[comment-number].patch</code><br />
 </div>
+
+<h3>Applying a patch</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch and that it is up-to-date using the following commands:
+<div class="codeblock">
+<code>git checkout --track origin/@branch</code><br />
+<code>git pull origin @branch</code><br />
+</div>
+
+Next, download the patch to your working directory to apply it. There are many variables involved in applying patches, so if the following command doesn't work for you, see <a href="/patch/apply">Applying patches</a> for more detail.</p>
+<div class="codeblock"><code>git apply [patch.name]</code><br /></div>
+Finally, remove the patch file:
+<div class="codeblock"><code>rm  [patch.name]</code><br /></div>
+
+<h3>Abandoning your local changes</h3>
+<p>
+Abandon changes to a specific file: <br />
+<div class="codeblock"><code>git checkout [filename]</code></div>
+</p><p>
+Abandon changes to the whole working tree: <br />
+<div class="codeblock"><code>git reset --hard</code></div>
+</p>
 EOT;
   return $default;
 }
@@ -651,16 +651,18 @@ function project_git_instructions_sandbox_nonmaintainer() {
   $default = <<<EOT
 <div class="meta">
 <ul>
-<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">changelog.txt</a> for details about updates to these instructions.</li>
-<li>Last updated: March 24, 2011</li>
+<li>Update Notice: See <a href="http://drupalcode.org/project/project_git_instructions.git/blob_plain/HEAD:/changelog.txt">CHANGELOG.txt</a> for details about updates to these instructions.</li>
+<li>Last updated: April 20, 2011</li>
 </div>
+
 <h2>One-Time Only</h2>
-<h3>Setting up this repository locally for the first time:</h3>
+<h3>Setting up this repository locally for the first time</h3>
 <div class="codeblock">
 <code>git clone --branch @branch @anon_sandbox_url @project_fullname</code><br />
 <code>cd @project_fullname</code>
 </div>
 Not working for you? See <a href="/node/1065850">Troubleshooting Git clone</a>.
+
 <h2>Routinely</h2>
 The headings below are not sequential. What you choose to do depends on where you are in your process.
 <h3>Checking your repository status</h3>
@@ -674,22 +676,40 @@ When you clone the repository you have access to all the branches and tags. The
 <code>git branch -a</code><br />
 <code>git checkout [branchname]</code><br />
 </div>
+<h2>Patching</h2>
+<h3>Getting ready to create or apply patches</h3>
+If you have not already cloned the repository, follow the directions above for setting up this repository in your local environment. Be sure you are on the branch you wish to patch, then ensure it is up-to-date with the following command: 
+<div class="codeblock">
+<code>git pull origin @branch</code><br />
+</div>
+
 <h3>Creating a patch</h3>
-For a discussion of this recommend patch sequence, see the <a href="/node/1054616">Patch contributor guide.</a>
+For most improvements, use the following command after making your changes:
 <div class="codeblock">
-<code>git checkout -b [description]-[issue-number]</code>
+<code>git diff >  [description]-[issue-number]-[comment-number].patch</code> <br />
 </div>
-After making changes, add and commit them. Do not begin commit messages with the # symbol. See <a href="/node/1061754">Commit messages</a> for details.
+For more complex improvements that require adding/removing files, work over the course of multiple days, or collaboration with others, see the <a href="/node/1054616">Advanced patch workflow</a>.
+
+<h3>Applying a patch </h3>
+Download the patch to your working directory. Apply the patch with the following command:
 <div class="codeblock">
-<code>git add -A</code><br />
-<code>git commit -m &quot;Issue #[issue number] by [comma-separated usernames]: [Short summary of the change].&quot;</code><br />
+<code>git apply -v [patchname.patch]</code><br />
 </div>
-Roll the patch.
+
+To avoid accidentally including the patch file in future commits, remove it:
 <div class="codeblock">
-<code>git status</code><br />
-<code>git fetch origin</code><br />
-<code>git rebase origin/@branch</code><br />
-<code>git format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patch</code><br />
+<code>rm  [patchname.patch]</code><br />
+</div>
+
+<h3>When you're done: Reverting uncommited changes</h3>
+Revert changes to a specific file: 
+<div class="codeblock">
+<code>git checkout [filename]</code><br />
+</div>
+
+Revert changes to the whole working tree: 
+<div class="codeblock">
+<code>git reset --hard</code><br />
 </div>
 EOT;
   return $default;