diff --git a/CHANGELOG.txt b/CHANGELOG.txt
index 97e2661..41c7922 100644
--- a/CHANGELOG.txt
+++ b/CHANGELOG.txt
@@ -1,10 +1,18 @@
+Project Git instructions 6.x-1.x, 2011-03-24
+--------------------------------------------
+- Default direction updates
+    * Issue #1080860: Updated commit message directions to explicitly recommend against starting messages with #.
+    * Issue #1092226: Updated command for creating patches from git format-patch to git diff
+    * Issue #1104302: Added directions for applying patches and abandoning local changes.
 
 Project Git instructions 6.x-1.x, 2011-xx-xx
 --------------------------------------------
+-  Default direction updates
+    * Issue #1075982 by helmo, David_Rothstein: Fixed 'Troubleshooting Git clone' link does not appear for projects you maintain.
 
-* Issue #1074220 by EclipseGc, helmo: Fixed Numerically Named Branches can result in bad instructions.
-* Issue #1073394 by drumm: Set project breadcrumb.
-* Issue #1075982 by helmo, David_Rothstein: Fixed 'Troubleshooting Git clone' link does not appear for projects you maintain.
+- Module updates
+    * Issue #1074220 by EclipseGc, helmo: Fixed Numerically Named Branches can result in bad instructions.
+    * Issue #1073394 by drumm: Set project breadcrumb.
 
 Project Git instructions 6.x-1.0, 2011-02-24
 --------------------------------------------
diff --git a/project_git_instructions.module b/project_git_instructions.module
index ee58de1..7cd4632 100644
--- a/project_git_instructions.module
+++ b/project_git_instructions.module
@@ -362,6 +362,11 @@ function project_git_instructions_project_promote_sandbox($project) {
  */
 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>
+</div>
 <h2>One-Time Only</h2>
 <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.
@@ -389,11 +394,10 @@ When you clone the repository you have access to all the branches and tags. The
 <code>git checkout [branchname]</code><br />
 </div>
 
-<h3>Commiting all changes locally</h3>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+<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 .</code><br />
+<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>
 </div>
 <h3>Pushing your code back to the repository on Drupal.org</h3>
@@ -405,8 +409,7 @@ For a discussion of this recommend patch sequence, see the <a href="/node/105461
 <div class="codeblock">
 <code>git checkout -b [description]-[issue-number]</code>
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+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 />
@@ -416,7 +419,43 @@ 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>
+
+<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.
+<h3>Branch for a dev release</h3>
+This creates and checks out a new branch in one command.
+<div class="codeblock">
+<code>git checkout -b 7.x-1.x</code><br />
+<code>git push origin 7.x-1.x</code><br />
+</div>
+<h3>Tag for a stable release</h3>
+<div class="codeblock">
+<code>git checkout  7.x-1.x</code><br />
+<code>git tag 7.x-1.0</code><br />
+<code>git push origin 7.x-1.0</code><br />
 </div>
 EOT;
   return $default;
@@ -427,6 +466,12 @@ EOT;
  */
 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>
+</div>
+
 <h2>One-Time Only</h2>
 <h3>Setting up repository for the first time:</h3>
 <div class="codeblock">
@@ -452,8 +497,7 @@ For a discussion of this recommend patch sequence, see the <a href="/node/105461
 <div class="codeblock">
 <code>git checkout -b [description]-[issue-number]</code>
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+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 />
@@ -463,8 +507,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;
 }
@@ -512,6 +577,11 @@ EOT;
 
 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>
+</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
@@ -524,7 +594,6 @@ details.</p>
 <br />
 <code>cd @project_fullname</code><br />
 </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>
@@ -541,11 +610,10 @@ When you clone the repository you have access to all the branches and tags. The
 </div>
 
 <h3>Committing all changes locally</h3>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+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 .</code><br />
-<code>git commit -m "Message about your changes"</code><br />
+<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
@@ -561,17 +629,16 @@ of:</p>
 <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 [branchname] </code>
+<code>git checkout -b [description]-[issue-number]</code>
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+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 .</code><br />
+<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>
-
 Roll the patch.
 <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 />
@@ -582,6 +649,11 @@ EOT;
 
 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>
+</div>
 <h2>One-Time Only</h2>
 <h3>Setting up this repository locally for the first time:</h3>
 <div class="codeblock">
@@ -596,7 +668,6 @@ 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.
 <div class="codeblock">
@@ -606,17 +677,16 @@ When you clone the repository you have access to all the branches and tags. The
 <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 [branchname] </code>
+<code>git checkout -b [description]-[issue-number]</code>
 </div>
-<p>Make your changes. Note the change in syntax for issue-related commit messages. See the <a
-href="/node/1061754">Commit messages</a> page for details.</p>
+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 .</code><br />
+<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>
-
 Roll the patch.
 <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 />